[jbosstools-issues] [JBoss JIRA] (JBIDE-11157) Explore publishing parent pom to nexus
Nick Boldt (JIRA)
jira-events at lists.jboss.org
Mon Apr 16 23:26:17 EDT 2012
[ https://issues.jboss.org/browse/JBIDE-11157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12684741#comment-12684741 ]
Nick Boldt commented on JBIDE-11157:
------------------------------------
Max: read this:
https://svn.jboss.org/repos/devstudio/trunk/documentation/Release_Guide/2012_Release_Branching_For_Milestone.txt
Numerous things change after branching so that the branch builds point at the correct composites / aggregates. This is how we avoid mixing trunk bits into the stable branch builds.
Beyond the parent pom, a lot of other files have to change too. Some in trunk, some in branch.
> 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.Beta3
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Fix For: 3.3.0.Beta3
>
>
> 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
More information about the jbosstools-issues
mailing list