Difference between revisions of "How we set up the p2 update site on SourceForge"

From Event-B
Jump to navigationJump to search
imported>Nicolas
(New page: {{TODO}})
 
imported>Nicolas
Line 1: Line 1:
{{TODO}}
+
= Core P2 Update Site =
 +
 
 +
== Redirecting Web to FRS ==
 +
 
 +
We are using the project web on SF as the entry point for our update site
 +
<pre>
 +
http://rodin-b-sharp.sourceforge.net/core-updates
 +
</pre>
 +
 
 +
In the 'core-updates' directory, we put a single '.htaccess' file:
 +
<pre>
 +
RewriteEngine On
 +
RewriteRule (.*) http://sourceforge.net/projects/rodin-b-sharp/files/Core_Update_Site/$1/download [L]
 +
</pre>
 +
that redirects all requests to the FRS.
 +
 
 +
== Storing Update Site on FRS ==
 +
 
 +
The 'Core_Update_Site' directory in the FRS contains the update site, with its usual contents:<br/>
 +
artifacts.jar  binary        content.jar    features      plugins
 +
 
 +
When we produce a new version of the update site, we simply replace the files in this directory

Revision as of 15:18, 17 January 2014

Core P2 Update Site

Redirecting Web to FRS

We are using the project web on SF as the entry point for our update site

http://rodin-b-sharp.sourceforge.net/core-updates

In the 'core-updates' directory, we put a single '.htaccess' file:

RewriteEngine On
RewriteRule (.*) http://sourceforge.net/projects/rodin-b-sharp/files/Core_Update_Site/$1/download [L]

that redirects all requests to the FRS.

Storing Update Site on FRS

The 'Core_Update_Site' directory in the FRS contains the update site, with its usual contents:
artifacts.jar binary content.jar features plugins

When we produce a new version of the update site, we simply replace the files in this directory