[ https://issues.jboss.org/browse/JBIDE-13232?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-13232 at 12/21/12 1:56 AM: -------------------------------------------------------------- Multiple git repos was never suggested. [~mickael_istria] suggested we move target-platforms/ to its own github repo, but if we did that then jbosstools-build would only have 2 files in it - parent/pom.xml and the checkout.sh script. So... that seems pointless. We could, however, BRANCH the jbosstools-build repo every time there's a new TP definition created, and put that new definition into a separate branch. Or we could simply TAG after each TP is defined, built, and deployed to nexus. BTW, [~maxandersen] when you edited my proposal to cut down the Maven/POM Path lines, you omitted the fact that we moved from snapshots/ to public-jboss/, since the goal here is also to drop the -SNAPSHOT suffix. Still waiting on a +1 to proceed. was (Author: nickboldt): Multiple git repos was never suggested. [~mickael_istria] suggested we move target-platforms/ to its own github repo, but if we did that then jbosstools-build would only have 2 files in it - parent/pom.xml and the checkout.sh script. So... that seems pointless. We could, however, branch the jbosstools-build repo every time there's a new TP definition created, and put that new definition into a separate branch. BTW, [~maxandersen] when you edited my proposal to cut down the Maven/POM Path lines, you omitted the fact that we moved from snapshots/ to public-jboss/, since the goal here is also to drop the -SNAPSHOT suffix. Still waiting on a +1 to proceed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira