[jbosstools-issues] [JBoss JIRA] Created: (JBIDE-7736) Verify pi4soa jobs

Verify pi4soa jobs ------------------ Key: JBIDE-7736 URL: https://jira.jboss.org/browse/JBIDE-7736 Project: Tools (JBoss Tools) Issue Type: Bug Components: pi4soa Affects Versions: 3.2.0.CR1 Reporter: Nick Boldt Assignee: Max Andersen Priority: Trivial I have two builds for pi4soa right now. One pulls from trunk and builds towards a 3.1 release (JBoss Tools CR1 from trunk): http://hudson.qa.jboss.com/hudson/job/jbosstools-pi4soa-3.1_trunk/configure https://pi4soa.svn.sourceforge.net/svnroot/pi4soa/trunk http://anonsvn.jboss.org/repos/jbosstools/trunk/build The other pulls from a stable branch and builds toward a 3.1 release (JBoss Tools 3.2.0.Beta2 from branch): http://hudson.qa.jboss.com/hudson/job/jbosstools-pi4soa-3.1_stable_branch... https://pi4soa.svn.sourceforge.net/svnroot/pi4soa/branches/pi4soa-3.1.x http://anonsvn.jboss.org/repos/jbosstools/branches/jbosstools-3.2.0.Beta2... My questions: Should there be a pi4soa 3.2 trunk build too, like Teiid has with 7.1/7.2 builds? If so, we need to clarify which branches should be used for JBT Beta2 and CR1 builds. If not, nothing to do. Is trunk toward 3.1 or 3.2? If the former, you're fine. If the latter, you need to update your poms and manifests - I didn't see any that were on version 3.2 (or even 3.1.1). -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira