[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:
----------------------------------------
Conclusion on that is that it would require workflow change for a more rigourous version
management. But so far, the "legacy" versioning and publish mechanism has been
working fine and isn't too hard to maintain.
So there is no plan to change that for now. However, the ideas and solutions listed in
this Jira are valuable if we really want to enfore Nexus usage one day.
I'm unassigning and untargeting the issue.
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
Priority: Optional
Fix For: LATER
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.4.11#64026)