[ https://issues.jboss.org/browse/JBRULES-3470?page=com.atlassian.jira.plug... ] Nick Boldt updated JBRULES-3470: -------------------------------- Description: Currently the only ways to get drools/jbpm 5 plugins installed into Eclipse are to: a) download the org.drools.updatesite-*-assembly.zip zip from Nexus, or b) unpack the droolsjbpm-tools-distribution-*.zip linked from http://www.jboss.org/drools/downloads, or c) use the nightly staging site for JBT SOA Tooling http://download.jboss.org/jbosstools/updates/nightly/soa-tooling/trunk/ d) use the nightly staging site for JBDS SOA Tooling http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-5.0_trunk.... Since the JBT site (c) is going away, and (a) and (b) are a relative pain in the butt, we need a new unpacked site, eg., under here: http://download.jboss.org/drools/updates/ or http://download.jboss.org/drools/releases/ ---- For JBoss Tools, the convention we use is: http://download.jboss.org/jbosstools/updates/stable/ (releases) http://download.jboss.org/jbosstools/updates/development/ (milestones and candidate releases) http://download.jboss.org/jbosstools/updates/nightly/ (bleeding edge CI builds) http://download.jboss.org/jbosstools/updates/ (see this page for further discussion of the build types) was: Currently the only ways to get drools/jbpm 5 plugins installed into Eclipse are to: a) download the org.drools.updatesite-*-assembly.zip zip from Nexus, or b) unpack the droolsjbpm-tools-distribution-*.zip linked from http://www.jboss.org/drools/downloads, or c) use the nightly staging site for JBT SOA Tooling http://download.jboss.org/jbosstools/updates/nightly/soa-tooling/trunk/ d) use the nightly staging site for JBDS SOA Tooling http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-5.0_trunk.... Since the JBT site (c) is going away, and (a) and (b) are a relative pain in the butt, we need a new unpacked site, eg., under here: http://download.jboss.org/drools/updates/ or http://download.jboss.org/drools/releases/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBRULES-3470?page=com.atlassian.jira.plug... ] Geoffrey De Smet commented on JBRULES-3470: ------------------------------------------- Can this unpacked update site also be: http://download.jboss.org/drools/release/5.4.0.CR1/org.drools.updatesite http://download.jboss.org/drools/release/5.3.2.Final/org.drools.updatesite ... That would be far more consistent which what we do now. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBRULES-3470?page=com.atlassian.jira.plug... ] Nick Boldt commented on JBRULES-3470: ------------------------------------- patch is here: https://github.com/nickboldt/droolsjbpm-build-distribution pull request is here: https://github.com/droolsjbpm/droolsjbpm-build-distribution/pull/2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBRULES-3470?page=com.atlassian.jira.plug... ] Geoffrey De Smet resolved JBRULES-3470. --------------------------------------- Fix Version/s: 5.4.0.Final Resolution: Done MErged for 5.4.0.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBRULES-3470?page=com.atlassian.jira.plug... ] Nick Boldt commented on JBRULES-3470: ------------------------------------- I see that 5.4.0.Final has a site. http://download.jboss.org/drools/release/5.4.0.Final/org.drools.updatesite/ Can it be linked from https://www.jboss.org/drools/downloads, so the community can find it? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBRULES-3470?page=com.atlassian.jira.plug... ] Nick Boldt commented on JBRULES-3470: ------------------------------------- Drools 5 and jBPM 5 (as well as jBPM 3) are not strictly part of JBoss Tools anymore, so there's little point linking to http://www.jboss.org/tools/download.html as JBoss Tools, once the SOA Tools ships, will provide a link to it from within JBoss Central (that is, if you've installed JBoss Tools you'll be able to discover Drools/jBPM3/jBPM5 right in Eclipse. As to the "you can download the Drools and jBPM tools zip", it's not clear which zip you mean. Perhaps link to it, or reference it using the exact same text as in the table above? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBRULES-3470?page=com.atlassian.jira.plug... ] Geoffrey De Smet commented on JBRULES-3470: ------------------------------------------- Done. Placing a link wasn't possible because it contains the version which changes all the time. Here's the new text: "Click here to go to the Drools and jBPM update site 5.4.0.Final. The Drools and jBPM plugin for Eclipse can also be discovered from JBoss Tools. Alternatively, you can download the "Drools and jBPM tools" zip (from the table above), unzip it and configure the directory "binaries/org.drools.updatesite" as a local updatesite." -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBRULES-3470?page=com.atlassian.jira.plug... ] Nick Boldt edited comment on JBRULES-3470 at 8/28/12 1:33 PM: -------------------------------------------------------------- Would it be possible to symlink your content in http://download.jboss.org/drools/release/5.4.0.Final/org.drools.updatesite/ from http://download.jboss.org/jbosstools/updates/stable/indigo/soa-tooling/dr... ? You can achieve this with some shell script at the end of your publishing job in Jenkins: {code} ECLIPSERELEASE=indigo PROJECTNAME=droolsjbpm SOURCESERVER=tools@filemgmt.jboss.org:/downloads_htdocs SOURCEPATH=/drools/release DESTINATION=tools@filemgmt.jboss.org:/downloads_htdocs/tools/updates/stable/${ECLIPSERELEASE}/soa-tooling PROJECTVERSION=$(echo "ls *.Final" | sftp ${SOURCESERVER}${SOURCEPATH} 2>&1 | grep "\.\+Final" | grep -v sftp | sort | tail -1); PROJECTVERSION=${PROJECTVERSION%%/*}; echo ${PROJECTVERSION} # if folder already exists, sftp will throw an error but should still be able to proceed echo "mkdir ${PROJECTNAME}" | sftp ${DESTINATION} # symlinking appears to only works with relative paths echo "ln ../../../../../..${SOURCEPATH}/${PROJECTVERSION}/org.drools.updatesite ${PROJECTVERSION}" | sftp ${DESTINATION}/${PROJECTNAME}/ echo "Click here: http://download.jboss.org/jbosstools/updates/stable/${ECLIPSERELEASE}/soa... {code} Alternatively, instead of symlink, could also fetch from one site & post to the other (uses twice as much disk space, however) {code} rsync -aPz --rsh=ssh --protocol=28 ${SOURCESERVER}${SOURCEPATH}/${PROJECTVERSION}/org.drools.updatesite/* /tmp/org.drools.updatesite-${PROJECTVERSION} rsync -aPz --rsh=ssh --protocol=28 --delete /tmp/org.drools.updatesite-${PROJECTVERSION}/* ${DESTINATION}/${PROJECTNAME}/${PROJECTVERSION}/ # cleanup rm -fr /tmp/org.drools.updatesite-${PROJECTVERSION} echo "Click here: http://download.jboss.org/jbosstools/updates/stable/${ECLIPSERELEASE}/soa... {code} was (Author: nickboldt): Would it be possible to symlink your content in http://download.jboss.org/drools/release/5.4.0.Final/org.drools.updatesite/ from http://download.jboss.org/jbosstools/updates/stable/indigo/soa-tooling/dr... ? You can achieve this with some shell script at the end of your publishing job in Jenkins: {code} ECLIPSERELEASE=indigo PROJECTNAME=droolsjbpm SOURCESERVER=tools@filemgmt.jboss.org:/downloads_htdocs SOURCEPATH=/drools/release DESTINATION=tools@filemgmt.jboss.org:/downloads_htdocs/tools/updates/stable/${ECLIPSERELEASE}/soa-tooling PROJECTVERSION=$(echo "ls *.Final" | sftp ${SOURCESERVER}${SOURCEPATH} 2>&1 | grep "\.\+Final" | grep -v sftp | sort | tail -1); PROJECTVERSION=${PROJECTVERSION%%/*}; echo ${PROJECTVERSION} # if folder already exists, sftp will throw an error but should still be able to proceed echo "mkdir ${PROJECTNAME}" | sftp ${DESTINATION} # symlinking appears to only works with relative paths echo "ln ../../../../../..${SOURCEPATH}/${PROJECTVERSION}/org.drools.updatesite ${PROJECTVERSION}" | sftp ${DESTINATION}/${PROJECTNAME}/ echo "Click here: http://download.jboss.org/jbosstools/updates/stable/${ECLIPSERELEASE}/soa... {code} Alternatively, instead of symlink, could also fetch from one site & post to the other (uses twice as much disk space, however) {code} rsync -aPz --rsh=ssh --protocol=28 ${SOURCESERVER}${SOURCEPATH}/${PROJECTVERSION}/org.drools.updatesite/* /tmp/org.drools.updatesite-${PROJECTVERSION} rsync -aPz --rsh=ssh --protocol=28 --delete /tmp/org.drools.updatesite-${PROJECTVERSION}/* ${DESTINATION}/${PROJECTNAME}/${PROJECTVERSION}/ # cleanup rm -fr /tmp/org.drools.updatesite-${PROJECTVERSION} {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBRULES-3470?page=com.atlassian.jira.plug... ] Geoffrey De Smet reopened JBRULES-3470: --------------------------------------- Reopining for Nick's extra request, looking at it now -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBRULES-3470?page=com.atlassian.jira.plug... ] Geoffrey De Smet commented on JBRULES-3470: ------------------------------------------- We 've made a script to be used during the release procedure, but it's not being used yet because there are caching problems on download.jboss.org. jbossorg has been notified and they are looking into it -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira