Short description of how to create an update site refresh: * update feature version, force feature version into plugins (synchronize) * add feature to update site category "PHPEclipse x.y" * build feature from update site editor, you should now have the newly versioned jar files in sub folders * modify feature url in site.xml to point to http://osdn.dl.sourceforge.net/sourceforge/phpeclipse/net.sourceforge.phpeclipse.feature_x.y.z.jar * rename the newly created file features/net.sourceforge.phpeclipse_x.y.z.jar into features/net.sourceforge.phpeclipse.feature_x.y.z.jar (notice the additional .feature in between). This is to avoid file name clashes with the plugin file name as all files go into a single directory afterwards * for each plugin add the following line to the site.xml: * upload all new feature and plugin jars to Sourceforge (as flat file list) * in Sourceforge File Release Manager, create a new active release in hidden package "PHPeclipse update site" * add all uploaded jars to this release, set their file descriptions * upload site.xml via SCP or SFTP to htdocs/update/releases * take a fresh Eclipse runtime and verify by installing from update site differences for creating a CVS update site package: * in feature.xml and site.xml use this update site url: http://phpeclipse.sourceforge.net/update/cvs/ * replace the category "Eclipse x.y" by category "CVS version" in the site.xml * create the file release in the package "PHPeclipse CVS update site" on Sourceforge instead * upload site.xml to htdocs/update/cvs instead