[
https://issues.jboss.org/browse/JBIDE-11157?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-11157:
------------------------------------
Why not publish the parent pom at the same time as the JBT TP?
https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.target-platfo... (I
added the 'deploy' step a week or two ago; forgot to mention it here.)
Do we really need ANOTHER set of jobs (one per stream) for parents?
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