[jbosstools-issues] [JBoss JIRA] (JBIDE-12505) ensure all JBT SOA components have published exploded update sites on http://download.jboss.org/jbosstools/updates/
Nick Boldt (JIRA)
jira-events at lists.jboss.org
Tue Aug 28 19:05:15 EDT 2012
[ https://issues.jboss.org/browse/JBIDE-12505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
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/switchyard/0.5.0.Final/
Publishes elsewhere, manually symlinked:
* Drools/jbpm5 - JBRULES-3470 - http://download.jboss.org/jbosstools/updates/stable/indigo/soa-tooling/droolsjbpm/5.4.0.Final/
Publishes elsewhere:
* Modeshape Tools - JBBUILD-720, MODE-1506 - http://download.jboss.org/modeshape/builds/staging/modeshape-tools-continuous/ ?
* 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_designer-7.7.0.v20120410-1918-H1074-Final.zip/download
No publishing or archiving strategy (staging only):
* ESB - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk.component--esb/all/repo/
* jbpm3 - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk.component--jbpm/all/repo/
* JBoss BPEL - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk.component--bpel/all/repo/
---
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/switchyard/0.5.0.Final/
Publishes elsewhere, manually symlinked:
* Drools/jbpm5 - JBRULES-3470 - http://download.jboss.org/jbosstools/updates/stable/indigo/soa-tooling/droolsjbpm/5.4.0.Final/
Publishes elsewhere:
* Modeshape Tools - JBBUILD-720, MODE-1506 - http://download.jboss.org/modeshape/builds/staging/modeshape-tools-continuous/ ?
* 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_designer-7.7.0.v20120410-1918-H1074-Final.zip/download
No publishing strategy (staging only):
* ESB - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk.component--esb/all/repo/
* jbpm3 - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk.component--jbpm/all/repo/
* JBoss BPEL - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk.component--bpel/all/repo/
---
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.
> ensure all JBT SOA components have published exploded update sites on http://download.jboss.org/jbosstools/updates/
> -------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-12505
> URL: https://issues.jboss.org/browse/JBIDE-12505
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng, SOA Tooling, updatesite
> Affects Versions: 3.3.0.Final-SOA, 4.0.0.M1-SOA
> Reporter: Nick Boldt
> Assignee: Nick Boldt
>
> 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/switchyard/0.5.0.Final/
> Publishes elsewhere, manually symlinked:
> * Drools/jbpm5 - JBRULES-3470 - http://download.jboss.org/jbosstools/updates/stable/indigo/soa-tooling/droolsjbpm/5.4.0.Final/
> Publishes elsewhere:
> * Modeshape Tools - JBBUILD-720, MODE-1506 - http://download.jboss.org/modeshape/builds/staging/modeshape-tools-continuous/ ?
> * 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_designer-7.7.0.v20120410-1918-H1074-Final.zip/download
> No publishing or archiving strategy (staging only):
> * ESB - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk.component--esb/all/repo/
> * jbpm3 - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk.component--jbpm/all/repo/
> * JBoss BPEL - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk.component--bpel/all/repo/
> ---
> 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
More information about the jbosstools-issues
mailing list