[jbosstools-issues] [JBoss JIRA] (JBDS-2361) Consider removing com.jboss.jbds.* features from Extras site; keep only 3rd party content in Central site

Nick Boldt (JIRA) jira-events at lists.jboss.org
Sat Nov 10 12:04:17 EST 2012


    [ https://issues.jboss.org/browse/JBDS-2361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733237#comment-12733237 ] 

Nick Boldt edited comment on JBDS-2361 at 11/10/12 12:03 PM:
-------------------------------------------------------------

To put 3rd party stuff on Extras site, we need feature wrappers so that the features can be clearly marked with "Selected" or "Certified" and state that these are "Features selected by Red Hat for use with JBoss Developer Studio." This comes from old requirements JBDS-1836 (JBDS 4) and JBDS-1834 (JBDS 5).

If...
* we are no longer required to label these groups of features in the old way, and 
* can instead ONLY provide them via Central as 3rd party add-ons (regardless of their being "selected" or "certified"), 
* which by definition of what Central is are still "selected by Red Hat for use with JBoss Developer Studio", 

...then 

* we need no longer wrap them with com.jboss.jbds.[featuregroupname].feature, 
* we can remove those features and clean up SVN,
* we can instead replace the connectors in the JBDS Central Discovery plugin's plugin.xml with a list of 3rd party IUs, and
* we can simply mirror the content that's here [1] to a devstudio.jboss.com mirror [2] and link it from the JBDS Central site [3].

[1] http://download.jboss.org/jbosstools/updates/requirements/
[2] https://devstudio.jboss.com/updates/requirements/
[3] https://devstudio.jboss.com/updates/6.0-staging/central/core/

----

For further clarity of purpose and steps, I've renamed this issue to reflect what I was actually talking about:

"Consider removing com.jboss.jbds.* features from Extras site; keep only 3rd party content in Central site"

                
      was (Author: nickboldt):
    
To put 3rd party stuff on Extras site, we need feature wrappers so that the features can be clearly marked with "Selected" or "Certified" and state that these are "Features selected by Red Hat for use with JBoss Developer Studio." This comes from old requirements JBDS-1836 (JBDS 4) and JBDS-1834 (JBDS 5).

If...
* we are no longer required to label these groups of features in the old way, and 
* can instead ONLY provide them via Central as 3rd party add-ons (regardless of their being "selected" or "certified"), 
* which by definition of what Central is are still "selected by Red Hat for use with JBoss Developer Studio", then 

We need no longer wrap them with com.jboss.jbds.[featuregroupname].feature.

In that case, I can simply mirror the content that's here [1] to a devstudio.jboss.com mirror [2] and link it from the JBDS Central site [3].


[1] http://download.jboss.org/jbosstools/updates/requirements/
[2] https://devstudio.jboss.com/updates/requirements/
[3] https://devstudio.jboss.com/updates/6.0-staging/central/core/

----

For further clarity of purpose and steps, I've renamed this issue to reflect what I was actually talking about:

"Consider removing com.jboss.jbds.* features from Extras site; keep only 3rd party content in Central site"

                  
> 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&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12726296 ... 
> 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


More information about the jbosstools-issues mailing list