[
http://jira.codehaus.org/browse/JIBX-415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Don Corley resolved JIBX-415.
-----------------------------
Resolution: Fixed
Fix Version/s: JiBX 1.2.3
1.2.3 has fixed this issue.
> schema-codegen does not work if module is built in an "also-make" way or from
> a multimodule parent
> --------------------------------------------------------------------------------------------------
>
> Key: JIBX-415
> URL: http://jira.codehaus.org/browse/JIBX-415
> Project: JiBX
> Issue Type: Bug
> Components: maven plugin
> Affects Versions: JiBX 1.2.1
> Environment: Windows 7, Maven 3.0.2
> Reporter: Antti Koivisto
> Assignee: Don Corley
> Fix For: JiBX 1.2.3
>
>
> I have a multi module project like this:
> * A
> ** A.I
> *** A.I.OXM
> *** A.I.COMMON
> The A.I.OXM module contains the following:
> {code}
> <build>
> <plugins>
> <plugin>
> <groupId>org.jibx</groupId>
> <artifactId>maven-jibx-plugin</artifactId>
> <executions>
> <execution>
> <id>generate-java-code-from-schema</id>
> <goals>
> <goal>schema-codegen</goal>
> </goals>
> <configuration>
> <options>
>
> <directory>src/main/resources/jibx</directory>
> <package>foo.bar</package>
> </options>
> </configuration>
> </execution>
> <execution>
> <id>compile-binding</id>
> <goals>
> <goal>bind</goal>
> </goals>
> <configuration>
> <directory>target/generated-sources</directory>
> <load>true</load>
> <validate>true</validate>
> <verbose>true</verbose>
> <verify>true</verify>
> </configuration>
> </execution>
> </executions>
> </plugin>
> </plugins>
> </build>
> {code}
> If I build the A.I.OXM module by going into it and issuing "mvn clean
> install", the codes are generated correctly and the jar file installed to
> local maven repo contains the generated sources.
> But if I go into module A and do a "mvn clean install
> --projects=A.I/A.I.COMMON --also-make" the A.I.OXM module is not built
> properly. The xsd schema file available in the specified directory is not
> picked up.
> Also doing a "mvn clean install" in the A module has the same effect.
> A solution to this problem seems to be to remove the <directory> option and
> use the default location.
> When I did this, all three ways of building the module were successful.
> The problem might be mostly with documentation that used
> <directory>src/something</directory> as an example. Should it have some maven
> property references too?
> My environment is:
> Apache Maven 3.0.2 (r1056850; 2011-01-09 02:58:10+0200)
> Java version: 1.6.0_23, vendor: Sun Microsystems Inc.
> Java home: C:\java\jdk6u23\jre
> Default locale: fi_FI, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
jibx-devs mailing list
jibx-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-devs
