[
https://issues.jboss.org/browse/JBIDE-13835?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-13835:
------------------------------------
Having a source zip for JBDS is a *productization requirement*. They're not required
for projects.
IIRC, we now fetch source zips from github via the SHA of the commit (based on a list of
plugins whose MANIFEST.MF files are checked). These sources are then collected into the
JBT build, and reused in JBDS. We should continue this. cc: [~maxandersen]
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.11#6341)