[
https://issues.jboss.org/browse/JBIDE-13835?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-13835:
---------------------------------------------
The installable source bundles are buildable so I actually think it is enough.
But lets put that aside.
If it is about having "raw sources" why don't our maven builds produce
-source artifacts, just like ordinary maven projects does ? why do we need a separate
github fetching process for this when we already have maven that can do this for us during
build time ?
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)