[jbosstools-issues] [JBoss JIRA] (JBIDE-13308) Remove cascading and rename trunk jobs to follow new naming scheme

[ https://issues.jboss.org/browse/JBIDE-13308?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13308: ------------------------------------ (2013-01-31 15:43:53) nickboldt: <project>_<version>_<qualifier><more metadata> (2013-01-31 15:52:47) maxandersen: my suggestion was simply jbt-<component>-<stream>-<what> {code} jbt-hibernatetools_41 (unclear if that's hibernatetools 4.1, for hibernate 4.1, or as part of jbt 4.1) jbt-hibernatetools_master (won't have to rename it after we split off 4.1.x branch) jbt-javaee_41 jbt-javaee_master jbt-central_41 jbt-central_master etc. {code} Or we could do this, which maps to the github project name, minus the "jbosstools-" prefix, and uses the shortest possible suffix to define the stream, assuming that if no version is stated, it's from master branch: {code} hibernatetools_jbt41 (won't have to rename it for every milestone) hibernatetools_jbt (won't have to rename it after we split off 4.1.x branch) javaee_jbt41 javaee_jbt central_jbt41 central_jbt and jbosstools.flow{1-5}_jbt41 - looking at having 5 sequential flow jobs. See JBIDE-12850 #comment-12751438) jbosstools.flow{1-5} jbosstools.core.aggregate_jbt41 jbosstools.core.aggregate jbosstools.webtools.aggregate_jbt41 jbosstools.webtools.aggregate jbosstools.integrationtests.aggregate_jbt41 jbosstools.integrationtests.aggregate devstudio_70 devstudio_trunk etc. {code} -- 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