[jbosstools-issues] [JBoss JIRA] (JBIDE-11157) Explore publishing parent pom to nexus

Mickael Istria (JIRA) jira-events at lists.jboss.org
Mon Apr 16 12:41:18 EDT 2012


    [ https://issues.jboss.org/browse/JBIDE-11157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12684615#comment-12684615 ] 

Mickael Istria commented on JBIDE-11157:
----------------------------------------

> If parent pom is going to start using 3.3.0.Beta3-SNAPSHOT (in upcoming branch) and 3.3.0.CR1-SNAPSHOT in trunk... we need to reopen this and make the change in trunk, break everyone, and force them to adopt the new version / convention ASAP, as Beta3 code freeze is just around the corner. 

We are not forced to get components using the latest parent. At least, we are not obliged to break everything immediatly. We can first branch "mormally" then change parent pom version, get it pushed on Nexus, and move components parent version later to avoid breaking them.

> Or we could wait and do this at the point where we branch so that both streams will be broken at the same time, causing the most impact but least churn.

Sounds safe.
                
> 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