[
https://issues.jboss.org/browse/JBIDE-25455?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-25455:
------------------------------------
m2e is referenced by other features so there's no need to list it explicitly. But
AFAIK, we have nothing that extends or depends on buildship, so we have to list it there
if we want to provide it as an optional install for our users.
As I said in December:
{quote}Note that Buildship was added to JBT and devstudio as an OOTB install via
JBDS-3510, back on May 31, 2017.{quote}
This was an intentional choice. If you feel strongly that JBT should not encourage users
to optionally install Buildship, please address your concerns to [~rpdavis] and
[~jeffmaury].
JBoss Tools marketplace listing includes org.eclipse features
-------------------------------------------------------------
Key: JBIDE-25455
URL:
https://issues.jboss.org/browse/JBIDE-25455
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: marketplace
Affects Versions: 4.5.1.Final
Reporter: Nick Boldt
Assignee: Jeff MAURY
Labels: releasework
Fix For: 4.5.2.Final
Attachments: jbosstools-eclipse-plugins-marketplace.png
Someone added org.eclipse.buildship and org.eclipse.wst.* features to the Marketplace
listing as optional-selected features.
Shouldn't these be installed via requirements from JBT features, and therefore not
needed on the site?
The list of sanctioned features in the CoreTools category on the JBT site is here:
http://download.jboss.org/jbosstools/static/oxygen/stable/updates/core/4....
So... why did the other features get added? And if they SHOULD be there, they should also
be added to the JBT site too, for consistency. Right?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)