[jbosstools-issues] [JBoss JIRA] (JBIDE-21012) Why do we deploy JBT components to Nexus snapshots repo?

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-21012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122577#comment-13122577 ] 

Nick Boldt commented on JBIDE-21012:
------------------------------------

One will discard the other. 

20 mins ago, I saw "Latest Build: 1.5.100-SNAPSHOT (Alpha1-v20151026-1942-B311)" in https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/freemarker/freemarker.site/1.5.100-SNAPSHOT/freemarker.site-1.5.100-SNAPSHOT-Alpha1.zip-unzip/index.html and https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/freemarker/freemarker.site/1.5.100-SNAPSHOT/freemarker.site-1.5.100-20151026.194304-12-Alpha1.zip contains that same content: "Latest Build: 1.5.100-SNAPSHOT (Alpha1-v20151026-1942-B311)"

Then I rebuilt with BUILD_ALIAS=Alpha0 to test this theory:

http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-freemarker_master/312/parameters/ (Alpha0)
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-freemarker_master/312/console

{code}
11:47:35 [INFO] Uploaded: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/freemarker/freemarker.site/1.5.100-SNAPSHOT/freemarker.site-1.5.100-20151027.154728-13-Alpha0.zip (2944 KB at 2914.6 KB/sec)
{code}

Now, this URL is 404'd:

https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/freemarker/freemarker.site/1.5.100-SNAPSHOT/freemarker.site-1.5.100-SNAPSHOT-Alpha1.zip-unzip/

and instead we have these:

https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/freemarker/freemarker.site/1.5.100-SNAPSHOT/freemarker.site-1.5.100-SNAPSHOT-Alpha0.zip-unzip/index.html (no longer Alpha1; instead Alpha0)
https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/freemarker/freemarker.site/1.5.100-SNAPSHOT/freemarker.site-1.5.100-SNAPSHOT.zip-unzip/index.html (not sure why this has appeared -- wasn't there when I did an Alpha1 build)



> 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)