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

[Mickael Istria (JIRA)]

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

Mickael Istria edited comment on JBIDE-21012 at 10/26/15 11:37 AM:
-------------------------------------------------------------------

The issue noticed by [~nickboldt] about empty folders on Nexus is a relatively new one. I'm positive on the fact that when the profile was introduced, the zips were attached on Nexus, and the sites were available. Maybe something changed in our conventions or in Tycho to explain the new behaviour.
In any case, as I mentioned above, as long as we keep same Maven version in pom.xml for a year, and for both branch and master, we cannot rely on Nexus for our builds/publishing of snapshot component sites.


was (Author: mickael_istria):
The issue noticed by [~nickboldt] about empty folders on Nexus is a relatively new one. I'm positive on the fact that when the profile was introduced, the zips were attached on Nexus, and the sites were available. Maybe something changed in our conventions or in Tycho to explain the new behaviour.
In any case, as I mentioned above, as long as we keep same Maven version in pom.xml for a year, and for both branch and master, we cannot rely on Nexus for our builds.

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