[ https://issues.jboss.org/browse/JBIDE-22446?page=com.atlassian.jira.plugi... ] 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 -- This message was sent by Atlassian JIRA (v6.4.11#64026)