[
https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-18772:
----------------------------------------
{quote}But isn't what you did in
https://github.com/jbosstools/jbosstools-integration-tests/pull/990 basically copying the
whole profile?{quote}
Yes, and in later commits, I changed it to re-use what is defined in the parent pom. The
change only *adds* an additional deploy steps compared to what is in the parent pom, but
still consume the
deploy-to-jboss.org profile from parent.
{quote}Integration tests inherit the parent pom, whereas RedDeer doesn't. Does RedDeer
need anything more than what you did for integration tests?{quote}
Yes, I believe RedDeer has to copy the
deploy-to-jboss.org profile that is in parent pom.
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.Beta1
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)