[jbosstools-issues] [JBoss JIRA] (JBIDE-13682) Investigate use of Atlassian 3.2 in JBoss Central

[Victor Rubezhny (JIRA)]

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

Victor Rubezhny commented on JBIDE-13682:
-----------------------------------------

This comment is made by using:
- JBoss Developer Studio, Version: 7.0.0.Alpha1, Build id: Alpha1-v20130306-0101-B124, Build date: 20130306-0101 started with the following option: -Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/7.0-development/devstudio-directory.xml due to specify Boss Central Discovery Directory URL
- Atlassian Connector for Eclipse, Version 3.2.0 installed from http://download.jboss.org/jbosstools/updates/requirements/atlassian/3.2.0.v20130212/
- Mylyn Issue Tracker Connectors installed from JBoss Central (The following two software options were excluded: Atlassian Connector for Eclipse Usage Monitoring, Version: 3.0.7.v20121218 and Atlassian JIRA Connector (Recommended), Version: 3.0.7.v20121218)


                
> Investigate use of Atlassian 3.2 in JBoss Central
> -------------------------------------------------
>
>                 Key: JBIDE-13682
>                 URL: https://issues.jboss.org/browse/JBIDE-13682
>             Project: Tools (JBoss Tools)
>          Issue Type: Sub-task
>          Components: central
>    Affects Versions: 4.1.0.Alpha1
>            Reporter: Nick Boldt
>            Assignee: Victor Rubezhny
>             Fix For: 4.1.0.Alpha2
>
>
> Need to evaluate if Atlassian Connector for Eclipse 3.0.7 is compatible w/ Kepler and works the same way as the previous 3.0.6 version, which requires Juno.
> There is also a 3.2 available:
> https://confluence.atlassian.com/display/IDEPLUGIN/Atlassian+Connector+for+Eclipse+-+v3.2+Release+Notes
> available from http://update.atlassian.com/atlassian-eclipse-plugin/rest/e3.6/

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