Hi John,
why are you having both the castor-xml and the castor JARs on your class
path. Can you please drop the Über-Castor JAR ? That should make it work.
Kind Regards
Werner
On 11.01.2014 00:37, [email protected] wrote:
Hi all,
I’ve have an old app that builds with Maven 1.1 that I’m trying to bring
in to the 21^st century. I’m not ready to upgrade Maven, but I am
trying to upgrade Castor from 1.0.5 to 1.3.3. I’m having difficulty with
the code generation.
I’m updating the Maven 1.1 Castor plugin to use the new Castor 1.3.3
jars. I can’t figure out the right combination of jars to use,
however. If I don’t fork the Castor code gen step
(org.exolab.castor.builder.SourceGenerator) then the build appears to
succeed.
However I would like to fork the step, as I always have, because my
build is very memory intensive. When I do that, I get a sealing
exception saying that org.castor.mapping is sealed. Indeed, that
package is in both the castor and castor-xml jars. In fact, there is a
lot of overlap between them. Unfortunately if I omit one or the other,
I get class not found issues. Should I just unseal the jar? Am I way
off base?
BTW, I seem to need these jars:
Castor
Codegen
Xml-schema
Xml
Core
Commons-lang
Thanks
John
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
