[
https://issues.jboss.org/browse/JBDS-1998?page=com.atlassian.jira.plugin....
]
Max Rydahl Andersen commented on JBDS-1998:
-------------------------------------------
Im +1, no need to make svn harder to use than it already is.
The important validation/confirmation i'm interested in is that 1.8 works with
previous svn versions and wether you can use this in a mixed environment (servers/teams
are still on svn 1.6, other team members are on 1.7) but yours is on 1.8.
I believe all of that should work fine but I haven't used svn from within in eclipse
in a looong while so I'm not uptodate on what differences there are.
Investigate use of subclipse 1.8 in JBDS 5 and JBoss Central
------------------------------------------------------------
Key: JBDS-1998
URL:
https://issues.jboss.org/browse/JBDS-1998
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.M5
Reporter: Fred Bricon
Assignee: Len DiMaggio
Fix For: 5.0.0.Beta1
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.
--
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