[
https://issues.jboss.org/browse/JBDS-2001?page=com.atlassian.jira.plugin....
]
Nick Boldt updated JBDS-2001:
-----------------------------
Description:
While updating Indigo Sr2 dependencies, I notice there's now eGit 1.3 builds.
Should we adopt 1.3?
was:
I've been using native svn 1.7 for a while now, Today while reinstalling a new Eclipse
installation from scratch, I installed subclipse from JBoss Central.
After installation, I tried to share my existing projects in eclipse but couldn't,
since the 1.7 checkout is not supported by subclipse (based on svn 1.6).
Can we update the subclipse version from central to use the 1.8.x stream?
With svn 1.7, you have only have one .svn folder at the root of your checkout, no more
.svn folders crawling everywhere making copying and moving folders a breathe.
Affects Version/s: 5.0.0.Beta1
(was: 5.0.0.M5)
Investigate use of egit 1.3 in JBDS 5 and JBoss Central
-------------------------------------------------------
Key: JBDS-2001
URL:
https://issues.jboss.org/browse/JBDS-2001
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Build, central,
updatesite
Affects Versions: 5.0.0.Beta1
Reporter: Fred Bricon
Assignee: Len DiMaggio
Fix For: 5.0.0.Beta1
While updating Indigo Sr2 dependencies, I notice there's now eGit 1.3 builds.
Should we adopt 1.3?
--
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