Bram de Kruijff wrote:
1) The ant build failes on my Windows XP system (ant 1.6.3 / maven 2.0.4
/ JDK1.5.0_6).
Don't know why all executables are in my PATH, but it probably has to do
with my config.
Workaround: I just run de mvn commands by hand.
----------------------------------------------
BUILD FAILED
c:\subversion\felix\trunk\build.xml:37: Execute failed:
java.io.IOException: CreateProcess: C:\java\maven-2.0.4\bin\mvn -f
pom-new-plugin.xml clean install error 193
----------------------------------------------
To me, this seems like a Windows issue...I am not sure what to do about
it right off the top of my head.
2) Next, building the trunk with pom-new-plugin.xml failes because the
maven-bundle-plugin can't be located.
Maven bug? The module is in the pom-new-plugin.xml but that doesn't help
:(
Workaround: I build this module by hand first so it is in my local repo.
This doesn't seem like it should be an issue because I have an
up-to-date maven-bundle-plugin in the snapshot repository.
I just removed my local maven repository and rebuilt from scratch by
typing "ant" in the trunk directory and everything built fine.
3) Next, building the trunk with pom-new-plugin.xml buils successfull!
4) Next, building the trunk with pom-old-plugin.xml failes on ipojo
dependencies.
It seems the reactor failes to resolve the proper order. Some
dependecies may be wrong?
Workaround: I first build the ipojo.metadata module and then the
ipojo.plugin module so it is in my local repo.
Again, I built from scratch and it worked for me. It almost sounds like
you are having some issues with the snapshot repository, but I don't
know what.
5) Next, building the trunk with pom-old-plugin.xml fails because the
module http.jetty doesn't compile.
It seems the transient dependency on the javax.servlet module (Servlet
API 2.1) takes precedence over the tomcat:servlet:4.0.6 dependency
(Servlet API 2.3)? This happens in compile:compile but also in Eclipse
3.2 using the Maven2 plugin.
Workaround: I disabled the module. I don't need it.
Yes, this is a known issue...the strange thing is, sometimes it builds
for me and sometimes it does not. I asked Rob Walker if he could look
into this issue...I may end up commenting out the offending line in the
HTTP service until I figure out what should really be done.
Thanks for the feedback. It is helpful, although I am not exactly sure
what we can do to fix all of the issues...perhaps someone else has some
insight.
-> richard
