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

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

Changes pushed to job configurations.
Let's wait for time to do his work and give us ideas on what's to improve (if there's stuff to improve). Example of site created: https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/openshift/openshift.site/2.6.0-SNAPSHOT/openshift.site-2.6.0-SNAPSHOT.zip-unzip/
Note that nothing says it's part of the "master" nor "4.2.luna" stream. If we go for releases the project will have to announce new available versions and all consumers (components, aggregation, product) would have to adapt, similarly to what happens for JBT-IS.
                
> 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.Alpha2
>
>         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 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