[Pax URL] Status of unreleased and obsolete modules

2012-01-23 Thread Harald Wellmann
I'd like to clarify the status of unreleased and potentially obsolete Pax URL modules and maybe delete some of them for the 1.4.0 release. pax-url-mvn: There's a request to delete this "deprecated" module. (http://team.ops4j.org/browse/PAXURL-131) I can't find any deprecation markers in this

Re: Many pax url bundles are broken due to org.slf4j.impl import

2012-01-23 Thread Achim Nierbeck
Hi Harald, I didn't even notice this behavior since there wasn't any issue with it so far. Back to your initial question, I don't know why it is that way and I'm with you that we should favor import over embedding. So as long as there is a proper package available I'm +1 for changing embedding to

Re: Many pax url bundles are broken due to org.slf4j.impl import

2012-01-23 Thread Harald Wellmann
Ok, the problem seems to be caused by all those embedded dependencies. I hadn't really noticed that Pax URL bundles embed most of their dependencies instead of importing them. I suppose we could add import directives to the BND configuration so that the Pax URL bundles import the required packages