Miguel,

This issue has been solved in JiBX 1.2.3. We are attempting to get this release out the door soon.

The new jibx plugin has goals for generating schema code (test-schema-codegen) and binding (test-bind) during the test phase.

To use the new code, please check it out of the cvs dev repository and build it. ie., type:

cvs -z3 -d:pserver:anonymous@jibx.cvs.sourceforge.net:/cvsroot/jibx co -P maven-jibx-plugin
cd maven-jibx-plugin
mvn install
mvn site (this will install the new documentation on your hard disk at target/site
(ignore any warnings)

This will overwrite your maven-jibx-plugin version 1.2.2 with the new code.
Now try to build your maven project. It should work as expected.
Thanks,
Don

---quoted
Message: 4
Date: Sat, 15 Jan 2011 12:22:35 +0000
From: Miguel <miguel@almeida.at>
Subject: [jibx-users] Jibx an Maven: how to have different profiles
       for testing and production
To: jibx-users@lists.sourceforge.net
Message-ID: <1295094155.3648.11.camel@itcd001>
Content-Type: text/plain; charset="utf-8"

Dear all,

I use Maven and the jibx-maven plugin. I have a conceptual doubt
regarding the usage of both with testing.

While testing the jibx  components I have some *bindingTest.xml
bindings. While these are useful for testing purposes, they shouldn't be
in the production environment. Moreover, I might even have two
conflicting bindings (ie, relating to the same class), like
PersonbindingTest.xml and Personbinding.xml

Now, because Jibx uses bytecode enhancement, this means that if I
package my classes in Maven and run the tests, I believe the packaged
file will contain bindingTest's bytecode enhancement, even if, in Maven,
I tell it not to package the bindingTest.xml files.

My current "hack" for this problem involves creating two maven profiles
in the jibx-plugin (see http://pastebin.com/GbDVP54d ): one is invoked
in the testing goal, the other in the packaging goal.

The tests fail, however, if I run the package goal without "skip tests",
because *bindingTest.xml files were not used.
Is there a configuration I am not seeing that allows us to run the
bindingTest.xml to perform the test, but ignores these files (and
deletes the corresponding bytecode enhanced classes) in the packaging
phase?


All input welcome!


Miguel Almeida
---- quoted