[
https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-18772:
----------------------------------------
{quote}Alternatively, we could start rewriting rsync.sh as some-kinda-deployment-mojo and
jbosstools-cleanup.sh as some-kinda-cleanup-mojo. More work but ultimately way more
portable.{quote}
Yes. Let's just try to consume the scripts from pom.xml for now, and once they're
working, a next iteration would be to turn them into mojos.
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: Feature Request
Components: build
Reporter: Max Rydahl Andersen
Assignee: Mickael Istria
Fix For: 4.3.0.Alpha2
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.11#6341)