[
https://issues.jboss.org/browse/JBIDE-13835?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-13835 at 12/4/14 12:14 PM:
--------------------------------------------------------------
Yes, and if we're OK with "no installers on
devstudio.redhat.com because they go
to GoldenGate/CSP/www.jboss.org" then we can have TWO publishing steps for JBDS:
a) generic "update site publish" script, which also publishes the update site
zip / target platform zips
b) specific-to-JBDS internal only "installer folder publish" script
With the proposed changes in JBDS-3208, making the update site publish script more generic
for both JBT/JBDS/IS will be easier. [~maxandersen] [~mickael_istria] can we get some +1s
and quorum on that? I'd like to start moving stuff around for Mars.
was (Author: nickboldt):
Yes, and if we're OK with "no installers on
devstudio.redhat.com because they go
to GoldenGate/CSP/www.jboss.org" then we can have TWO publishing steps for JBDS:
a) generic "push update site" script, which also publishes the update site zip /
target platform zips
b) specific-to-JBDS internal only "copy build folder w/ installers onto
www.qa"
script
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.3.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)