[jbosstools-issues] [JBoss JIRA] (JBIDE-15976) forge 2 is not ready/maintained in JBT 4.1 - prepare patches to remove it

Nick Boldt (JIRA) jira-events at lists.jboss.org
Fri Nov 15 11:49:05 EST 2013


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

Nick Boldt commented on JBIDE-15976:
------------------------------------

To clarify [~maxandersen]'s confusion:

JBT update site category.xml, referencing Forge 2 feature:

https://github.com/jbosstools/jbosstools-build-sites/blob/jbosstools-4.1.x/aggregate/site/category.xml#L217

JBDS updte site category.xml, referencing Forge 2 feature (commented out):

https://github.com/jbdevstudio/jbdevstudio-product/blob/jbosstools-4.1.x/site/category.xml#L217

As you can see, they're both on line 217, because I keep these files in sync so it's obvious when things are intentionally excluded (or categorized differently) in JBDS vs. in JBT.

Better?
                
> forge 2 is not ready/maintained in JBT 4.1 - prepare patches to remove it
> -------------------------------------------------------------------------
>
>                 Key: JBIDE-15976
>                 URL: https://issues.jboss.org/browse/JBIDE-15976
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: forge
>            Reporter: Max Rydahl Andersen
>            Assignee: Koen Aers
>             Fix For: 4.1.0.CR1
>
>
> Make sure forge 2 plugins are not mentioned in site/category/features.xml in JBT 4.1.x branch
> work with michael/nick to make sure it is not listed in any higher up aggregations (probably need separate PR)

--
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