Jibx compiler modified "non-jibx" classes in multi-module Maven environment
---------------------------------------------------------------------------
Key: JIBX-181
URL: http://jira.codehaus.org/browse/JIBX-181
Project: JiBX
Issue Type: Bug
Components: core
Affects Versions: JiBX 1.1.5
Environment: jdk 1.5; maven 2.0.5
Reporter: Frank Luo
This problem only exists with maven projects with multi-modules.
Supposing there are two maven projects A and B. B depends on A and jibx is used
in B but classes in A is refered in the binding files via get/set-methods. So
in theory, classes in A shouldn't be modified because only getter/setters are
accessed by Jibx, but it might or might not be true, depends on how maven is
invoked.
If the projects are built separately, namely build A first, then B. Because B
is refering A throught a jar file, then classes in A are not modified (of
course). But if A and B are built at the same time, then at the time B is
built, maven is smart enough to add project A's classes, instead of A.jar, in
the classpath for compiling, and somehow A's classes are modified by Jibx,
which is not desired.
Did I make myself clear?
--
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
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
jibx-devs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jibx-devs
