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

[Mickael Istria (JIRA)]

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

Mickael Istria commented on JBIDE-16128:
----------------------------------------

[~nickboldt] [~maxandersen] Any reason why not giving a try?

I already expect the following pitfall:
* versioning of p2 sites: p2 sites in component (generally in jbosstools-thing/site/) are sometimes not correctly versioned in the pom.xml, and it can happen that 2 streams have the same version in the pom.xml. So it leads to the fact that those 2 streams will collide and override one and other in Nexus.
This will encourage/force you to think about/manage streams for *components*, which is IMO a good step forward.
                
> 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
>             Fix For: 4.2.0.Alpha1
>
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira