Ok with this debugging information I was able to debug into the maven
execution and see where the validation really fails. For some reason the
MavenExecutionRequest had its system properties not populated. I looked what
the hudson embedder is doing regarding the system properties and did the
same:
I am still hunting this one down. For some reason I do not seem to be able to
get proper debug output from maven. I really would like to know why this
keeps preventing me from getting the proper dependencies for the resources
plugin included:
10:54:43.051 [main] WARN d.b.a.i.b.maven.MavenLogging
Hi,
thanks for the hint. When including this dependency for some reason I seem
to run into major classloader issues. Here is the output/exception of the
maven execution:
11:09:28.750 [main] WARN d.b.a.i.b.maven.MavenLoggingAdapter - The POM for
org.apache.maven:maven-archiver:jar:2.4.1 is inval
Hi,
I'm in the middle of developing an integration server for several month now.
Of course the system embedds maven which did work rather good with maven
2.2.1 and even the beta builds of maven 3. Since the release of 3.0 and even
3.0.1 my own MavenEmbedder class (basically something like this
ht
