[
https://issues.jboss.org/browse/JBIDE-22446?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-22446:
------------------------------------
[~jeffmaury] A custom rule is needed because we only want to prevent use of SNAPSHOT deps
for Final/GA releases; they're fine for Alphas/Betas (or else there wouldn't be
openshift-rest-client 5.0.0-SNAPSHOT being used in master branch right now!).
The default rule would require changing poms every time we moved from an AMx milestone to
a Final/GA. This introduces less overhead for devs since the rule need not be changed
every 4 sprints.
[~mickael_istria] Yes, it could live in jbosstools-maven-plugins repo if you'd prefer
it there. Any other refactoring suggestions?
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)