[
https://issues.jboss.org/browse/JBIDE-16128?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-16128:
----------------------------------------
{quote}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 ?{quote}
Yes, avoiding to avoid several active branch with the same version would allow to use
Nexus. This pattern of branching a still active branch to do a milestone is what prevents
Nexus to work for us.
{quote}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. {quote}
Those projects don't have 2 branches with the same version, and prefer a tag-after
based approach rather than a branch-before model.
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)