[
https://issues.jboss.org/browse/JBIDE-13835?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-13835:
------------------------------------
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)