[
https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-18772:
---------------------------------------------
I reread the links the last time, I also reread them again and I still have the same
question.
About copy-or-rename stuff, we do we even have such step ? why don't we actually
produce what we want/need ?
The links just shows to me how we currently are doing it which seems to be there just
because thats what its been like in the past, not because its the simplest and most
maintainable way.
Include publish.sh in parent pom as versioned maven dependency
--------------------------------------------------------------
Key: JBIDE-18772
URL:
https://issues.jboss.org/browse/JBIDE-18772
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: build
Reporter: Max Rydahl Andersen
Assignee: Mickael Istria
Priority: Critical
Fix For: 4.3.0.Beta1
instead of relying to publish.sh being on master, we should use a versioned publish.sh
(or maybe even mojo) that the build then uses.
suggestion:
publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform
publishing.
What this helps with is:
a) can do changes to publish mechanism without affecting every past builds.
b) more movable build system
c) isolated testing possible
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)