[
https://issues.jboss.org/browse/JBTIS-355?page=com.atlassian.jira.plugin....
]
Max Rydahl Andersen commented on JBTIS-355:
-------------------------------------------
I'm not following how creating a com.jboss.devstudio.core.central.feature helps this
situation about having a slimmer central.
The splitting up is a jboss tools level issue, not devstudio.
For me there are two issues:
1) getting the list of toplevel features to install central as it is today
2) looking at cutting down the footprint of these features IF they are found too
excessive.
Is the above devstudio.core feature #1 ? or also #2 ? #1 my belief (at least during f2f
was that this was doable today) , #2 is something we said we would *possibly* look into.
neither of these we need a date for to create the jiras - create the jiras first so they
can be triaged would be better.
Enable JBDSIS Marketplace entries for product groupings - Luna
--------------------------------------------------------------
Key: JBTIS-355
URL:
https://issues.jboss.org/browse/JBTIS-355
Project: JBoss Tools Integration Stack
Issue Type: Feature Request
Components: distribution
Affects Versions: 8.0.0.GA
Reporter: Paul Leacu
Assignee: Nick Boldt
* In JBDS 8.1, add a new com.jboss.devstudio.core.central.feature that packages up
com.jboss.devstudio.core.central plugin;
** include this in com.jboss.devstudio.core.feature instead of the plugin?
* enable usage tracking in JBT IS components' MANIFST.MF files - JBTIS-290
* create three connectors, each based on the content in JBDS IS disco plugin.xml's
top three BIG connectors; include com.jboss.devstudio.core.CENTRAL.feature in order to
install Central along for the ride
(For JBDS 9, we will look at making the Central feature much smaller so the footprint is
significantly smaller - see JBIDE-18734.)
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)