[
https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-18772:
---------------------------------------
[~mickael_istria] integration tests build now works, thanks for that:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBo...
But isn't what you did in
https://github.com/jbosstools/jbosstools-integration-tests/pull/990 basically copying the
whole profile?
Integration tests inherit the parent pom, whereas RedDeer doesn't. Does RedDeer need
anything more than what you did for integration tests?
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)