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

Wed Mar 14 05:42:48 EDT 2012

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

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

> Seriously - nothing goes to nexus release before we got these things cleaned up.

What is to clean up? We cannot work on improving the way parent is published and, more important consume by components, if we don't publish it to Nexus. Is your ban also true for SNAPSHOTs?

> About TP -> tell me why other tycho projects uses it over site.xml then ?

I think other Tycho projects are not big enough yet to see drawbacks with target platforms.

>  and composite-update-site is not something you can describe in a mvn project; a TP you can. 

true, but we don't really need this composite update-site for our deps, we prefer an aggregated update site. Tycho allows us to make update-site of ours with more comfortable ways that using TP.

> 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