Community
Participate
Working Groups
http://www.eclipse.org/bpmn/ -> click "STP update site" -> http://download.eclipse.org/stp/updates/site.xml -> 404. Actual URL is here: http://download.eclipse.org/stp/updates/helios/ or http://download.eclipse.org/stp/updates/2.1.0/ But because you have no composite site metadata in the updates/ folder, users get a 404 and "no update site found" Metadata is really simple to create. Here's a sample I've used to collect a couple of remote sites into one. Works with relative paths too: http://download.jboss.org/jbosstools/updates/helios/compositeContent.xml http://download.jboss.org/jbosstools/updates/helios/compositeArtifacts.xml Just put files like those in the ~/downloads/stp/updates/ folder and you can redirect users' Eclipse instances to the correct subfolder automatically.
Hi Nick. Thanks for the report. We are familiar with p2 and the composite repository and what you are looking at is an old build system from before those days. Antoine, Oisin, I don't have the write permissions to create the composite repository.
BPMN has been terminated and archived. Marking as WONTFIX.
