[
https://issues.jboss.org/browse/JBIDE-21012?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-21012:
------------------------------------
Parent poms rebuilt. Browsersim rebuilt, but only deployed to
dl.jb.org. Browsersim
standalone rebuilt and redeployed to Nexus &
dl.jb.org (as expected):
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bro...
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bro...
Also realized we link to the wrong URL in JBT website, so here's a PR for that:
https://github.com/jbosstools/jbosstools-website/pull/526 ( JBIDE-18432 )
Rebuilt Locus here:
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
(update.site-1.5.0-20151120.153147-2.zip dated Fri Nov 20 10:31:49 EST 2015)
https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/lo...
(dated Fri Nov 20 10:31:49 EST 2015)
So... locus and browsersim are still deploying correctly after changes.
Also kicked a freemarker build:
http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-fre...
shows a build B322 from today, yet Nexus is NOT updated (as expected):
https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/fr...
https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/fr...
(nothing new since Nov 15)
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
(nothing new since Nov 15)
So... this is verified working for the 2 cases where Nexus deployment should continue, and
for 2 cases (of >40) where it should not. I'm not going to test the other 38+ cases
since they all use the same parent pom. :D
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) ?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)