Locally upgrading Pax URL from 1.4.0 to 1.4.2 breaks my Pax Exam builds.

There is a new dependency on org.osgi.service.cm which was not required in 1.4.0.

I've traced this down to http://team.ops4j.org/browse/PAXURL-187, but from the problem description and the commit comments, I don't really see why the Config Admin Service is involved at all or why it has to be introduced in a base class for _all_ URL handlers.

Could someone please shed some light on this...?

Best regards,
Harald

_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general

Reply via email to