Hello,

unfortunately, it happens rarely. Not easy to reproduce this. I think that I
saw this when starting Karaf cleanly, i.e. after deleting the data folder. I
have skipped 4.0.6, so cannot tell whether it would also show up there.

Regarding my org.ops4j.pax.url.mvn.cfg: everything is commented except for
the following:

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.data}/kar@id=kar.repository@multi@snapshots, \
   
file:${karaf.base}/${karaf.default.repository}@id=child.system.repository@snapshots,
\
    file:${karaf.home}/myrepo@id=my_repository@snapshots

And (but I don't know whether that may be relevant in this context) I have
changed the enterprise feature xml in my custom distribution: using 2.4.0
version of the Eclipselink JPA adapter bundle.

I assume that it stumbles over the enterprise feature xml is just due to the
fact that this is the first one in my featuresRepositories setting in
org.apache.karaf.features.cfg. But also for that, I don't have a proof.

Regards,
Jochen



--
View this message in context: 
http://karaf.922171.n3.nabble.com/Avoird-default-value-for-org-ops4j-pax-url-mvn-repositories-tp4048924p4048955.html
Sent from the Karaf - User mailing list archive at Nabble.com.

Reply via email to