[ https://issues.jboss.org/browse/JBIDE-21012?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21012: ------------------------------------ So... I have no answer here for how to use Nexus for snapshots that don't conflict across the same x.y.z version. And I have no answer for how to publish to the snapshots repo, with automatic unpacking via the unzip plugin, for a deployment which doesn't have -SNAPSHOT in its name. Sure, we could build the update site and call it 4.3.0.Beta5 instead of 4.3.0-SNAPSHOT, but then it gets pushed to the non-public staging Nexus repo for RELEASE (which Jenkins can't directly push to, afaict), not the public snapshots repo. I can currently only think of two possible ways around this: * upversion every time we do a milestone (instead of 4.3.0.Beta1 then 4.3.0.Beta2, we would do 4.3.0 then 4.3.1) * freeze master branch builds until the milestone is built, respun if needed, and released. IMHO neither of these are viable solutions (too much churn, too likely to screw up if a job is accidentally turned back on), so we have no choice but to remove deployment to nexus for JBT component sites. One last option I can see is to figure out a way to convince Jenkins that when it wants to push to /staging/ it REALLY means /snapshots/... perhaps with a Maven config override or settings.xml file? [~mickael_istria] do you know a way to force Maven to push a non-SNAPSHOT versioned artifact to /snapshots/ instead of /staging/ ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)