Hi,
long term, I think we should try to remove all the generated classes
(whether from mapping.xsd, binding.xsd et alias) from the SVN repository
altogether, as classes that are generted should be .. well, generated
(at least everytime the source artefact changes).
In terms of build process, this should be easily achievable, as both
Maven and Ant have support for code generation through Ant tasks or
Maven plugins. It's just a matter of getting the Maven POM and/or Ant
build file modified accordingly.
Let me just point out one thing in particular, though: whilst this
change will be achievable for both JDO configuration file and XML code
generation binding file, for the mapping this might not be achievable,
as we need a working (compileable) data binding framework in order to be
able to call e.g. the Ant task from Ant.
As a first step, I'd suggest to move the generated classes for e.g. the
binding file to a new package
org.exolab.castor.builder.binding.generated
and to amend src/build.xml accordingly, to make things a bit clearer and
better structured.
What's the thoughts on this ?
Regards
Werner
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
