Hi John, John Langley schrieb: > I ran into something similar yesterday, however in my case a command > line driven maven build was fine, whereas a maven build from within > eclipse was failing in the way that Vidar describes.
Failure to compile inside Eclipse but not on the command line might be related to the fact, that depending on the Maven plugin you are using, the Eclipse-integrated Maven version operates differently than your command line Maven version with respect to class path ordering. Regards Felix > > I considered it an unfortunate eclipse idiosyncrasy and moved on using > just command line based maven builds. However, I was hoping that the > problem could be resolved as "giving up" on the capabilities that > eclipse brings in terms of navigating and discovering the relationships > between objects in the source in invaluable. > > -- Langley > > > On Wed, 2009-02-18 at 10:42 -0500, Vidar Ramdal wrote: > >>> Vidar Ramdal schrieb: >>>> I'm unable to build Sling at the moment (fresh checkout, clean install): >>>> INFO] Compilation failure >>>> [...] >>>> I see Felix (Meschberger) has updated the dependency to (Apache) Felix >>>> Framework 1.5.0-SNAPSHOT - maybe something has changed in >>>> 1.5.0-SNAPSHOT since then? >>> What platform (OS, Java Version, Maven Version) are you using in this >>> failed build ? >> OS X 10.5.6, Java 1.6 (also tried 1.5, same result), Maven 2.0.7 >> >> I looked into the .jars downloaded by Maven (both >> org.apache.felix.framework-1.5.0-SNAPSHOT.jar and >> org.apache.felix.framework-1.5.0-20090217.191803-5.jar), and they both >> include the two missing constants in org.osgi.framework.Constants. >> >> Can we exclude the OSGi Core jar from the launchpad/base build? >> >
