The current 3.3-SNAPSHOT off of trunk (rev 600620) doesn't build for
me either. Cleaned .m2 and checked out, it fails on step2:
Downloading: http://repo1.maven.org/maven2/org/apache/axis2/axis2-
saaj-api/1.3-r562247/axis2-saaj-api-1.3-r562247.pom
[INFO] [xmlbeans:xmlbeans {execution: default}]
[INFO] All schema objects are up to date.
[INFO] [build:copy {execution: default}]
[INFO] [groovy:execute {execution: default}]
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Invalid value for 'source' parameter; contains nested elements
[INFO]
------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Invalid value
for 'source' parameter; contains nested elements
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
(DefaultLifecycleExecutor.java:564)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec
ycle(DefaultLifecycleExecutor.java:480)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal
(DefaultLifecycleExecutor.java:459)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle
Failures(DefaultLifecycleExecutor.java:311)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
DefaultLifecycleExecutor.java:278)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute
(DefaultLifecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:
334)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced
(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode
(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: Invalid
value for 'source' parameter; contains nested elements
at org.codehaus.mojo.groovy.MojoSupport.execute
(MojoSupport.java:79)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo
(DefaultPluginManager.java:443)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
(DefaultLifecycleExecutor.java:539)
... 16 more
Caused by: org.apache.maven.plugin.MojoExecutionException: Invalid
value for 'source' parameter; contains nested elements
at org.codehaus.mojo.groovy.execute.ExecuteMojo.process
(ExecuteMojo.java:150)
at org.codehaus.mojo.groovy.ComponentMojoSupport.doExecute
(ComponentMojoSupport.java:68)
at org.codehaus.mojo.groovy.MojoSupport.execute
(MojoSupport.java:71)
... 18 more
On Dec 8, 2007, at 4:43 AM, Guillaume Nodet wrote:
So i now have the same problem.
Given that it was working at some point (at least when I did the
release),
I'm wondering if there has been any change in a maven repo.
On Dec 8, 2007 8:18 AM, Guillaume Nodet <[EMAIL PROTECTED]> wrote:
It's more a logical path rather than a physical one. You may have
the
version between the two /s.
Anyway, I will try to build 3.2.1 and 3.3-snapshot from a clean repo
on Monday and see what happens.
On 12/8/07, samjoe9998 <[EMAIL PROTECTED]> wrote:
I agree that those 'file:'s should have nothing to do with the
exception. Do
you know how do I validate the .car file is valid or not? Why the
path
is
not 'org.apache.geronimo.configs/jee-specs/car' but
'org.apache.geronimo.configs/jee-specs//car' ?
bsnyder wrote:
On Dec 7, 2007 11:22 AM, samjoe9998 <[EMAIL PROTECTED]> wrote:
I used the exact instruction there. I think the difference is that
you
might
build (since you use tarball, I guess) on Linux platform. I
built on
Windows
XP. The windows 3.2.1-src.zip contains invalid entries such as
"file:xxx"
(a
bunch of HTMLs) which can not be extracted by WinZip. I have to
use
7-Zip
to
remove those entries before uncompress, but that should not affect
the
build
at all. Is this relate to the path separator between Linux and
Windows?
I did notice during my testing for this issue that I also have a
directory named file: upon expansion of the tarball. This build
issue
has nothing to do with the extra directory that's included from the
filesystem. This issue appears to have something to do with a
bad car
file from Geronimo as it says it failed to load.
Bruce
--
perl -e 'print
unpack("u30","D0G)[EMAIL PROTECTED]&5R\"F)R=6-E+G-N>61E<D\!G;6%I;
\"YC;VT*"
);'
Apache ActiveMQ - http://activemq.org/
Apache Camel - http://activemq.org/camel/
Apache ServiceMix - http://servicemix.org/
Apache Geronimo - http://geronimo.apache.org/
Blog: http://bruceblog.org/
--
View this message in context:
http://www.nabble.com/ServiceMix-3.2.1-build-failure%3A-Unable-to-
resolve-dependency-org.apache.geronimo.configs-jee-specs--car-
tf4962714s12049.html#a14225204
Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
--
Daryl
http://itsallsemantics.com
