[
https://issues.jboss.org/browse/JBIDE-22446?page=com.atlassian.jira.plugi...
]
Jeff MAURY commented on JBIDE-22446:
------------------------------------
I meant we should fail only for release builds. This is what the standard maven rule does
by default. We need to be able to use snapshot dependencies in the Dev cycle and any
solution that requires the rule to be skipped is likely to fail. I think the rule can
adapt based on build_alias to skip
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)