[ https://jira.jboss.org/browse/JBIDE-7736?page=com.atlassian.jira.plugin.s... ] Nick Boldt updated JBIDE-7736: ------------------------------ Description: I have two builds for pi4soa right now. One pulls from trunk and builds towards a 3.1 release (JBoss Tools 3.2.0.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). was: 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

[ https://jira.jboss.org/browse/JBIDE-7736?page=com.atlassian.jira.plugin.s... ] Gary Brown commented on JBIDE-7736: ----------------------------------- pi4soa is no longer being developed, so only in maintenance mode - so we don't really need a trunk job. If fixes are necessary, then they will be applied to the 3.1.x branch. In terms of the pom/manifest. I have actually published the current 3.1.x branch to Nexus as 3.1.0.Final - however if the actual poms are changed, then the Tycho build complains about the versions not matching. If you have any thoughts on how best to update the pom to define the 3.1.0.Final version, then if you could let me know. If this can be resolved, then I can create the 3.1.0.Final tag with the correct pom, and the jbosstools hudson jobs can all reference this, until such time as there is any maintanence releases. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-7736?page=com.atlassian.jira.plugin.s... ] Max Andersen updated JBIDE-7736: -------------------------------- Fix Version/s: 3.2.0.CR1 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira