[
https://issues.jboss.org/browse/JBIDE-16128?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-16128:
----------------------------------------
A first drawback of Nexus compared to current publishing mechanism is that current plain
"mvn deploy" don't take into account whether it's necessary to
re-publish stuff (changes in code). However, as some changes can happen independently of
commits (for example build config changing some build options), checking only commits to
decide whether to publish or not seems somehow limited. Ideally what would be cool would
be to re-use Tycho mechanism for replacement, but without enforcing commit-based
timestamps.
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.2.0.Alpha2
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 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