[ https://issues.jboss.org/browse/JBIDE-18742?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-18742: ----------------------------------- Description: Instead of the composite-install test to decide whether we aggregate or not, it would be simpler to build aggregation in any case and then use p2diff (or other smart mechanism) to decide whether we want to publish the new composite or not. It's more or less just a matter of scripting {code} p2diff file:${WORKSPACE}/results/${JOB_NAME}/all/repo/ http://download.jboss.org/jbosstools/builds/staging/${JOB_NAME}/all/repo/ | grep -e ^\< -e ^\> > p2diff_snapshot if [[ -s p2diff_snapshot ]]; then ./publish.sh fi {code} Another benefit is that it allows us to get rid of the composite (1 less couple of files to maintain) was: Instead of the composite-install test to decide whether we aggregate or not, it would be simpler to build aggregation in any case and then use p2diff (or other smart mechanism) to decide whether we want to publish the new composite or not. It's more or less just a matter of scripting {code} p2diff file:/local/p2/repo http://download.jboss.org/builds/jbosstools-aggregate_master/repo > diff if [ diff seems cool ]; then ./publish.sh fi {code} Another benefit is that it allows us to get rid of the composite (1 less couple of files to maintain) -- This message was sent by Atlassian JIRA (v6.3.8#6338)