[jbosstools-issues] [JBoss JIRA] (JBIDE-16128) Publish component sites to Nexus

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBIDE-16128:
------------------------------------

But... we DO upversion for each milestone on the branch.

For example... 1.3.1, 1.3.2, 1.3.3 in Forge 4.2.x branch: https://github.com/jbosstools/jbosstools-forge/commits/jbosstools-4.2.x

That said I don't care if we deploy update site to Nexus or not. I'm perfectly happy with the new rsync script for pushing here: http://download.jboss.org/jbosstools/mars/snapshots/builds/

> Publish component sites to Nexus
> --------------------------------
>
>                 Key: JBIDE-16128
>                 URL: https://issues.jboss.org/browse/JBIDE-16128
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: build
>            Reporter: Mickael Istria
>            Assignee: Mickael Istria
>            Priority: Optional
>             Fix For: 4.3.x
>
>         Attachments: deployWithJenkins.png
>
>
> In order to get a first idea of how easy/difficult it would be to rely on Nexus for publication,we could simply start by configuring CI jobs to also run a "mvn deploy" to deploy the output p2 repository onto Nexus.
> Then we'll see what are the pros/cons of this approach.
> Current publication process and locations will be kept. These p2 repo on Nexus won't be consumed by aggregator, at least not until we are sure it's worth it.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)