I had a similar problem (see
http://karaf.922171.n3.nabble.com/Intermittent-error-on-startup-Error-resolving-artifact-td4047587.html).
The enterprise feature was always tried to be resolved (always the one which
was mentioned as first feature), though it was present in the local
repository. It ended up with a different exception in karaf 4.0.5 though.
We got rid of this be setting the pax mav url properties as System
Properties instead of setting them in the "org.ops4j.pax.url.mvn.cfg". The
problem in my case what that the bundle got reloaded upon reading the new
configs and got into a wired state. Maybe this helps to reveal the real
problem.
org.ops4j.pax.url.mvn.cfg
---
org.ops4j.pax.url.mvn.useFallbackRepositories=false
org.ops4j.pax.url.mvn.repositories=
system.properties
---
org.ops4j.pax.url.mvn.useFallbackRepositories=false
org.ops4j.pax.url.mvn.defaultRepositories=\
file:${karaf.home}/${karaf.default.repository}@id=system.repository@snapshots,
\
file:${karaf.base}/${karaf.default.repository}@id=child.system.repository@snapshots
Cheers,
Philipp
--
View this message in context:
http://karaf.922171.n3.nabble.com/Avoird-default-value-for-org-ops4j-pax-url-mvn-repositories-tp4048924p4048968.html
Sent from the Karaf - User mailing list archive at Nabble.com.
