[
https://issues.jboss.org/browse/JBTIS-358?page=com.atlassian.jira.plugin....
]
Mickael Istria commented on JBTIS-358:
--------------------------------------
Do we want those features to be categorized in some p2 repositories?
Overall, I think it's good if we have such features because it turns the marketplace
entries into something that we can define/build/test more easily. However, I'm afraid
that using requires instead of includes makes that updating this feature wouldn't
automatically update it's referenced bundles/features unless we constrain the version
range strictly enough. But constraining the version range of a require would more or less
produce the same issues than using includes.
I'm concerned about the multiplication of features being a potential cause for
installation conflicts, rather than a solution.
Use wrapper features to simplify the install and clean up the
Marketplace UI?
-----------------------------------------------------------------------------
Key: JBTIS-358
URL:
https://issues.jboss.org/browse/JBTIS-358
Project: JBoss Tools Integration Stack
Issue Type: Bug
Components: distribution
Affects Versions: 7.0.3.GA
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 7.1.0.GA-JBDSIS
Attachments: is-marketplace1.png, is-marketplace2.png
For 7.1.0, could consider having wrapper features to simplify the install and clean up
the Marketplace UI. Doing so would mean instead of a laundry list of features in the UI,
we could list only 3 features.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)