Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: JiBX 1.2.3
-
Fix Version/s: JiBX 1.2.3
-
Component/s: maven plugin
-
Labels:None
-
Number of attachments :
Description
Date: Tue, 15 Mar 2011 17:13:15 -0700
From: Frank Mena <jibxusers@gmail.com>
Subject: [jibx-users] jibx maven plugin breaks between version 1.2.2
and 1.2.3
To: jibx-users@lists.sourceforge.net
Message-ID:
<AANLkTimqdDQYvp3v1bXvqJMGeTxD5kACt7Bwfgz9L5CP@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Hi Dennis, long time no speak. I was the original author of the plugin
collaborating with Andreas back in 2005.
Here is my setup:
project common: some bindings
project dbmodel: some bindings
project service: some bindings
project web: no bindings, jibx plugin
Here is the plugin in the web pom:
<plugin>
<groupId>org.jibx</groupId>
<artifactId>maven-jibx-plugin</artifactId>
<version>$
{jibx.version}</version>
<executions>
<execution>
<phase>process-classes</phase>
<goals>
<goal>bind</goal>
</goals>
</execution>
</executions>
<configuration>
<multimodule>true</multimodule>
<directory>src/main/config</directory>
<includes>
<include>*.jibx.xml</include>
</includes>
</configuration>
</plugin>
This works perfectly with version 1.2.2, but version 1.2.3 says:
Not running JiBX binding compiler (multi-module mode) - no binding files
I have tried every combination of changing to restricted mode:
<bindingModules>
<classPath>com.noledgy.appryse:common</classPath>
<classPath>com.noledgy.appryse:dbmodel</classPath>
<classPath>com.noledgy.appryse:service</classPath>
</bindingModules>
and the new syntax:
<modules>
<module>com.example:example1</module>
<module>com.example:example2</module>
</modules>
but nothing works. What's wrong?
Frank Mena
Activity
| Field | Original Value | New Value |
|---|---|---|
| Status | Open [ 1 ] | Closed [ 6 ] |
| Fix Version/s | JiBX 1.2.3 [ 16349 ] | |
| Resolution | Fixed [ 1 ] |
Yep, I broke it.
I changed the file scanner from apache oro to plexus, since oro was retired by Apache. In the process I broke multi-module mode.
I should be able to fix this.
Note: I did add a new multi-module capability in 1.2.3 that does not require a build to be run on the shared parent.