[
https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-18772:
------------------------------------
{quote}Why do we need to override these things - can't those few ones be customized to
have that set properly ?{quote}
You say "customized" I say "overridden". Same thing - in either case
there's a default in parent pom, and a new value in the special root poms that need
something else. Like we do for jbdevstudio-product/pom.xml, for example.
{quote}About copy-or-rename stuff, we do we even have such step ? why don't we
actually produce what we want/need ? {quote}
Yes. Please re-read all the links to example I provided above, 4 days ago.
https://issues.jboss.org/browse/JBIDE-18772?focusedCommentId=13061673&...
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)