[
https://issues.jboss.org/browse/JBIDE-13682?page=com.atlassian.jira.plugi...
]
Victor Rubezhny commented on JBIDE-13682:
-----------------------------------------
I've successfully installed Atlassian 3.2 and Mylyn Issue Tracker Connectors from the
Central into JBDS 7.0.0.Alpha1. When finished the installation I was able to configure the
JBoss Comunity Task Repository, import my issues from
https://issues.jboss.org as Tasks in
Task List and create a new comment on this issue ([See my previous
comment|https://issues.jboss.org/browse/JBIDE-13682?focusedCommentId=1276...]).
I didn't faced any problem while doing it.
What else can I test here?
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+fo...
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