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

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBIDE-11157:
------------------------------------

Parent pom [1] only depends on target platform pom [2] (and accompanying .target file(s)), but not the target sites [3], [4]. Thus we can save time/effort/maintenance by having these two artifacts pushed to Nexus via a single job instead of 2.

[1] https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/parent/0.0.4-SNAPSHOT/
[2] https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/org.jboss.tools.target.platform/0.0.2-SNAPSHOT/

[3] http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.target-platform/
[4] http://hudson.qa.jboss.com/hudson/job/devstudio-5.0_trunk.target-platform/


                
> 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