-
Bug
-
Resolution: Done
-
Major
-
4.3.0.Final, 4.4.0.Alpha1
-
None
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) ?
- is cloned by
-
JBIDE-21120 Why do we deploy TP zips to Nexus snapshots repo?
- Closed
- is related to
-
JBIDE-20992 Why is freemarker build failing to deploy to nexus?
- Closed
-
JBIDE-18432 consider refactoring org.jboss.tools.vpe.browsersim_3.6.0 to org.jboss.tools.browsersim_3.7.0
- Closed
- relates to
-
JBIDE-16128 Publish component sites to Nexus
- Reopened