- Documentation
Updating the updatesite
Once a release have been build for Ivy or IvyDE, they should be push to the Eclipse updatesite so that Eclipse users will be able to update automatically their installed version of Ivy or IvyDE.
Push the new version
The update site svn location is there: https://svn.apache.org/repos/asf/ant/ivy/site/ivyde/updatesite/- For an Ivy release:
the new ivy bundle have to be placed in the plugins directory of the updatesite. The convention is to name the bundle org.apache.ivy_${BUNDLE-VERSION}.jar.
Eclipse needs a feature, it can be generated at the right place with an ant target. From the build file of the site, run:ant updatesite:generate-ivy-feature -Divy.version=${BUNDLE-VERSION}
- For an IvyDE release:
it contains a plugin and a feature, so they have to be place respectivly in the plugins directory and in the features directory.
And the site.xml file should be edited. The version number should be updated accordingly to the release.
Prepare the update site
The update site is optimized: the metadata of the features are aggregated into the digest.zip, and the jar of the plugins are compressed with a better algorithm.To accomplish this task, from the build file of the site, run:
ant updatesite:optimizeThe binary files then need to be signed and their checksum computed. For the checksums, run:
ant updatesite:checksumTo sign the binaries, you can use the signArtifacts.sh scripts which is in the updatesite directory.
Test the updatesite
The updatesite is ready to be tested. In order to test the new artifacts, as they are not yet deployed on Apache mirrors, the updatesite mirroring have to be disable. Basically it is just about not deploying the eclipse-update--xml files.If you are willing to just test yourself, you can setup in Eclipse a local updatesite. Wherever you want on your local filesystem, make a clone of you working copy of the updatesite directory, but without the eclipse-update--xml files.
To let the developper community test the updatesite, you can copy the new local updatesite without the eclipse-update--xml files to your public_html directory on people.apache.org:
scp -r digest.zip features plugins site.xml LOGIN@people.apache.org:/home/LOGIN/public_html/updatesite
Deployment
Two deployments are needed. One will be part of the website deployment, it will deploy the main updatesite, where there are only the metadata. The second is about pushing the binaries in the Apache dist directory.To deploy the main updatesite, juste regenerate the IvyDE site:
ant generate-site-ivydeand commit the changes of the "target" directory.
For the mirrors udpate site which contains the actual binaries, every binaries have to be copied, with their signatures and checksums, and the site.xml. So on people.apache.org, first do a backup of the current updatesite
mv /www/www.apache.org/dist/ant/ivyde/updatesite /www/www.apache.org/dist/ant/ivyde/updatesite.bakThen we recreate the updatesite:
mkdir /www/www.apache.org/dist/ant/ivyde/updatesiteAnd publish the new updatesite:
cd site/ivyde/updatesite
scp -r digest* plugins features site.xml LOGIN@people.apache.org:/www/www.apache.org/dist/ant/ivyde/updatesite