[jbosstools-issues] [JBoss JIRA] (JBIDE-12815) Create a JBoss Tools Orbit
[
https://issues.jboss.org/browse/JBIDE-12815?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-12815:
------------------------------------
If these bundles are to be *consumed as a dependency* of another project's plugins or
features (via MANIFEST.MF or feature.xml), then the fact that no license is presented when
installing is not really a problem for me. The same is true of any other installed plugin,
whether done via the p2 UI, JBoss Central, or p2.director: plugins don't present
license terms when installing, only features. This can be demonstrated, for example, when
installation of VJET (JBIDE-14122) causes the installation of other 3rd party Orbit
dependencies like org.w3c.dom.events or org.junit4 under the covers.
Create a JBoss Tools Orbit
--------------------------
Key: JBIDE-12815
URL: https://issues.jboss.org/browse/JBIDE-12815
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Build/Releng, locus
Reporter: Mickael Istria
Assignee: Paul Richardson
Fix For: 4.1.0.Beta1
Since all JBoss Eclipse-based project probably share some needs for usual libraries, we
should create a JBoss Tools Orbit project in which one we would provide those 3rd-party
dependencies packaged as OSGi Bundle in a p2 repository.
In a first time, we could simply create some OSGi "wrappers" around those jars.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira