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

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

{quote}I seriously hope that was not fixed by doing something like 1.5.151-SNAPSHOT.{quote}

It was not. I seriously wish you'd take the time to look in the github repo to assuage your fears instead of asking questions like this.

https://github.com/jbosstools/jbosstools-freemarker/blame/master/pom.xml#L11
https://github.com/jbosstools/jbosstools-freemarker/blame/jbosstools-4.3.x/pom.xml#L11

{quote}None of our other version issue detectors catched that missing bump afaik ? (sic){quote}

It wasn't a missing bump; it was an *INCORRECT* bump (removing -SNAPSHOT). And no, we have no current tooling to check for this particular user error.

Therefore I've opened "Create tool to verify all poms use -SNAPSHOT and manifests/feature.xml use .qualifier" in JBIDE-21132.


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