[jbosstools-issues] [JBoss JIRA] (JBIDE-16128) Publish component sites to Nexus
[
https://issues.jboss.org/browse/JBIDE-16128?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-16128:
---------------------------------------------
[~mickael_istria] just so I understood you here - bumping micro between each milestone is
just wrong (why bump micro when the final version haven't been released), so a proper
way to do this would be to stop having to branch for each milestone and simply have a
build/release cut by a developer to get fed into the build. That would work, right ?
Just trying to figure out why so many are happy with the nexus zip publishing but for some
reason it does not work for us.
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.11#6341)