Switch from CVS to Subversion - Revision history

imported>Laurent: /* How to Access the Repository from Eclipse */ Added recommendation for subclipse

2009-04-01T09:37:41Z

How to Access the Repository from Eclipse: Added recommendation for subclipse

← Older revision		Revision as of 09:37, 1 April 2009
Line 5:		Line 5:
	==How to Access the Repository from Eclipse==		==How to Access the Repository from Eclipse==

	To access the subversion repository, you need to install a Subversion plug-in into your Eclipse development platform. There is currently two plug-ins that are known to work quite well: [http://subclipse.tigris.org/ Subclipse] and [http://www.eclipse.org/subversive/ Subversive]. We ~~do not~~ recommend ~~yet which plug-in~~ to use~~, but experience will tell~~. ~~What is currently known is that it~~ would be a bad idea to install both plug-ins in the same platform as they conflict with each other.		To access the subversion repository, you need to install a Subversion plug-in into your Eclipse development platform. There is currently two plug-ins that are known to work quite well: [http://subclipse.tigris.org/ Subclipse] and [http://www.eclipse.org/subversive/ Subversive]. We recommend to use Sublipse. It would be a bad idea to install both plug-ins in the same platform as they conflict with each other.

	The repository itself is available at URL [https://rodin-b-sharp.svn.sourceforge.net/svnroot/rodin-b-sharp https://rodin-b-sharp.svn.sourceforge.net/svnroot/rodin-b-sharp].		The repository itself is available at URL [https://rodin-b-sharp.svn.sourceforge.net/svnroot/rodin-b-sharp https://rodin-b-sharp.svn.sourceforge.net/svnroot/rodin-b-sharp].

imported>Laurent: /* Where Are my Modules */ Added Brama directory

2009-03-24T15:51:30Z

Where Are my Modules: Added Brama directory

← Older revision		Revision as of 15:51, 24 March 2009
Line 71:		Line 71:
	org.animb.updatesite		org.animb.updatesite
	org.animb.valuation		org.animb.valuation
			and the following modules have been moved to the new <tt>Brama</tt> directory:
			com.clearsy.animator.core
			com.clearsy.animator.core.eclipseBuilder
			com.clearsy.predicateB
			com.clearsy.predicateB.tests

	==How to Move from CVS to Subversion==		==How to Move from CVS to Subversion==

imported>Laurent: Added section "Where Are my Modules"

2009-03-14T00:12:30Z

Added section "Where Are my Modules"

← Older revision		Revision as of 00:12, 14 March 2009
Line 8:		Line 8:

	The repository itself is available at URL [https://rodin-b-sharp.svn.sourceforge.net/svnroot/rodin-b-sharp https://rodin-b-sharp.svn.sourceforge.net/svnroot/rodin-b-sharp].		The repository itself is available at URL [https://rodin-b-sharp.svn.sourceforge.net/svnroot/rodin-b-sharp https://rodin-b-sharp.svn.sourceforge.net/svnroot/rodin-b-sharp].

			==Where Are my Modules==

			Just after the switch from CVS to Subversion, certain CVS modules have been moved to clean up the root of the repository. The modules below have been moved to the new <tt>RodinCore</tt> directory:
			fr.systerel.explorer
			fr.systerel.explorer.tests
			org.eventb.core
			org.eventb.core.ast
			org.eventb.core.ast.tests
			org.eventb.core.seqprover
			org.eventb.core.seqprover.doc.isv
			org.eventb.core.seqprover.tests
			org.eventb.core.tests
			org.eventb.doc.user
			org.eventb.eventBKeyboard
			org.eventb.eventBKeyboard.tests
			org.eventb.ide
			org.eventb.ide-feature
			org.eventb.pp
			org.eventb.pp.tests
			org.eventb.pp.ui
			org.eventb.pptrans
			org.eventb.pptrans.tests
			org.eventb.ui
			org.eventb.ui.icons
			org.eventb.ui.tests
			org.rodinp
			org.rodinp-feature
			org.rodinp.core
			org.rodinp.core.tests
			org.rodinp.platform
			org.rodinp.platform-feature
			org.rodinp.releng
			and the following modules have been moved to the new <tt>XProver</tt> directory:
			org.eventb.xprover.tptp.core
			org.eventb.xprover.tptp.core.tests
			org.eventb.xprover.tptp.spass.core
			org.eventb.xprover.tptp.spass.core.linux
			org.eventb.xprover.tptp.spass.core.macosx
			org.eventb.xprover.tptp.spass.core.tests
			org.eventb.xprover.tptp.spass.ui
			org.eventb.xprover.tptp.ui
			and the following modules have been moved to the new <tt>AnimB</tt> directory:
			org.animb.animation.stubclient
			org.animb.core
			org.animb.core.tests
			org.animb.eclipseBuilder
			org.animb.eclipseBuilder.test
			org.animb.eventsexecutor
			org.animb.export
			org.animb.feature
			org.animb.feature-def
			org.animb.history
			org.animb.ipConnectionTest
			org.animb.ipconnection
			org.animb.ipconnectionplugin
			org.animb.observer
			org.animb.server
			org.animb.serverplugin
			org.animb.site
			org.animb.ui.utils
			org.animb.updatesite
			org.animb.valuation

	==How to Move from CVS to Subversion==		==How to Move from CVS to Subversion==

imported>Laurent: Finished procedure

2009-03-13T22:31:05Z

Finished procedure

← Older revision		Revision as of 22:31, 13 March 2009
Line 18:		Line 18:

	When switching from CVS to Subversion, we made our best to keep the history of all files. We followed this procedure:		When switching from CVS to Subversion, we made our best to keep the history of all files. We followed this procedure:
	# retrieve a copy of the whole CVS repository into directory <tt>cvs</tt>		<ol>
	# launch commands		<li>retrieve a copy of the whole CVS repository into directory <tt>cvs</tt></li>
			<li>launch commands</li>
	cvs2svn -q --dumpfile=svndump --force-tag=GMF2 --encoding=utf-8 --encoding=latin1 cvs		cvs2svn -q --dumpfile=svndump --force-tag=GMF2 --encoding=utf-8 --encoding=latin1 cvs
	svndumpfilter exclude CVSROOT < svndump > svndump2		svndumpfilter exclude CVSROOT < svndump > svndump2
	gzip -9 svndump2		gzip -9 svndump2
	# upload file <tt>svndump2.gz</tt> to SourceForge		<li>upload file <tt>svndump2.gz</tt> to SourceForge</li>
	~~# {{TODO~~\|~~finish procedure}}~~		<li>start a shell service on SourceForge and type the following commands</li>
			adminrepo --checkout svn
			zcat svndump2.gz \| svnadmin load /svnroot/rodin-b-sharp
			adminrepo --save svn
			</ol>

			Note that the filtering on <tt>CVSROOT</tt> didn't seem to work as expected: this directory still occurred in the SVN trunk and had to be removed manually.

	[[Category:Developer documentation]]		[[Category:Developer documentation]]
	[[Category:Rodin Platform]]		[[Category:Rodin Platform]]

imported>Laurent: Initial release, procedure not yet complete

2009-03-13T19:05:48Z

Initial release, procedure not yet complete

New page

{{TOCright}}

The switch from CVS to Subversion took place Friday 13 March 2009. Before this date, all source code used to be managed in a CVS repository hosted by SourceForge. After this date, source code is managed in a Subversion repository also hosted by SourceForge.

==How to Access the Repository from Eclipse==

To access the subversion repository, you need to install a Subversion plug-in into your Eclipse development platform. There is currently two plug-ins that are known to work quite well: [http://subclipse.tigris.org/ Subclipse] and [http://www.eclipse.org/subversive/ Subversive]. We do not recommend yet which plug-in to use, but experience will tell. What is currently known is that it would be a bad idea to install both plug-ins in the same platform as they conflict with each other.

The repository itself is available at URL [https://rodin-b-sharp.svn.sourceforge.net/svnroot/rodin-b-sharp https://rodin-b-sharp.svn.sourceforge.net/svnroot/rodin-b-sharp].

==How to Move from CVS to Subversion==

The simpler is to create a second workspace on your computer and to launch two Eclipse programs, one on each workspace. For each project checked out in the CVS workspace, just checkout the same project in the Subversion workspace.

If you have some yet uncommitted changes in your CVS workspace, you can select the files and drag and drop them in the appropriate place in the Subversion workspace. Alternatively, you can create a patch. For that, select the project(s) that contain uncommitted changes, then select {{menu|Team > Create Patch...}} from the context menu and follow the wizard. Then, in the Subversion workspace, select {{menu|Team > Apply Patch...}} to apply the patch.

==Procedure Used for Moving CVS History to Subversion==

When switching from CVS to Subversion, we made our best to keep the history of all files. We followed this procedure:
# retrieve a copy of the whole CVS repository into directory <tt>cvs</tt>
# launch commands
cvs2svn -q --dumpfile=svndump --force-tag=GMF2 --encoding=utf-8 --encoding=latin1 cvs
svndumpfilter exclude CVSROOT < svndump > svndump2
gzip -9 svndump2
# upload file <tt>svndump2.gz</tt> to SourceForge
# {{TODO|finish procedure}}

[[Category:Developer documentation]]
[[Category:Rodin Platform]]