Folks, the jbpm-3.2.6 build fails because it references a jsf-console that is not released | <jbpm.jsf-console.version>3.2.6.GA</jbpm.jsf-console.version> | | [tdiesler@tddell jbpm3]$ ls -1 jsf-console | 3.2.2.GA | 3.3.0.GA | 3.3.1.GA | There is a tag for jsf-console-3.2.6.GA but it actually has a different version and references a 3.3.1-SNAPSHOT which is not used any more | [tdiesler@tddell jsf-console-3.2.6.GA]$ find . -name pom.xml | xargs grep SNAPSHOT | ./pom.xml: <version>3.3.1-SNAPSHOT</version> | ./pom.xml: <jbpm.version>3.3.1-SNAPSHOT</jbpm.version> | ./console/pom.xml: <version>3.3.1-SNAPSHOT</version> | ./jbpm4jsf/pom.xml: <version>3.3.1-SNAPSHOT</version> | ./soa/pom.xml: <version>3.3.1-SNAPSHOT</version> | The hudson box has been hacked to to contain that version. Why? | [hudson@jbpm ~]$ ls -1 ~/.m2/repository/org/jbpm/jbpm3/jsf-console | 3.2.6.GA | 3.3.0.GA | 3.3.1.GA | 3.3.1-SNAPSHOT | All of this is happening at a point of time were we are trying to wrap up a release. Can you please explain what is going on and why do see these unsolicited changes in the first place. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214395#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...