[ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18772: ------------------------------------ Well, just as buildchow's mission is to support a bunch of different use cases (nails, tacks, and screws) w/ a single large hammer, so too you're going to have a tough time making matrix jobs, JBDS jobs, and aggregates all look like the same type of nail. Here's an example of where we do a move and then 3 publishes. https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio.product_ma... Here's an example of where we do 2 publishes (builds & updates): https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit... Here's an example of where for webtools we do 2 publishes, but for central and earlyaccess, we do 4 publishes (to push the bits to devstudio.redhat.com, too): https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit... Here's an example of where we do 2 publishes for JBDS and 1 for JBT, within a matrix job, using a DIFFERENT publish.sh (from the master branch of jbosstools-targetplatforms, not the usual one from jbosstools-build-ci): https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplat... So, I admire the end-goal but I'm not sure how to get there from here. Would we have multiple profiles in the parent pom for each scenario? Or would we encode these alternate approaches in the root poms for the various projects instead, calling the same mojo as many times as required? Can you do if-else branching when calling mojos in a pom? -- This message was sent by Atlassian JIRA (v6.3.15#6346)