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

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBIDE-22446:
------------------------------------

Wait... you want different rules when we build a CI build to be released vs. when we build a "normal" CI build? That was never stated in the original problem statement. I assumed that "This should be avoided in future releases even for Alpha ones" meant "for all CI builds".

To achieve what you're asking, we would need a forked version of the parent pom (eg., by creating a 4.4.1.x branch for the 4.4.1.Final code freeze in 4 weeks). 

We could also pass these parameters to Jenkins (eg., <fail>false</fail> for master jobs built from master, <fail>true</fail> for _4.4.neon jobs built from 4.4.1.x branch).

Meanwhile, jbosstools-jst is failing now. Here's the fix:

https://github.com/jbosstools/jbosstools-jst/pull/567



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