[
https://issues.jboss.org/browse/JBDS-2361?page=com.atlassian.jira.plugin....
]
Max Rydahl Andersen commented on JBDS-2361:
-------------------------------------------
No, the Central UI has a certified info field. That is where such things can be put.
And no, I do not see any point in introducing additional sites to expose to the users list
of updatesites - we should not be even exposing stuff like central/core to anyone IMO.
Why not use extras for this ? that is what "extras" is. why need to introduce a
new site for this ?
Whatever site central refer to it is part of the public url's since these sites gets
added to the users list of p2 sites, right?
Consider removing com.jboss.jbds.* features from Extras site; keep
only 3rd party content in Central site
---------------------------------------------------------------------------------------------------------
Key: JBDS-2361
URL:
https://issues.jboss.org/browse/JBDS-2361
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Build, central, updatesite
Affects Versions: 6.0.0.Beta1
Reporter: Nick Boldt
Assignee: Max Rydahl Andersen
Fix For: 6.0.0.CR1
As per
https://issues.jboss.org/browse/JBDS-2284?focusedCommentId=12726296&p...
...
we can now look at eliminating the remaining JBDS Extras features, and keeping the
contents therein only in Central:
{quote}
* TestNG
* SpringIDE
* Mylyn
* Git.Mylyn
* Eclipse-CS
* GWT
* GWT.Designer
* Subclipse
* Subclipse.Mylyn
* com.jboss.jbds.m2e.extras (JBoss Tools Maven Integration plugins for GWT and JBoss
Packaging)
{quote}
Assigned to Max for comment then back to me to do the work.
--
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