[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=13122094#comment-13122094 ] 

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

So the last time that we had successfully deployed to Nexus and the unzip plugin fired to create the unpacked site was on *Thu Nov 13 09:33:23 EST 2014*

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

Not sure why deployment continues but unzipping does not.

---

Found a way to push to Nexus snapshots using a classifier to define the BUILD_ALIAS...

http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-freemarker_master/310/console
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-freemarker_master/ws/sources/site/target/freemarker.site-1.5.100-SNAPSHOT.zip

ends up with:

https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/freemarker/freemarker.site/1.5.100-SNAPSHOT/freemarker.site-1.5.100-20151026.184902-11-Alpha1-v20151026-1848-B310.zip

instead of 

https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/freemarker/freemarker.site/1.5.100-SNAPSHOT/freemarker.site-1.5.100-20151013.204143-6.zip

However, there's nothing in the unzip area:

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



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