Why do we deploy JBT components to Nexus snapshots repo? -------------------------------------------------------- Key: JBIDE-21012 URL: https://issues.jboss.org/browse/JBIDE-21012 Project: Tools (JBoss Tools) Issue Type: Bug Components: build, updatesite Affects Versions: 4.3.0.Final, 4.4.0.Alpha1 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 Currently, we deploy our x.y.z-SNAPSHOT update sites to the JBoss Nexus snapshots repo. But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just: * eat disk space in Nexus * consume time/resources in Jenkins Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the parent pom for all the projects (except of course Locus and Browsersim Standalone, which would use maven.deploy.skip=false) ?