[
https://jira.jboss.org/jira/browse/JBIDE-5318?page=com.atlassian.jira.plu...
]
Nick Boldt commented on JBIDE-5318:
-----------------------------------
FYI, you don't strictly have to have your sources in the same repo as the rest of JBT.
For example, pi4soa is built from sources hosted on
sourceforge.net.
Do you need to retain history? (I would guess yes.)
Does SVN have tools for cloning trees between disparate repos? (I assume so, but do they
retain history?)
And when would you want to do this migration? Is there a "shutdown" window
during which time you can safely do the copy and tell all your devs to use the new repo?
Perhaps between Dec 25 and Jan 01? Will you be responsible for notification of the change
so that your team will all be able to continue work in the new repo (after a fresh
workspace checkout, of course).
---
Perhaps instead of moving DNA, you only move the Eclipse plugins (as per jira DNA-564) ?
Then you can build the runtime, and the Eclipse plugins can be built downstream from that
(ultimately as part of JBoss Tools). Does that make sense?
Move Eclipse-based client DNA publishing projects to JBoss Tools SVN
--------------------------------------------------------------------
Key: JBIDE-5318
URL:
https://jira.jboss.org/jira/browse/JBIDE-5318
Project: Tools (JBoss Tools)
Issue Type: Task
Components: Build/Releng
Reporter: Johnny Verhaeg
Assignee: Nick Boldt
The Eclipse-based client DNA publishing projects, currently hosted under
https://svn.jboss.org/repos/dna/trunk/tools, need to be ported over to the JBoss Tools SVN
repository (and removed from DNA's SVN repository) and included in the JBoss Tools
build and distribution process.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira