[jbosstools-issues] [JBoss JIRA] (JBIDE-16128) Publish component sites to Nexus
[
https://issues.jboss.org/browse/JBIDE-16128?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-16128:
----------------------------------------
Actually, we could rely more closely on maven versioning for our component p2 repositories
in order to be able to deploy with Nexus:
https://github.com/mickaelistria/jbosstools-server/commit/5738e9d42035532...
With that, any component p2 repo can be deployed with "mvn deploy" and as long
as people correctly maintain different versions between branch and master (as suggested in
the commit), there is no risk of collision.
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.15#6346)