sesuncedu
commented
9 years ago With the bundle metadata, you could avoid the now embedded dependencies in the workbench. Embedded dependencies are a pain, though they do make deploying & checking plugins easier if there's only one jar to check. As long as the pom metadata is there, things will work outside OSGI with just wasted space. It would have made sense for OSGI to attempt to install any embedded dependencies that are bundles, but embedded dependencies are not encouraged, and, it would have made sense.
(Also, not sure what the backward compatibility version ranges should be for the workbench - explicit versions, with no upper range, promise that a dependency will never be backwards incompatible. The Maven bundle plugin defaults to making the upper bound be the next major version number of the version used, with the lower bound being the minor version number (which is a pain if the lower bound needs to be finer than point)) .
That's a different repository. On Mar 17, 2015 11:52 AM, "Matthew Horridge" notifications@github.com wrote:
Merged #3 https://github.com/matthewhorridge/owlexplanation/pull/3.
— Reply to this email directly or view it on GitHub https://github.com/matthewhorridge/owlexplanation/pull/3#event-257049454 .
1: Add description, with URL pointing to Horridge (2011). 2: Change owlapi version dependency to be [3.5.1 to 3.5.9] 3: Change telemetry version dependency to be any version <2 where 2.0.0-SNAPSHOT < 2 4: Exclude transitive owlapi import from telemetry. 5: Change packaging type to bundle. Doesn't seem to be actively harmful.