[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:all-tabpanel ]

Mickael Istria closed JBIDE-16128.
----------------------------------
    Resolution: Rejected


Since we don't have a versioning practices that matches Maven-style (ie we keep same versions on separate branch and use qualifier to make the distinction), it is conceptually not possible to leverage Nexus for our sites.
If we want to use Nexus, then it means that we'll need to have different version on each branch, ie to bump versions between milestones.

> 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)