[
https://issues.jboss.org/browse/JBIDE-22446?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-22446:
------------------------------------
Poms are always SNAPSHOT because we don't ever release them. We only publish p2 sites,
not maven artifacts.
(There are exceptions to this (such as for jbosstools-build-ci or
jbosstools-maven-plugins), but for the jbosstoos-[component-project] repos, this is the
case. Since we ALWAYS use snapshots for parent pom, the default rule will fail.)
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)