[
https://issues.jboss.org/browse/JBDS-2221?page=com.atlassian.jira.plugin....
]
Lucia Jelinkova commented on JBDS-2221:
---------------------------------------
The following scenario is very confusing.
# User installs JBDS 5.0.0
# User installs from extras Mylyn + Subclipse
# User uses Mylyn <-> SVN integration
# User updates to 5.0.1
RESULT: The Mylyn <-> SVN integration stops working, the solution is to install new
feature containing just the integration.
This should be at least documented somewhere.
@Nick I think that Jiras changing features and plugins on extra site should be verified
and closed by QA in the future.
remove mylyn from com.jboss.jbds.subclipse.feature; move into new
com.jboss.jbds.subclipse.mylyn.feature
--------------------------------------------------------------------------------------------------------
Key: JBDS-2221
URL:
https://issues.jboss.org/browse/JBDS-2221
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: 3rdPartyDependencies, central
Affects Versions: 5.0.0.GA
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 5.0.1.GA
Attachments: JBDS2219_JBDS2220_JBDS2221.snap.png, JBDS2221-50x.patch,
JBDS2221-trunk.patch
TODO:
[fix for 5.0.1] com.jboss.jbds.subclipse.feature (Selected) --> includes
org.tigris + svnkit (no mylyn)
[fix for 5.0.1] com.jboss.jbds.subclipse.mylyn.feature (Selected) --> includes
mylyn for svn (depends on com.jboss.jbds.subclipse.feature)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira