[
https://issues.jboss.org/browse/JBIDE-16126?page=com.atlassian.jira.plugi...
]
Mickael Istria closed JBIDE-16126.
----------------------------------
Resolution: Duplicate Issue
Dup of JBIDE-16128
Publish component sites to Nexus
--------------------------------
Key: JBIDE-16126
URL:
https://issues.jboss.org/browse/JBIDE-16126
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