Alexandros,
Wow, that's a lot of questions. Let me see if I can help you.
1. If you run:
mvn compile
The JiBX binding compiler will not run. This is the correct behavior.
Remember JiBX adds byte codes AFTER your code is compiled (in the '
process-classes' phase). Use
mvn package
and you should be okay.
2. If you use standard maven directories, your generated classes should
automatically be included in your jar files. If you are having problems, try
taking a look at some of our examples, here:
http://jibx.svn.sourceforge.net/viewvc/jibx/trunk/plugins/maven-plugin/test-suite/
3. Yes, there was a bug in multi-module generation:
http://jira.codehaus.org/browse/JIBX-431
It has been fixed.
This fixed code will be included in the 1.2.4 release. To use it now, just
check it out of our svn repo and build it:
svn co
https://jibx.svn.sourceforge.net/svnroot/jibx/trunk/plugins/maven-plugin/jibx-maven-plugin
cd jibx-maven-plugin
mvn install
Remember to change your plugin name to jibx-maven-plugin (from
maven-jibx-plugin) and update the revision number to 1.2.4-SNAPSHOT.
jibx-maven-plugin is the new plugin name.
If you can't get this to work, email me back and I'll release a bugfix
(1.2.3.1) version.
Hope this helps!
Don
------------------------------------------------------------------------------
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-users mailing list
jibx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-users
