> 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.
Allthough I think all felix -code should compile against the code in the reactor (right?) maven does look for the maven-bundle-plugin in the snapshot repository. So the build would (probably) still be succefull if the snapshot repository would be somewhat up-to-date. Are there any plans to keep the snapshot repository up-to-date (eg. using continuum)? regards, Bram > -----Original Message----- > From: Bram de Kruijff [mailto:[EMAIL PROTECTED] > Sent: Saturday, November 18, 2006 5:20 PM > To: felix-dev@incubator.apache.org > Subject: troubles building Felix > > Hello felix-dev, > > today I thought it would be fun to get the latest and > greatest Felix up and running. The good news is that I got it > to work in the end, but I did have some troubles. Some issues > may be related to my setup (or even > me) and some may be 'known issues'. I'm not sure. Anyway, > below is what happend when I tried to do a clean build > against an EMPTY local maven repository. I hope this helps > other people that encounter these same issues and help you to > improve the 'user experience' :) > > best regards, > Bram > > > system: Windows XP system (ant 1.6.3 / maven 2.0.4 / > JDK1.5.0_6) felix : At revision: 476549 > > > 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 > ---------------------------------------------- > > > 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. > > > 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. > > > 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. > > ---------------------------------------------- > [INFO] Compilation failure > > C:\subversion\felix\trunk\http.jetty\src\main\java\org\mortbay > \jetty\ser > vlet\OsgiServletHandler.java:[95,20] cannot find symbol > symbol : method flushBuffer() > location: interface javax.servlet.http.HttpServletResponse > ---------------------------------------------- > > 6) Next, building the trunk with pom-new-plugin.xml buils > successfull!
