> > Hmm... OK.... Not sure what to say then although it's probably the
> > same issue as ServiceMix had on the Mac.
> >
> > There is a bug in Maven where system properties can overwrite and
> > affect anything that uses "${project.version}" and/or
> > "${pom.version}" like we do.
>
> Questions:
>
> 1.) Do you know if the Maven team is aware of this problem--is it in
> their JIRA?
http://jira.codehaus.org/browse/MNG-2339
and a bunch of duplicates and related issues that are linked to it.
> 2.) Any reason why this might not be occurring with CXF 2.0.2? Or did
> the ServiceMix
> problem also occur with CXF 2.0.2?
Well, there are three major changes that may have caused this:
1) Catalog support in the tools - with catalog support, we had to add
some extra XML stuff to the tools to parse/process the catalogs.
2) Validation of the wsdl - 2.0.3 validates the wsdls now to make sure
they really are valid. Again, that's more XML processing.
3) To get (1) working, we had to add all the dependencies to the
classloader that is used when running the plugin. Thus, if your project
depended on a problematic xml parser, with 2.0.2, that wouldn't affect
the plugin running, but with 2.0.3, it might.
ServiceMix was mostly bit by #3 as they were sucking in some old versions
of xerces and such that caused issues.
> dkulp wrote:
> > The issue is that some XML parsers or processor (like the one
> > built into the OSX jvm) has a tendency to set a "version" system
> > property which messes that up. Thus, any plugin that does XML
> > processing at all can cause major issues. Unfortunately, our
> > wsdl2java plugin does XML processing.
>
> 3.) I'm probably exposing my Maven noviceness here, but can CXF be
> changed to stop using ${project.version} and ${pom.version} internally
> then to avoid this error? If I understand you correctly, as long as
> CXF avoids these properties, the problem goes away, correct?
Possibly, but we'll need to experiment a bit. In particular, the release
process may break. The release plugin currently updates everything that
is needed. I'm not sure if it would update a different property or
not.
--
J. Daniel Kulp
Principal Engineer, IONA
[EMAIL PROTECTED]
http://www.dankulp.com/blog
