Hi Vidar, This is strange and never has been reported... But it may be related to how maven resolves dependencies :-(
The point is that this property is rather new, so Framework 1.5-SNAPSHOT has it. But the property is in the org.osgi.framework.Constants interface which is both in the Apache Felix framework and the OSGi Core JAR Files. Thus if maven uses the framework first, the constant resolves. If maven uses the OSGi Core library first in the class path, the constant does not resolve. What platform (OS, Java Version, Maven Version) are you using in this failed build ? Regards Felix Vidar Ramdal schrieb: > Hi, > > I'm unable to build Sling at the moment (fresh checkout, clean install): > INFO] Compilation failure > > /Users/vramdal/dev/sling-trunk/launchpad/base/src/main/java/org/apache/sling/launchpad/base/impl/Sling.java:[396,68] > cannot find symbol > symbol : variable FRAMEWORK_STORAGE > location: interface org.osgi.framework.Constants > > /Users/vramdal/dev/sling-trunk/launchpad/base/src/main/java/org/apache/sling/launchpad/base/impl/Sling.java:[397,72] > cannot find symbol > symbol : variable FRAMEWORK_BEGINNING_STARTLEVEL > location: interface org.osgi.framework.Constants > > > 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? >