Details for Uploading Main Rodin Update Site - Revision history

imported>Tommy: /* Remote test and publishing */

2015-05-27T09:06:34Z

Remote test and publishing

← Older revision		Revision as of 09:06, 27 May 2015
Line 117:		Line 117:
	Removing /home/project-web/rodin-b-sharp/htdocs/test-updates/content.jar		Removing /home/project-web/rodin-b-sharp/htdocs/test-updates/content.jar

	Then to finally publish the updated main Rodin Update Site :		'''Then to finally ''publish'' the updated main Rodin Update Site :'''
	* commit 'content.jar' and 'artifacts.jar' to SVN		* commit 'content.jar' and 'artifacts.jar' to SVN (it will update the remote Rodin Update site)
	* test using the standard Rodin Update Site (you may need to reload it)		* test using the standard Rodin Update Site (you may need to reload it)




	== Removing installable units ==		== Removing installable units ==
	In order to remove installable units (features/plugins) from the repository, an Ant script named 'removeFeature.xml' has been created.		In order to remove installable units (features/plugins) from the repository, an Ant script named 'removeFeature.xml' has been created.

imported>Tommy at 09:05, 27 May 2015

2015-05-27T09:05:07Z

← Older revision		Revision as of 09:05, 27 May 2015
Line 70:		Line 70:

	== Remote test and publishing ==		== Remote test and publishing ==

			* test locally, using org.rodinp.updateSite as local update site; in particular, check that other plug-ins on the update site are still listed

			* upload the jars generated by the build as usual in your plugin's area on [http://sourceforge.net/apps/trac/sourceforge/wiki/Release%20files%20for%20download SourceForge FRS]

			* test remotely by uploading 'content.jar' and 'artifacts.jar' to /home/project-web/rodin-b-sharp/htdocs/test-updates on the rodin web space, and using 'http://rodin-b-sharp.sourceforge.net/test-updates' as remote update site (see #Remote test)

	Copy 'content.jar' and 'artifacts.jar' from your eclipse workspace to you user home directory (this just makes it easier to locate the file from the terminal command line since the user home directory is the default local directory in Terminal)		Copy 'content.jar' and 'artifacts.jar' from your eclipse workspace to you user home directory (this just makes it easier to locate the file from the terminal command line since the user home directory is the default local directory in Terminal)
	Open the Terminal utility and enter the following commands replacing <sourceforgeusername> and <sourceforgepassword>:		Open the Terminal utility and enter the following commands replacing <sourceforgeusername> and <sourceforgepassword>:
Line 103:		Line 110:
	and select it.		and select it.

	The .htaccess file redirects plugins/.jar and features/.jar requests to SourceForge FRS, thus using the archives that you have uploaded.<br>		The .htaccess file redirects plugins/.jar and features/.jar requests to [http://sourceforge.net/apps/trac/sourceforge/wiki/Release%20files%20for%20download SourceForge FRS], thus using the archives that you have uploaded.<br>

	'''Once the test is complete, please remove the jars:'''		'''Once the test is complete, please remove the jars:'''
Line 109:		Line 116:
	Removing /home/project-web/rodin-b-sharp/htdocs/test-updates/artifacts.jar		Removing /home/project-web/rodin-b-sharp/htdocs/test-updates/artifacts.jar
	Removing /home/project-web/rodin-b-sharp/htdocs/test-updates/content.jar		Removing /home/project-web/rodin-b-sharp/htdocs/test-updates/content.jar

			Then to finally publish the updated main Rodin Update Site :
			* commit 'content.jar' and 'artifacts.jar' to SVN
			* test using the standard Rodin Update Site (you may need to reload it)




	== Removing installable units ==		== Removing installable units ==

imported>Tommy at 08:33, 27 May 2015

2015-05-27T08:33:35Z

← Older revision		Revision as of 08:33, 27 May 2015
Line 3:		Line 3:

	There are two different ways to update the main Rodin Update site :		There are two different ways to update the main Rodin Update site :
	# using the site.xml file to build an updated version (see [[Details_for_Uploading_Main_Rodin_Update_Site#Using_site.xml]]),		# using the site.xml file to build an updated version of the p2 site (see [[Details_for_Uploading_Main_Rodin_Update_Site#Using_site.xml]]),
	# using a script to update it from your feature repository (see [[Details_for_Uploading_Main_Rodin_Update_Site#Using_an_externally_built_feature]]).		# using a script to update the p2 site from your feature repository (see [[Details_for_Uploading_Main_Rodin_Update_Site#Using_an_externally_built_feature]]).

	If you're interested in internal details, you can take a look at [[How we set up the p2 update site on SourceForge]].<br>		If you're interested in internal details, you can take a look at [[How we set up the p2 update site on SourceForge]].<br>

imported>Tommy at 08:31, 27 May 2015

2015-05-27T08:31:54Z

@@ Line 1: / Line 1: @@
 Since April 5th, 2012, the Rodin update site has the newer p2 format.
 From a release engineer point of view, the main change is that instead of uploading 'site.xml' to the rodin web space, you will just commit 'content.jar' and 'artifacts.jar' to SVN. This page explains how to generate these two files.
 If you're interested in internal details, you can take a look at [[How we set up the p2 update site on SourceForge]].<br>
 There are some [[Details_for_Maintaining_Main_Rodin_Update_Site#Rules_to_follow | few rules to follow when providing contents to the main Rodin update site]], please take a look at them.
 == Using site.xml ==
@@ Line 20: / Line 26: @@
 So 'site.xml' is no more uploaded nor committed to SVN, it is really just there to help working with 'content.jar' and 'artifacts.jar'. In particular, if for some reason you want to commit it nevertheless, take care not to commit the post 'Build' version, as it mixes everything up.
-== Removing installable units ==
+== Using an externally built feature ==
 That's the scripted way to proceed. If you are using scripts to build your feature (that is, without a running eclipse interface):
@@ Line 81: / Line 69: @@
          -categoryDefinition file:/$CAT_FOLDER/category.xml
-== Remote test ==
+== Remote test and publishing ==
 Copy 'content.jar' and 'artifacts.jar' from your eclipse workspace to you user home directory (this just makes it easier to locate the file from the terminal command line since the user home directory is the default local directory in Terminal)
 Open the Terminal utility and enter the following commands replacing <sourceforgeusername> and <sourceforgepassword>:
@@ Line 122: / Line 110: @@
   Removing /home/project-web/rodin-b-sharp/htdocs/test-updates/content.jar
 [[Category:Developer documentation|*Index]]
 [[Category:Rodin Platform|*Index]]

imported>Son: /* Removing installable units */

2013-02-27T23:18:22Z

Removing installable units

← Older revision		Revision as of 23:18, 27 February 2013
Line 21:		Line 21:

	== Removing installable units ==		== Removing installable units ==
	In order to remove installable units from the repository, an Ant script has been created.		In order to remove installable units (features/plugins) from the repository, an Ant script named 'removeFeature.xml' has been created.

	# make sure your workspace copy of the plugin project 'org.rodinp.updateSite' is synchronised with the SVN repository.		# make sure your workspace copy of the plugin project 'org.rodinp.updateSite' is synchronised with the SVN repository.

imported>Son: /* Remote test */

2013-02-27T23:16:32Z

Remote test

← Older revision		Revision as of 23:16, 27 February 2013
Line 103:		Line 103:
	Changing mode on /home/project-web/rodin-b-sharp/htdocs/test-updates/artifacts.jar		Changing mode on /home/project-web/rodin-b-sharp/htdocs/test-updates/artifacts.jar

	As an alternative, you can run ~~the~~ script upload.sh		As an alternative, you can run script 'upload.sh'
	./upload.sh		./upload.sh
	Sourceforge username: <sourceforgeusername>		Sourceforge username: <sourceforgeusername>

imported>Son: /* Remote test */ Added the possibility to use script for uploading

2013-02-27T23:15:58Z

Remote test: Added the possibility to use script for uploading

← Older revision		Revision as of 23:15, 27 February 2013
Line 102:		Line 102:
	sftp> chmod 644 artifacts.jar		sftp> chmod 644 artifacts.jar
	Changing mode on /home/project-web/rodin-b-sharp/htdocs/test-updates/artifacts.jar		Changing mode on /home/project-web/rodin-b-sharp/htdocs/test-updates/artifacts.jar

			As an alternative, you can run the script upload.sh
			./upload.sh
			Sourceforge username: <sourceforgeusername>
			<sourceforgeusername>,rodin-b-sharp@web.sourceforge.net's password: <sourceforgepassword>
			content.jar 100% 155KB 155.1KB/s 00:00
			artifacts.jar 100% 11KB 11.0KB/s 00:00

	You can then try this remote update site from a running Rodin platform.		You can then try this remote update site from a running Rodin platform.

imported>Son: /* Removing installable units */

2013-02-27T23:03:15Z

Removing installable units

← Older revision		Revision as of 23:03, 27 February 2013
Line 36:		Line 36:
	''Tip 1'': If you want to remove all versions of the feature/plugins, just leave out the version number and keep running the Ant script until you see 'Unable to find: Installable Unit [...]' for all features/plugins that you specified		''Tip 1'': If you want to remove all versions of the feature/plugins, just leave out the version number and keep running the Ant script until you see 'Unable to find: Installable Unit [...]' for all features/plugins that you specified

	''Tip 2'': Do ~~not~~ upload 'removeFeature.xml' to SVN (this instruction will be outdated)		''Tip 2'': Do NOT upload 'removeFeature.xml' to SVN (this instruction will be outdated)

	== Externally built feature ==		== Externally built feature ==

imported>Son: /* Removing installable units */

2013-02-27T23:03:02Z

Removing installable units

← Older revision		Revision as of 23:03, 27 February 2013
Line 35:		Line 35:

	''Tip 1'': If you want to remove all versions of the feature/plugins, just leave out the version number and keep running the Ant script until you see 'Unable to find: Installable Unit [...]' for all features/plugins that you specified		''Tip 1'': If you want to remove all versions of the feature/plugins, just leave out the version number and keep running the Ant script until you see 'Unable to find: Installable Unit [...]' for all features/plugins that you specified

	''Tip 2'': Do not upload 'removeFeature.xml' to SVN (this instruction will be outdated)		''Tip 2'': Do not upload 'removeFeature.xml' to SVN (this instruction will be outdated)

imported>Son: /* Removing installable units */

2013-02-27T23:02:48Z

Removing installable units

← Older revision		Revision as of 23:02, 27 February 2013
Line 34:		Line 34:
	# test using the standard Rodin Update Site (you may need to reload it)		# test using the standard Rodin Update Site (you may need to reload it)

	''Tip'': If you want to remove all versions of the feature/plugins, just leave out the version number and keep running the Ant script until you see 'Unable to find: Installable Unit [...]' for all features/plugins that you specified		''Tip 1'': If you want to remove all versions of the feature/plugins, just leave out the version number and keep running the Ant script until you see 'Unable to find: Installable Unit [...]' for all features/plugins that you specified
	''Tip'': Do not upload 'removeFeature.xml' to SVN (this instruction will be outdated)		''Tip 2'': Do not upload 'removeFeature.xml' to SVN (this instruction will be outdated)

	== Externally built feature ==		== Externally built feature ==