[jbosstools-issues] [JBoss JIRA] (JBDS-2280) Investigate use of SpringIDE 2.7.2 or 3 in JBoss 6 Central & JBDS Extras sites

[Nick Boldt (JIRA)]

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

Nick Boldt edited comment on JBDS-2280 at 11/23/12 11:12 AM:
-------------------------------------------------------------

Going to assume that means JBDS 6 Central should include 2.7.2, and have spawned a second JIRA to deal w/ Spring IDE 3.x in JBDS 6.x Central:

a) Investigate use of SpringIDE 2.7.2 in JBoss 6.0.0 Central - JBDS-2280
b) Investigate use of SpringIDE 3.x in JBoss 6.x Central - JBDS-2395
                
      was (Author: nickboldt):
    OK, so ... does that mean Central should include 2.7.2, or include nothing? Maybe we need two jiras here:

a) Investigate use of SpringIDE 2.7.2 in JBoss 6 Central
b) Investigate use of SpringIDE 3.x in JBoss 6.x Central
                  
> Investigate use of SpringIDE 2.7.2 or 3 in JBoss 6 Central & JBDS Extras sites
> ------------------------------------------------------------------------------
>
>                 Key: JBDS-2280
>                 URL: https://issues.jboss.org/browse/JBDS-2280
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: 3rdPartyCertification, 3rdPartyDependencies, central
>    Affects Versions: 6.0.0.Alpha1
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>            Priority: Blocker
>              Labels: respin-a
>             Fix For: 6.0.0.CR1
>
>
> Spring IDE update site (http://dist.springsource.com/release/TOOLS/update/e4.2) contains this version:
>     Spring IDE Core (required)	3.0.0.201208090952-RELEASE
> Bits are mirrored here:
> http://download.jboss.org/jbosstools/updates/requirements/springide/3.0.0.201208090952-RELEASE/

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