[ http://jira.codehaus.org/browse/MOJO-514?page=comments#action_78990 ] Dan Tran commented on MOJO-514: -------------------------------
I think this is a dup of http://jira.codehaus.org/browse/MOJO-413 Kaare, could you verify? my build dont have a need for jaxb2 any more, and I dont have the project to verify Thanks > When having multiple executions the jaxb plugin uses same staleFile for both > runs > --------------------------------------------------------------------------------- > > Key: MOJO-514 > URL: http://jira.codehaus.org/browse/MOJO-514 > Project: Mojo > Issue Type: Bug > Components: jaxb2 > Environment: all > Reporter: Kaare Nilsen > > When using mulitple executions like this : > <plugin> > <groupId>org.codehaus.mojo</groupId> > <artifactId>jaxb2-maven-plugin</artifactId> > <version>1.0</version> > <executions> > <execution> > <id>status</id> > <goals> > <goal>xjc</goal> > </goals> > <configuration> > <packageName>com.myapp.apackage</packageName> > <schemaFiles>xxx.xsd</schemaFiles> > </configuration> > </execution> > <execution> > <id>command</id> > <goals> > <goal>xjc</goal> > </goals> > <configuration> > <packageName>anotherPackage</packageName> > <schemaFiles>xxx2.xsd</schemaFiles> > </configuration> > </execution> > </executions> > </plugin> > </plugins> > The follwing happens.. a .staleFlag is created when the firt execution runs, > and then the second finds that there are no changes, and do not run. > So. a possible fix would be that each execution had its own staleFlag. > It is possible to workaround this by setting staleFlag in the config, but > hey.. not very intituive right ? -- 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 --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
