[jbosstools-issues] [JBoss JIRA] (JBIDE-18772) Include publish steps in pom files
[
https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-18772:
---------------------------------------
[~mickael_istria], ok, I stand corrected - parent pom has that hardcoded also. You're
right, using nexus would bring some benefits. As discussed previously, I will propose this
on our next meeting (Tuesday).
[~maxandersen] the idea has been and still is that RedDeer is independent of JBoss Tools
and can be used by other projects also. So it has its own git repo also. I think our
perception is that we're still independent, but in reality we're tied to JBoss
Tools in several ways (for example because we need to publish to download.jboss.org).
Include publish steps in pom files
----------------------------------
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.Beta2
Attachments: jbds-publish-to-snapshots.png
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)