[ https://issues.jboss.org/browse/JBIDE-12505?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-12505: ------------------------------- Description: For each of the JBT SOA components, we should ensure that they're all publishing into standard locations on http://download.jboss.org/jbosstools/updates/. This issue should be a container for child issues assigned to each project's releng person. Done: * SwitchYard - JBIDE-10672 - http://download.jboss.org/jbosstools/updates/stable/indigo/soa-tooling/sw... Publishes elsewhere, manually symlinked: * Drools/jbpm5 - JBRULES-3470 - http://download.jboss.org/jbosstools/updates/stable/indigo/soa-tooling/dr... Publishes elsewhere: * Modeshape Tools - JBBUILD-720, MODE-1506 - http://download.jboss.org/modeshape/builds/staging/modeshape-tools-contin... ? * Savara - http://download.jboss.org/savara/releases/updates/2.0.x/ * pi4soa - http://pi4soa.sourceforge.net/updates/ Publishes as zip only: * Teiid Designer - https://www.jboss.org/teiiddesigner/downloads/ -> http://sourceforge.net/projects/teiid/files/teiid-designer/7.7/teiid_desi... No publishing or archiving strategy (staging only): * ESB - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk.... * jbpm3 - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk.... * JBoss BPEL - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk.... --- Once all the components are publishing sites, they can a) easily link to those individual sites from their download pages on www.jboss.org/{projectname} b) easily composite those sites into a single site and reference that site from www.jboss.org/tools/ c) more easily aggregate the components into a single site & zip, proving that the content can be co-installed via p2 and that there are no unmet or conflicting dependencies d) (with a through c met) therefore provide additional stability checking for JBDS SOA/BRMS tooling, provided individually via JBDS Central. was: For each of the JBT SOA components, we should ensure that they're all publishing into standard locations on http://download.jboss.org/jbosstools/updates/. This issue should be a container for child issues assigned to each project's releng person. Done: * SwitchYard - JBIDE-10672 - http://download.jboss.org/jbosstools/updates/stable/indigo/soa-tooling/sw... Publishes elsewhere, manually symlinked: * Drools/jbpm5 - JBRULES-3470 - http://download.jboss.org/jbosstools/updates/stable/indigo/soa-tooling/dr... Publishes elsewhere: * Modeshape Tools - JBBUILD-720, MODE-1506 - http://download.jboss.org/modeshape/builds/staging/modeshape-tools-contin... ? * Savara - http://download.jboss.org/savara/releases/updates/2.0.x/ * pi4soa - http://pi4soa.sourceforge.net/updates/ Publishes as zip only: * Teiid Designer - https://www.jboss.org/teiiddesigner/downloads/ -> http://sourceforge.net/projects/teiid/files/teiid-designer/7.7/teiid_desi... No publishing strategy (staging only): * ESB - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk.... * jbpm3 - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk.... * JBoss BPEL - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk.... --- Once all the components are publishing sites, they can a) easily link to those individual sites from their download pages on www.jboss.org/{projectname} b) easily composite those sites into a single site and reference that site from www.jboss.org/tools/ c) more easily aggregate the components into a single site & zip, proving that the content can be co-installed via p2 and that there are no unmet or conflicting dependencies d) (with a through c met) therefore provide additional stability checking for JBDS SOA/BRMS tooling, provided individually via JBDS Central. -- 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/JBIDE-12505?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-12505: ------------------------------- Description: For each of the JBT SOA components, we should ensure that they're all publishing into standard locations on http://download.jboss.org/jbosstools/updates/. This issue should be a container for child issues assigned to each project's releng person. Done: * SwitchYard - JBIDE-10672 - http://download.jboss.org/jbosstools/updates/stable/indigo/soa-tooling/sw... Publishes elsewhere, manually symlinked: * Drools/jbpm5 - JBRULES-3470 - http://download.jboss.org/jbosstools/updates/stable/indigo/soa-tooling/dr... Publishes elsewhere: * Modeshape Tools - JBBUILD-720, MODE-1506 - http://download.jboss.org/modeshape/builds/staging/modeshape-tools-contin... ? * Savara - http://download.jboss.org/savara/releases/updates/2.0.x/ * pi4soa - http://pi4soa.sourceforge.net/updates/ Publishes as zip only: * Teiid Designer - https://www.jboss.org/teiiddesigner/downloads/ -> http://sourceforge.net/projects/teiid/files/teiid-designer/7.7/teiid_desi... No publishing or archiving strategy (staging only): * ESB - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk.... * jbpm3 - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk.... --> see also https://issues.jboss.org/browse/JBIDE-12631 * JBoss BPEL - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk.... --- Once all the components are publishing sites, they can a) easily link to those individual sites from their download pages on www.jboss.org/{projectname} b) easily composite those sites into a single site and reference that site from www.jboss.org/tools/ c) more easily aggregate the components into a single site & zip, proving that the content can be co-installed via p2 and that there are no unmet or conflicting dependencies d) (with a through c met) therefore provide additional stability checking for JBDS SOA/BRMS tooling, provided individually via JBDS Central. was: For each of the JBT SOA components, we should ensure that they're all publishing into standard locations on http://download.jboss.org/jbosstools/updates/. This issue should be a container for child issues assigned to each project's releng person. Done: * SwitchYard - JBIDE-10672 - http://download.jboss.org/jbosstools/updates/stable/indigo/soa-tooling/sw... Publishes elsewhere, manually symlinked: * Drools/jbpm5 - JBRULES-3470 - http://download.jboss.org/jbosstools/updates/stable/indigo/soa-tooling/dr... Publishes elsewhere: * Modeshape Tools - JBBUILD-720, MODE-1506 - http://download.jboss.org/modeshape/builds/staging/modeshape-tools-contin... ? * Savara - http://download.jboss.org/savara/releases/updates/2.0.x/ * pi4soa - http://pi4soa.sourceforge.net/updates/ Publishes as zip only: * Teiid Designer - https://www.jboss.org/teiiddesigner/downloads/ -> http://sourceforge.net/projects/teiid/files/teiid-designer/7.7/teiid_desi... No publishing or archiving strategy (staging only): * ESB - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk.... * jbpm3 - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk.... * JBoss BPEL - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk.... --- Once all the components are publishing sites, they can a) easily link to those individual sites from their download pages on www.jboss.org/{projectname} b) easily composite those sites into a single site and reference that site from www.jboss.org/tools/ c) more easily aggregate the components into a single site & zip, proving that the content can be co-installed via p2 and that there are no unmet or conflicting dependencies d) (with a through c met) therefore provide additional stability checking for JBDS SOA/BRMS tooling, provided individually via JBDS Central. -- 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/JBIDE-12505?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-12505: ------------------------------- Description: For each of the JBT SOA components, we should ensure that they're all publishing into standard locations on http://download.jboss.org/jbosstools/updates/. This issue should be a container for child issues assigned to each project's releng person. Done: * SwitchYard - JBIDE-10672 - http://download.jboss.org/jbosstools/updates/stable/indigo/soa-tooling/sw... * Modeshape Tools - JBBUILD-720, MODE-1506 - http://download.jboss.org/jbosstools/updates/development/indigo/soa-tooli... and - http://download.jboss.org/jbosstools/updates/development/juno/soa-tooling... Publishes elsewhere, manually symlinked: * Drools/jbpm5 - JBRULES-3470 - http://download.jboss.org/jbosstools/updates/stable/indigo/soa-tooling/dr... Publishes elsewhere: * Savara - http://download.jboss.org/savara/releases/updates/2.0.x/ * pi4soa - http://pi4soa.sourceforge.net/updates/ Publishes as zip only: * Teiid Designer - https://www.jboss.org/teiiddesigner/downloads/ -> http://sourceforge.net/projects/teiid/files/teiid-designer/7.7/teiid_desi... No publishing or archiving strategy (staging only): * ESB - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk.... * jbpm3 - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk.... --> see also https://issues.jboss.org/browse/JBIDE-12631 * JBoss BPEL - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk.... --- Once all the components are publishing sites, they can a) easily link to those individual sites from their download pages on www.jboss.org/{projectname} b) easily composite those sites into a single site and reference that site from www.jboss.org/tools/ c) more easily aggregate the components into a single site & zip, proving that the content can be co-installed via p2 and that there are no unmet or conflicting dependencies d) (with a through c met) therefore provide additional stability checking for JBDS SOA/BRMS tooling, provided individually via JBDS Central. was: For each of the JBT SOA components, we should ensure that they're all publishing into standard locations on http://download.jboss.org/jbosstools/updates/. This issue should be a container for child issues assigned to each project's releng person. Done: * SwitchYard - JBIDE-10672 - http://download.jboss.org/jbosstools/updates/stable/indigo/soa-tooling/sw... Publishes elsewhere, manually symlinked: * Drools/jbpm5 - JBRULES-3470 - http://download.jboss.org/jbosstools/updates/stable/indigo/soa-tooling/dr... Publishes elsewhere: * Modeshape Tools - JBBUILD-720, MODE-1506 - http://download.jboss.org/modeshape/builds/staging/modeshape-tools-contin... ? * Savara - http://download.jboss.org/savara/releases/updates/2.0.x/ * pi4soa - http://pi4soa.sourceforge.net/updates/ Publishes as zip only: * Teiid Designer - https://www.jboss.org/teiiddesigner/downloads/ -> http://sourceforge.net/projects/teiid/files/teiid-designer/7.7/teiid_desi... No publishing or archiving strategy (staging only): * ESB - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk.... * jbpm3 - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk.... --> see also https://issues.jboss.org/browse/JBIDE-12631 * JBoss BPEL - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk.... --- Once all the components are publishing sites, they can a) easily link to those individual sites from their download pages on www.jboss.org/{projectname} b) easily composite those sites into a single site and reference that site from www.jboss.org/tools/ c) more easily aggregate the components into a single site & zip, proving that the content can be co-installed via p2 and that there are no unmet or conflicting dependencies d) (with a through c met) therefore provide additional stability checking for JBDS SOA/BRMS tooling, provided individually via JBDS Central. -- 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/JBIDE-12505?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-12505: ------------------------------- Description: For each of the JBT SOA components, we should ensure that they're all publishing into standard locations on http://download.jboss.org/jbosstools/updates/. This issue should be a container for child issues assigned to each project's releng person. Most important part of this is the documentation of process / rules / expecations / nomenclature, and creation of tooling to make it simple for project leads to publish & promote their bits: * JBIDE-12220 create generic publishing job which takes as input three parameters Done: * SwitchYard - JBIDE-10672 - http://download.jboss.org/jbosstools/updates/stable/indigo/soa-tooling/sw... * Modeshape Tools - JBBUILD-720, MODE-1506 - http://download.jboss.org/jbosstools/updates/development/indigo/soa-tooli... and - http://download.jboss.org/jbosstools/updates/development/juno/soa-tooling... Publishes elsewhere, manually symlinked: * Drools/jbpm5 - JBRULES-3470 - http://download.jboss.org/jbosstools/updates/stable/indigo/soa-tooling/dr... Publishes elsewhere: * Savara - http://download.jboss.org/savara/releases/updates/2.0.x/ * pi4soa - http://pi4soa.sourceforge.net/updates/ Publishes as zip only: * Teiid Designer - https://www.jboss.org/teiiddesigner/downloads/ -> http://sourceforge.net/projects/teiid/files/teiid-designer/7.7/teiid_desi... No publishing or archiving strategy (staging only): * ESB - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk.... * jbpm3 - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk.... --> see also https://issues.jboss.org/browse/JBIDE-12631 * JBoss BPEL - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk.... --- Once all the components are publishing sites, they can a) easily link to those individual sites from their download pages on www.jboss.org/{projectname} b) easily composite those sites into a single site and reference that site from www.jboss.org/tools/ c) more easily aggregate the components into a single site & zip, proving that the content can be co-installed via p2 and that there are no unmet or conflicting dependencies d) (with a through c met) therefore provide additional stability checking for JBDS SOA/BRMS tooling, provided individually via JBDS Central. was: For each of the JBT SOA components, we should ensure that they're all publishing into standard locations on http://download.jboss.org/jbosstools/updates/. This issue should be a container for child issues assigned to each project's releng person. Done: * SwitchYard - JBIDE-10672 - http://download.jboss.org/jbosstools/updates/stable/indigo/soa-tooling/sw... * Modeshape Tools - JBBUILD-720, MODE-1506 - http://download.jboss.org/jbosstools/updates/development/indigo/soa-tooli... and - http://download.jboss.org/jbosstools/updates/development/juno/soa-tooling... Publishes elsewhere, manually symlinked: * Drools/jbpm5 - JBRULES-3470 - http://download.jboss.org/jbosstools/updates/stable/indigo/soa-tooling/dr... Publishes elsewhere: * Savara - http://download.jboss.org/savara/releases/updates/2.0.x/ * pi4soa - http://pi4soa.sourceforge.net/updates/ Publishes as zip only: * Teiid Designer - https://www.jboss.org/teiiddesigner/downloads/ -> http://sourceforge.net/projects/teiid/files/teiid-designer/7.7/teiid_desi... No publishing or archiving strategy (staging only): * ESB - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk.... * jbpm3 - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk.... --> see also https://issues.jboss.org/browse/JBIDE-12631 * JBoss BPEL - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk.... --- Once all the components are publishing sites, they can a) easily link to those individual sites from their download pages on www.jboss.org/{projectname} b) easily composite those sites into a single site and reference that site from www.jboss.org/tools/ c) more easily aggregate the components into a single site & zip, proving that the content can be co-installed via p2 and that there are no unmet or conflicting dependencies d) (with a through c met) therefore provide additional stability checking for JBDS SOA/BRMS tooling, provided individually via JBDS Central. -- 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/JBIDE-12505?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-12505: ------------------------------- Description: For each of the JBT SOA components, we should ensure that they're all publishing into standard locations on http://download.jboss.org/jbosstools/updates/. This issue should be a container for child issues assigned to each project's releng person. Most important part of this is the documentation of process / rules / expecations / nomenclature, and creation of tooling to make it simple for project leads to publish & promote their bits: * JBIDE-12220 create generic publishing job which takes as input three parameters Done: * SwitchYard - JBIDE-10672 - http://download.jboss.org/jbosstools/updates/stable/indigo/soa-tooling/sw... * Modeshape Tools - JBBUILD-720, MODE-1506 *- http://download.jboss.org/jbosstools/updates/development/indigo/soa-tooli... and *- http://download.jboss.org/jbosstools/updates/development/juno/soa-tooling... Publishes elsewhere, manually symlinked: * Drools/jbpm5 - JBRULES-3470 - http://download.jboss.org/jbosstools/updates/stable/indigo/soa-tooling/dr... Publishes elsewhere: * Savara - http://download.jboss.org/savara/releases/updates/2.0.x/ * pi4soa - http://pi4soa.sourceforge.net/updates/ Publishes as zip only: * Teiid Designer - https://www.jboss.org/teiiddesigner/downloads/ -> http://sourceforge.net/projects/teiid/files/teiid-designer/7.7/teiid_desi... No publishing or archiving strategy (staging only): * SOA Runtime Detection - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk.... * ESB - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk.... * jbpm3 - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk.... --> see also https://issues.jboss.org/browse/JBIDE-12631 * JBoss BPEL - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk.... --- Once all the components are publishing sites, they can a) easily link to those individual sites from their download pages on www.jboss.org/{projectname} b) easily composite those sites into a single site and reference that site from www.jboss.org/tools/ c) more easily aggregate the components into a single site & zip, proving that the content can be co-installed via p2 and that there are no unmet or conflicting dependencies d) (with a through c met) therefore provide additional stability checking for JBDS SOA/BRMS tooling, provided individually via JBDS Central. was: For each of the JBT SOA components, we should ensure that they're all publishing into standard locations on http://download.jboss.org/jbosstools/updates/. This issue should be a container for child issues assigned to each project's releng person. Most important part of this is the documentation of process / rules / expecations / nomenclature, and creation of tooling to make it simple for project leads to publish & promote their bits: * JBIDE-12220 create generic publishing job which takes as input three parameters Done: * SwitchYard - JBIDE-10672 - http://download.jboss.org/jbosstools/updates/stable/indigo/soa-tooling/sw... * Modeshape Tools - JBBUILD-720, MODE-1506 *- http://download.jboss.org/jbosstools/updates/development/indigo/soa-tooli... and *- http://download.jboss.org/jbosstools/updates/development/juno/soa-tooling... Publishes elsewhere, manually symlinked: * Drools/jbpm5 - JBRULES-3470 - http://download.jboss.org/jbosstools/updates/stable/indigo/soa-tooling/dr... Publishes elsewhere: * Savara - http://download.jboss.org/savara/releases/updates/2.0.x/ * pi4soa - http://pi4soa.sourceforge.net/updates/ Publishes as zip only: * Teiid Designer - https://www.jboss.org/teiiddesigner/downloads/ -> http://sourceforge.net/projects/teiid/files/teiid-designer/7.7/teiid_desi... No publishing or archiving strategy (staging only): * ESB - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk.... * jbpm3 - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk.... --> see also https://issues.jboss.org/browse/JBIDE-12631 * JBoss BPEL - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk.... --- Once all the components are publishing sites, they can a) easily link to those individual sites from their download pages on www.jboss.org/{projectname} b) easily composite those sites into a single site and reference that site from www.jboss.org/tools/ c) more easily aggregate the components into a single site & zip, proving that the content can be co-installed via p2 and that there are no unmet or conflicting dependencies d) (with a through c met) therefore provide additional stability checking for JBDS SOA/BRMS tooling, provided individually via JBDS Central. -- 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