[
https://issues.jboss.org/browse/JBIDE-13835?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-13835:
------------------------------------
We can hope, but we will be full of fail. We cannot put the EAP bundled installers on
ds.rh.com. So we have two choices:
a) publish everything BUT the EAP bundles (rsync with --exclude)
b) publish only the update sites, and leave all the builds/ on
www.qa
But there's no way the publish script can do the same for JBT and JBDS. At least we
can make the URL patterns more consistent.
Improve publish script (split? Move to maven?)
----------------------------------------------
Key: JBIDE-13835
URL:
https://issues.jboss.org/browse/JBIDE-13835
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: build
Reporter: Mickael Istria
Fix For: 4.1.x, 4.2.x
Publish script deals with a lot of different and not-always-related things. It makes it
difficult to maintain it. We should think about some improvements such as
* different conventions from different stream
* components vs aggregate
* devstudio vs jbosstools.
Or,
* Make publishing part of a "mvn deploy" step.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)