You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently there is no UI support for jars.extra.classpath in the Manifest editor and du to its prominent placing people instead use often additional.bundles to add something that should be there for compile but not imported (what serves a different purpose) leading to confusion.
Even though jars.extra.classpath theoretically supports different styles, we should only support the form where one can specify a single bundle platform:/plugin/<Bundle-SymbolicName> as this is also supported by Tycho and easy to adapt by other tools.
The text was updated successfully, but these errors were encountered:
Officially also relative path is supported as well as inner jars:
extra classpaths used to perform automated build. Classpath can either be relative paths, or platform urls referring to plug-ins and fragments of your development environment (e.g. ../someplugin/xyz.jar, platform:/plugins/org.apache.ant/ant.jar). Platform urls are recommended over relative paths;
I just think that if one really requires a version or relative path one can do it manually, but e.g additional bundles do only support a BSN and people seem happy with that already (but using it for a different purpose).
Currently there is no UI support for
jars.extra.classpath
in the Manifest editor and du to its prominent placing people instead use oftenadditional.bundles
to add something that should be there for compile but not imported (what serves a different purpose) leading to confusion.Even though
jars.extra.classpath
theoretically supports different styles, we should only support the form where one can specify a single bundleplatform:/plugin/<Bundle-SymbolicName>
as this is also supported by Tycho and easy to adapt by other tools.The text was updated successfully, but these errors were encountered: