[jbosstools-issues] [JBoss JIRA] (JBIDE-16128) Publish component sites to Nexus
Mickael Istria (JIRA)
issues at jboss.org
Mon May 19 08:40:57 EDT 2014
[ https://issues.jboss.org/browse/JBIDE-16128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mickael Istria updated JBIDE-16128:
-----------------------------------
Fix Version/s: 4.3.x
(was: 4.2.0.Beta2)
Delaying this as it's more something that we should try to adapt very early in the lifecycle of a release.
> 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.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.2.3#6260)
More information about the jbosstools-issues
mailing list