Hi, Central build was failing because the org.jboss.tools.maven.project.examples plugin was moved to the examples directory (JBIDE-17714). The Jenkins workspace contained this plugin in two directories what caused jacoco to break. I have fixed this by removing the Jenkins workspace. Snjeza _______________________________________________ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev

The Hibernate build fails because there are the same class names within the hibernate component (there are four org.jboss.tools.hibernate.proxy.SessionFactoryProxy, for instance). See https://issues.jboss.org/browse/JBIDE-17551

On 7 Jul 2014, at 10:36, Mickael Istria wrote: > On 07/05/2014 07:03 PM, Snjezana Peco wrote: >> The Hibernate build fails because there are the same class names >> within >> the hibernate component (there are four >> org.jboss.tools.hibernate.proxy.SessionFactoryProxy, for instance). >> See >> https://issues.jboss.org/browse/JBIDE-17551 > This was already reported for master, and I just removed the Jacoco > step from build to get it working. So Hibernate doesn't have Jacoco > coverage any more. > I'm not sure your patch is better than just disabling jacoco. Since it > ignores all stuff from hibernate, the results of coverage for > Hibernate will most likely become quite useless, so IMO, just removing > the Jacoco step for Hibernate on branch would have been a cleaner fix > that implementing exceptions in the script (that we'll for sure forget > to remove if one day we re-enable Jacoco for Hibernate builds). I still don't get why this is suddenly a new problem - hibernate tools have for years had multiple versions of the same classnames because it has multiple version support. What is so different about these? /max http://about.me/maxandersen _______________________________________________ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev

On 7/7/2014 1:03 PM, Max Rydahl Andersen wrote: > On 7 Jul 2014, at 10:36, Mickael Istria wrote: > >> On 07/05/2014 07:03 PM, Snjezana Peco wrote: >>> The Hibernate build fails because there are the same class names >>> within >>> the hibernate component (there are four >>> org.jboss.tools.hibernate.proxy.SessionFactoryProxy, for instance). >>> See >>> https://issues.jboss.org/browse/JBIDE-17551 >> This was already reported for master, and I just removed the Jacoco >> step from build to get it working. So Hibernate doesn't have Jacoco >> coverage any more. >> I'm not sure your patch is better than just disabling jacoco. Since it >> ignores all stuff from hibernate, the results of coverage for >> Hibernate will most likely become quite useless, so IMO, just removing >> the Jacoco step for Hibernate on branch would have been a cleaner fix >> that implementing exceptions in the script (that we'll for sure forget >> to remove if one day we re-enable Jacoco for Hibernate builds). > I still don't get why this is suddenly a new problem - hibernate tools > have for years had multiple versions of the same classnames because it > has multiple version support. > > What is so different about these? I am not sure, but the org.jboss.tools.hibernate.proxy.SessionFactoryProxy class is a new class. I will try to reproduce the issue locally.

Snjeza > /max > http://about.me/maxandersen > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev _______________________________________________ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev