[
https://issues.jboss.org/browse/JBIDE-11157?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-11157:
------------------------------------
The future of the TP will be: there will be a TP for JBT and a second one for JBDS (plus
maybe some others, too, though they could be built as part of the same job - see
JBIDE-10915).
Often, during the Eclipse R/SR1/SR2 cycle, the TP for stable branch will be different from
that of trunk. So we'll always need at least 4 jobs for TP builds.
I'm in favour of each year's stream being different from the previous (and thus no
backward compat between parent poms, as we have today)... I'm just not in favour of
needing to add a pair of new jobs simply to build/deploy the parent pom when it changes
less frequently than the TPs themselves.
You've expressed concern w/ the fact that we have so many little component builds
(which could be built together as "component bundles") ... why not head in that
direction by having the parent/TP built in a single job too?
Max, your thoughts?
Explore publishing parent pom to nexus
--------------------------------------
Key: JBIDE-11157
URL:
https://issues.jboss.org/browse/JBIDE-11157
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.Beta2
Reporter: Nick Boldt
Assignee: Mickael Istria
Fix For: 3.3.0.Beta2
We tried this a year ago and it wasn't very successful, but it's worth
considering it again.
We can use `mvn deploy` to push the parent pom (and perhaps the target platform's
pom) to nexus for reuse by downstream components.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira