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. 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.
One way to see if that really is the issue it to do:
mvn clean install
then just
mvn install
If the first fails, but the second passes, that's likely the culprit as
the second install will skip processing anything since the first one did
it. For 2.0.4, we're working around it in the codegen plugin by
recording and saving the system properties around the code generation so
when the plugin exits, things are restored. That said, if you have any
other maven plugins that do some xml processing, they could be causing
the same issue.
Suggestion to try:
Run 'mvn -X' and look at the dependency reports. (possibly use the
dependency plugin as well) See if anything that looks like an XML
parser or processor (like xalan or saxon or something) is being pulled
in. If so, see if you can exclude it. That MIGHT work.
Dan
On Thursday 17 January 2008, Glen Mazza wrote:
> No, Windows XP Professional, SP2.
>
> dkulp wrote:
> > Geln,
> >
> > You aren't, by any chance, on a Mac? Are you?
> >
> > Dan
> >
> > On Thursday 17 January 2008, Glen Mazza wrote:
> >> Hello,
> >>
> >> I'm having difficulty upgrading from CXF 2.0.2 to CXF 2.0.3 using
> >> Mavenized builds. With CXF 2.0.3 (not 2.0.2), Maven keeps trying
> >> to download nonexistent versions of jars (in particular, Version
> >> 1.0 of cxf-api and cxf-rt-core, neither of which have 1.0 versions
> >> anywhere) and fails because it cannot find them. As you can see
> >> below, running "mvn clean install" with the debug (-X) option seems
> >> to show that cxf-rt-transports-http-jetty is the culprit: it is
> >> resolving its dependencies to the invalid 1.0 versions while
> >> cxf-rt-frontend-jaxws is requesting the normal, available, 2.0.3
> >> versions.
> >>
> >> [DEBUG]
> >> org.apache.cxf:cxf-rt-transports-http-jetty:jar:2.0.3-incubator:com
> >>pil e (selected for compile)
> >> -->[DEBUG] org.apache.cxf:cxf-api:jar:1.0:compile (selected for
> >> compile) [DEBUG]
> >> org.apache.cxf:cxf-rt-transports-http:jar:1.0:compile (applying
> >> version: 2.0.3-incubator)
> >> [DEBUG]
> >> org.apache.cxf:cxf-rt-transports-http:jar:2.0.3-incubator:compile
> >> (selected for compile)
> >> -->[DEBUG] org.apache.cxf:cxf-rt-core:jar:1.0:compile
> >> (selected for compile)
> >> [DEBUG] org.apache.cxf:cxf-rt-core:jar:1.0:compile (selected
> >> for compile)
> >> [DEBUG] org.mortbay.jetty:jetty:jar:6.1.5:compile (selected for
> >> compile) [DEBUG]
> >> org.mortbay.jetty:jetty-util:jar:6.1.5:compile (selected for
> >> compile)
> >> [DEBUG]
> >> org.apache.geronimo.specs:geronimo-servlet_2.5_spec:jar:1.1-M1:comp
> >>ile (selected for compile)
> >> [DEBUG] commons-lang:commons-lang:jar:2.3:compile (selected for
> >> compile) [DEBUG]
> >> org.apache.cxf:cxf-rt-frontend-jaxws:jar:2.0.3-incubator:compile
> >> (selected for compile)
> >> [DEBUG] javax.xml.ws:jaxws-api:jar:2.0:compile (selected for
> >> compile) -->[DEBUG]
> >> org.apache.cxf:cxf-api:jar:2.0.3-incubator:compile (removed -
> >> nearer found: 1.0)
> >> -->[DEBUG]
> >> org.apache.cxf:cxf-rt-core:jar:2.0.3-incubator:compile (removed -
> >> nearer found: 1.0)
> >> [DEBUG]
> >> org.apache.cxf:cxf-rt-bindings-soap:jar:2.0.3-incubator:compile
> >> (selected for compile)
> >> [DEBUG] org.apache.cxf:cxf-api:jar:2.0.3-incubator:compile
> >> (removed - nearer found: 1.0)
> >> [DEBUG]
> >> org.apache.cxf:cxf-tools-common:jar:2.0.3-incubator:compile
> >> (selected for compile)
> >> [DEBUG] velocity:velocity:jar:1.4:compile (selected for
> >> compile) [DEBUG] velocity:velocity-dep:jar:1.4:runtime
> >> (selected for runtime)
> >>
> >> I'm still somewhat early in my troubleshooting, I'm going to
> >> simplify the pom files next to the bare minimum that reproduces
> >> this error. In the meantime, though, has anyone seen this error
> >> before? I am hoping that someone would know what might cause this
> >> to save me
> >> troubleshooting time.
> >>
> >> Also, when does one need the "cxf-rt-transports-http-jetty"
> >> dependency? Is it a requirement for Jetty use--we are using Jetty
> >> so I cannot remove this dependency (which might indirectly fix this
> >> problem) if Jetty requires it. I might be able to pull it out of
> >> compilation scope, however.
> >>
> >> Thanks,
> >> Glen
> >
> > --
> > J. Daniel Kulp
> > Principal Engineer, IONA
> > [EMAIL PROTECTED]
> > http://www.dankulp.com/blog
--
J. Daniel Kulp
Principal Engineer, IONA
[EMAIL PROTECTED]
http://www.dankulp.com/blog
