I haven't seen this happen in my tests, and in looking at the code the
only way I can see for it to occur is perhaps if your binding starts out
with a <mapping> for a class that can't be modified directly. Can you
give the first part of your binding definition? Thanks,
- Dennis
Daniel Cox wrote:
jibx-beta3b has been working perfectly for me using run-time bindings.
I now need to integrate JiBX into the ANT build process - and cut/paste the
directions directly from www.jibx.org.
My Java source files are in src/ and the resulting class files go into bin/ which is
then JARed. build.xml is in the parent directory.
./build.xml
./src/package/*.java
./bin/package/*.class
If I run the Binding Compiler manually with java -jar (from the bin/ directory) it
works.
The ANT bind task creates the following files in the current directory (ie. NOT in bin)
- JiBX_MungeAdapter.class
- JiBX_bindingHashMapper_0.class
- JiBX_bindingFactory.class
All other classes are created in the correct package subdirectories of bin/.
How can the ANT script be modified so the bind process will create all files under a
specified path instead of the current directory?
Thankyou,
Daniel C.
-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
_______________________________________________
jibx-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jibx-users
