[jboss-jira] [JBoss JIRA] (JBRULES-3470) publish org.drools.updatesite-*-assembly.zip contents to download.jboss.org so it can be used by end-users and linked from JBoss Central

[ https://issues.jboss.org/browse/JBRULES-3470?page=com.atlassian.jira.plug... ] Nick Boldt commented on JBRULES-3470: ------------------------------------- Yes, consistency with your existing project structure is perhaps more important than consistency w/ JBoss Tools conventions. (copied from #droolsdev on codehaus) however, it would be nice to provide a composite site which is always pointing at the latest good build for a given Eclipse version and you can do that regardless of where the ACTUAL bits reside, be they under http://download.jboss.org/drools/release/5.3.2.Final/org.drools.updatesite or http://download.jboss.org/drools/updates/indigo/5.3.2.Final/ there are two benefits here for composite sites... a) users don't have to guess where the next release is, they can just refresh the site and see it now points at 5.3.2 instead of 5.3.1 and just magically get the update b) JBoss Central discovery plugin need no be respun every time a new release comes out; instead, only the composite metadata needs to be updated. and it's dead-simple and doesn't require a build, only publishing a couple xml files for example: http://download.jboss.org/jbosstools/updates/development/indigo/soa-tooli... so step one is "unpack the zip onto download.jboss.org"; step two is "push a couple xml files from git -> download.jboss.org (if you want I can set up a jenkins job to keep the code in github in sync w/ what's on the filesystem so "publishing" requires nothing but a git commit. -- 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