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

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

Successfully built and deployed a SNAPSHOT site using -DBUILD_ALIAS_NUM=51 (to synthesize a Beta1):

https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/freemarker/freemarker.site/1.5.151-SNAPSHOT/

And the exploded update site:

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

So... this approach might be doable. 

*{color:red}HOWEVER{color}* ... [~dgolovin] raised a good point here about how aggregation would work for CI builds in master branch while component builds are being replaced by a new build result. Will things break (because the resolved stuff has vanished)? Likely, since there's only one "latest" build available in the /unzip/ URL. So if we do move to this model, it sounds like it might best be used only for building from code freeze branches, NOT from master.



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