[ https://issues.jboss.org/browse/JBIDE-21120?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21120: ------------------------------- Description: Currently, we deploy our TP update sites to the JBoss Nexus snapshots repo. {code} Uploading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... Uploading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... Uploading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... Uploading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... Uploading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... Uploading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... ... {code} 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 jbosstools-targetplatform & jbosstools-discovery root pom to prevent this waste of time/space? was: 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) ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)