On Wed, 29 Mar 2017, Konstantin Gribov wrote:
I've been surprised by such separation, what was the reason to separate them?
I think partly history (we split in 1.x), partly how the split was done (osgi folks amongst the most keen), and partly a desire not to have non-OSGi users getting a load of things they didn't need / might confuse them?
If there's no blockers I'd prefer to merge them: OSGi headers in MANIFEST.MF do not affect artifact usage in usual Java SE environment and it reduces number of artifacts drastically and simplifies dependency management.
Just adding a few headers to the manifest would be fine with me, that seems low-risk and low-impact
Not sure on the unit testing front - we'd want the current parser unit tests to run fully outside OSGi, plus we want some other tests to run within an OSGi environment to ensure the bundle's fine. Can we easily do both if we merged? or would we want to merge the headers but leave the OSGi-specific tests in another module?
Nick
