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

[Max Rydahl Andersen (JIRA)]

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

Max Rydahl Andersen commented on JBIDE-16128:
---------------------------------------------

We don't need to mirror nexus content for stuff that is just for building imo. We can just have a composite referencing the nexus locations. We should test what performance difference there is if any before starting to force mirror.

And Nick, *every* other jboss developer uses nexus to release - we don't because our current setup that you describe is not easy to understand and is very different and mixes various concerns. That is just where we ended up by growing it organically and with focus on release engineering immediate needs, missing a more overall view. We are trying to clean that up.
Experimenting with nexus to make it as easy to do mvn deploy is part of that.

I'm not saying using nexus solves everything but it removes alot of complexity and it becomes clearer which parts does what. 

With respect to next steps - [~mickael_istria] are you just suggesting we enabled mvn deploy towards snapshot repo in jenkins build to see what happens ? 
Not really sure what that will give us that a basic manual mvn deploy would not do ?

I would imagine next step is to fork a few of the components and try see how parent pom and their pom could be setup to consume these nexus urls (or derived composite urls) ?


                
> 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