[jbosstools-issues] [JBoss JIRA] (JBIDE-13209) Need to add ESB 4.12 option with constraints

[Rob Stryker (JIRA)]

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

Rob Stryker commented on JBIDE-13209:
-------------------------------------

> it does not solve the ESB plugin side which still would have to re-released just to support a new updated esb plugin afaics.

Yes you are right, but that is an issue of facets and is up for the esb team to figure out. 

> With your patch here do we even want to have esb 4.12 listed in as core ?

There is no problem with duplicates, one listed in as.core and one listed here.  The situation for future versions would move support for esb 100% outside of as.core, such that the esb plugins (and the attached patch of code or similar) would be in charge of this. 

So it's not a problem for as.core to list 4.12 for now. that was added just in case the esb team doesn't move and get these PR's merged in, as a back-door safety. It's better for completeness, and it certainly doesn't hurt anything. 

So for 4.1 stream, if the patch is accepted, i plan to remove all references to esb from as.core. 
                
> Need to add ESB 4.12 option with constraints
> --------------------------------------------
>
>                 Key: JBIDE-13209
>                 URL: https://issues.jboss.org/browse/JBIDE-13209
>             Project: Tools (JBoss Tools)
>          Issue Type: Task
>          Components: esb
>            Reporter: Tom Cunningham
>            Assignee: Brian Fitzpatrick
>             Fix For: 3.3.2, 4.1.0.Alpha1, 4.0.x
>
>         Attachments: JBIDE-13209.patch
>
>
> SOA-P 5.3.1 is coming out soon and will require an ESB "4.12" option to be added to the ESB versions.  
> Additionally, it may or may not have a new jUDDI version, which would require a different constraint to verify the AS has ESB 4.12 - or a removal of the constraints altogether.

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