Hi, yes, this is a known defect due to the maven aether module. It always tries to load the latest version from the maven repo cause usually you don't have the needed meta data if you build on your local machine.
For development right now I suggest using a local Maven Repo Proxy like Nexus or Apache Archiva Regards, Achim 2012/2/22 Guofeng Zhang <[email protected]> > Hi,**** > > ** ** > > Build last Karaf 3.0.0-SNAPSHOT, then try to launch webconsole, I got the > following wire error:**** > > Error executing command: Could not start bundle > mvn:org.apache.karaf.shell/org.apache.karaf.shell.http/3.0.0-SNAPSHOT in** > ** > > feature(s) http-3.0.0-SNAPSHOT: Unresolved constraint in bundle > org.apache.karaf.shell.http [57]: Unable to resolve 57.**** > > 0: missing requirement [57.0] osgi.wiring.package; > (&(osgi.wiring.package=org.ops4j.pax.web.service.spi)(version>=1.1.0)**** > > (!(version>=2.0.0)))**** > > ** ** > > I configured org.ops4j.pax.url.mvn.cfg to use my local maven repository:** > ** > > org.ops4j.pax.url.mvn.settings=file:///c:/.m2/settings.xml**** > > ** ** > > but I find that Karaf or pax-url always download > org.apache.karaf.shell.http from apache snapshot repository, because I find > the following jar in system repository and it depends on > org.ops4j.pax.web.service.spi [1.1.0,2.0.0]**** > > org.apache.karaf.shell.http-3.0.0-20120202.094242-172.jar**** > > ** ** > > what did I configure org.ops4j.pax.url.mvn.cfg improperly?**** > > ** ** > > Thanks**** > > ** ** > > Guofeng**** > > ** ** > > ** ** > -- Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead blog <http://notizblog.nierbeck.de/>
