[jbosstools-issues] [JBoss JIRA] (JBIDE-22446) Release process should disallow inclusion of snapshots artifacts

[Martin Malina (JIRA)]

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

Martin Malina commented on JBIDE-22446:
---------------------------------------

Nope, [~nickboldt], it was not RC1, the dependency was SNAPSHOT - I tried this on August 9 and it was still SNAPSHOT (I checked that). If you look at the repo history you will see that it was changed from SNAPSHOT to RC1 2 days after I tried it:
https://github.com/jbosstools/jbosstools-openshift/commit/9213c7febc4afe37889eb300340ecb24e9a1e60c#diff-3a6d58b27bfc553340813d683a2d8a29L5

But if you're saying that setting -DBUILD_ALIAS from command line won't change a thing, then that's another thing - that would then explain it. I don't see a reason why the command line argument shouldn't be honored just like it is for the rest of maven, but it depends on how hard it is to achieve that.

BTW, I did do the steps you suggested and it worked. And when I reverted the revert (i.e. moved back to RC1 rest client), the build passed as expected. Good to see it works.

> Release process should disallow inclusion of snapshots artifacts
> ----------------------------------------------------------------
>
>                 Key: JBIDE-22446
>                 URL: https://issues.jboss.org/browse/JBIDE-22446
>             Project: Tools (JBoss Tools)
>          Issue Type: Release
>          Components: build
>    Affects Versions: 4.4.0.Alpha2
>            Reporter: Jeff MAURY
>            Assignee: Nick Boldt
>             Fix For: 4.4.1.Final
>
>
> 4.4.0.Alpha2 was generated with a SNAPSHOT dependency. This should be avoided in future releases even for Alpha ones
> Update: This issues is for adding some automated test/check to detect situation when our release includes a snapshot dependency.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)