Hi all, Here is the PR to move target-platforms to Kepler RC3: https://github.com/jbosstools/jbosstools-target-platforms/pull/5 Please test it on your favorite component using the following steps from you jbosstools-target-platform repo: $ git remote add mickael git://github.com/mickaelistria/jbosstools-target-platforms.git $ git fetch mickael keplerRC3 $ cd jbosstools/multiple $ mvn clean install -P \!multiple2repo $ cd ~/git/jbosstools-myfavoritecomponent $ mvn clean verify -P multiple.target Then come to the PR and add a message such as "works for ... component" or "failing on ... component: error is 'cannot resolve dependency <details>' ". Please note that this will only test the new TP if you've moved your reference to parent pom to 4.1.0.Beta2-SNAPSHOT. If you didn't do that, then please scroll up in your mail box and read carefully the mail prefixed with "URGENT". Cheers, -- Mickael Istria Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools> My blog <http://mickaelistria.wordpress.com> - My Tweets <http://twitter.com/mickaelistria>

On 06/11/2013 08:35 PM, Alexey Kazakov wrote: I forgot a git checkout FETCH_HEAD. Also in order to test, one has to INSTALL the target platform, not only verify it. So what I recommand is: # Git stuff, do it as you want $ git remote add mickael git://github.com/mickaelistria/jbosstools-target-platforms.git $ git fetch mickael keplerRC3 $ git checkout FETCH_HEAD # Install TP locally $ cd jbosstools/multiple $ mvn clean install -P \!multiple2repo # Then test it on your component $ cd ~/git/jbosstools-myfavoritecomponent $ mvn clean verify -P multiple.target But there are many ways to achieve the same goal, which is to install the newer mutliple.target locally and then try a build locally. If you have another git workflow you feel better with, feel free to use it. -- Mickael Istria Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools> My blog <http://mickaelistria.wordpress.com> - My Tweets <http://twitter.com/mickaelistria>

Here is the most interesting ouput I got: mistria@mistria--rh:~/git/p2diff/org.eclipse.equinox.p2.example.p2diff.packaging/target/products/org.eclipse.equinox.p2.example.p2diff.product/linux/gtk/x86_64$ ./p2diff -mode=ignoreVersions http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.3... file:/home/mistria/git/jbosstools-target-platforms/jbosstools/multiple/target/jbosstools-multiple.target.repo/ < org.eclipse.update.core [3.2.600.v20130514-1341] === Summary === http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.3... contains 1 unique IUs file:/home/mistria/git/jbosstools-target-platforms/jbosstools/multiple/target/jbosstools-multiple.target.repo/ contains 0 unique IUs It's interesting, but in this specific case, it doesn't provide much value. Here is what we would have noticed if we have used it earlier: mistria@mistria--rh:~/git/p2diff/org.eclipse.equinox.p2.example.p2diff.packaging/target/products/org.eclipse.equinox.p2.example.p2diff.product/linux/gtk/x86_64$ ./p2diff -mode=ignoreVersions http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.3... http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.3... < org.eclipse.ecf.provider.filetransfer.httpclient [4.0.300.v20130309-0714] < org.eclipse.persistence.jpa.jpql.source [2.5.0.v20130425-368d603] < org.eclipse.ecf.provider.filetransfer.httpclient.ssl [1.0.0.v20130309-0714] === Summary === http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.3... contains 3 unique IUs http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.3... contains 2 unique IUs Which is more interesting (notice the httpclient removal). So it looks like this p2 diff tool can definitly help to anticipate some bugs as it allows to spot changes in transitive dependencies. Cheers, -- Mickael Istria Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools> My blog <http://mickaelistria.wordpress.com> - My Tweets <http://twitter.com/mickaelistria>