Community
Participate
Working Groups
Is: Currently there are 2 branches and 2 corresponding Hudson jobs for Vex at https://hudson.eclipse.org/hudson: origin/vex-release -> cbi-wtp-inc.vex-integration origin/vex-dev -> cbi-wtp-inc.vex-integration Each of the Hudson jobs provides a Software Site URL, e.g. for vex-dev: https://hudson.eclipse.org/hudson/job/cbi-wtp-inc.vex/lastSuccessfulBuild/artifact/sourceediting/development/org.eclipse.wst.xml.vex.repository/target/site The installation of Vex via "Help > Install New Software..." for both update sites fails because of the missing required org.w3c.css.sac plug-in. As workaround this plug-in have to installed manually or the Orbit Software Site must be added (e.g. http://download.eclipse.org/tools/orbit/downloads/drops/S20100831105311/) Should: 1. Installation of Vex should be possible without adding the Orbit Software Site (or installing org.w3c.css.sac manually) 2. The names of the Hudson jobs should correspond to the names of the branches, e.g. origin/vex-release -> wtp-inc.vex-release origin/vex-dev -> wtp-inc.vex-dev 3. The Software Site URLs should be as short as possible, e.g. https://hudson.eclipse.org/hudson/job/wtp-inc.vex-dev/lastSuccessfulBuild/artifact 4. The Software Site of vex-release should be pushed to Eclipse download because of performance reasons (-> Linux Cron job required)
Shouldn't the requirement of org.w3c.css.sac be added into the VEX builds in the same way the WTP build picks up org.mozilla.javascript, org.apache.xerces, etc.?
(In reply to comment #1) > Shouldn't the requirement of org.w3c.css.sac be added into the VEX builds in > the same way the WTP build picks up org.mozilla.javascript, org.apache.xerces, > etc.? Thanks for the hint. The WTP p2 repository (http://download.eclipse.org/webtools/repository/helios/) does not reference the Orbit repository but contains org.mozilla.javascript. Maybe a Composite Repository (see <http://wiki.eclipse.org/Equinox/p2/Composite_Repositories_%28new%29>) which combines the Orbit and the Vex repository could be the solution for (1) and (3).
In Equinox p2 forum asked: "How to include third party bundles into a p2 Update Site?" http://www.eclipse.org/forums/index.php?t=msg&th=197971&start=0&S=e9a4c8cb9368d9f59039c61325183517
CC'ing Dave, the master of Vex builds: Could we include/copy org.w3c.css.sac into the Vex p2 repository?
(In reply to comment #4) > CC'ing Dave, the master of Vex builds: > Could we include/copy org.w3c.css.sac into the Vex p2 repository? Just add the plugin to the the Vex feature, and it'll get included.
I added org.w3c.css.sac to the feature.xml without a restriction on the bundle version. Thus the version which is currently in the Orbit repository will be included in our update site. Until our first release, we should point to https://hudson.eclipse.org/hudson/view/WTP/job/cbi-wtp-inc.vex/lastSuccessfulBuild/artifact/sourceediting/development/org.eclipse.wst.xml.vex.repository/target/site/ in the Eclipse Marketplace. After 1.0M3 we can hopefully point to a more memorizable site on download.eclipse.org... PS: Since Hudson runs behind a proxy, there occasionally occurr 502 errors when Eclipse downloads the bundles from the update site. Just retry until all bundles were successfully downloaded. @Holger: please resolve this bug, if this solution is sufficient for you
Resolving this per the last comment.
done
Moved to Mylyn Docs Vex.
