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

[Mickael Istria (JIRA)]

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

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

> Why not publish the parent pom at the same time as the JBT TP?

That would make sense. We need to find a nice name for this job.
But since we are not that sure of the future of the target platform, I don't think this effort will be worth it, and I don't see anything annoying in having 2 jobs.

> Do we really need ANOTHER set of jobs (one per stream) for parents?

Either we maintain backward compatibility for build (which means builder in 4.x should be able to build 3.3), either we version and branch our build elements the same way we do for anything else in the project. I am in favor of the 2nd way.
                
> 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