[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=12676557#comment-12676557 ] 

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

> Please don't use updatesites as TP

Oops, we've been doing that for 2 years now. :)

> we risk those sites to disappear/not be the same

That's why I mirror everything onto download.jboss.org and www.qa servers, and change URLs every time we release a major update to the TP sites. History:

http://download.jboss.org/jbosstools/updates/target-platform/ (3.2.helios version)
http://download.jboss.org/jbosstools/updates/target-platform_3.3.indigo/ (3.3.insigo SR0 version)
http://download.jboss.org/jbosstools/updates/target-platform_3.3.indigo.SR1
http://download.jboss.org/jbosstools/updates/target-platform_3.3.indigo.SR1-M/
http://download.jboss.org/jbosstools/updates/target-platform_3.3.indigo.SR2/

                
> 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