]
Nick Boldt closed JBDS-2087.
----------------------------
Verified in jbdevstudio-product-universal-5.0.0.v201205141759M-H140-Beta3.jar (Beta3b)
move all features from com.jboss.jbds.all (generated top-level
product feature) to com.jboss.jbds.product.feature so that all of JBDS can be installed
into Eclipse via a single feature
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBDS-2087
URL:
https://issues.jboss.org/browse/JBDS-2087
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: Build, installer, updatesite, Upstream
Affects Versions: 5.0.0.Beta3
Reporter: Nick Boldt
Assignee: Nick Boldt
Priority: Blocker
Fix For: 5.0.0.Beta3
Attachments: eclipse.log.20120413.txt,
install-jbds5beta3intoEclipseIndigoSR2JEEbundle.png, JBDS2087.patch.txt,
JBDS2087.patch2.txt
A few milestones ago, I moved much of the content of com.jboss.jbds.product.feature into
com.jboss.jbds.all to expose it more obviously when a user looks into Help > About >
Installation details in JBDS.
However, this means that the single point of entry to installing all of JBDS is now
com.jboss.jbds.all, which, because it's a PRODUCT, can't be installed into
something like Eclipse JEE Indigo SR2.
Solution is to move all the contents of com.jboss.jbds.all into its child feature,
com.jboss.jbds.product.feature, and have the .all include ONLY the single
.product.feature.
Any objections to this plan? Denis? Mickael? Max?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: