org.eclipse.jdt.core;visibility:=reexport,

Looks like we once again have broken JDT patch in our TP ? [ERROR] Internal error: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.eclipse.jdt.core 3.7.3.v_OTDT_r202_201201310618 to org.eclipse.objectteams.otdt.core.patch.feature.group [2.0.0,3.0.0).", "Unable to satisfy dependency from org.jboss.tools.site.core raw:0.0.2.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):0.0.2-SNAPSHOT to org.jboss.tools.maven.jpa.feature.feature.group 0.0.0.", "No solution found because the problem is unsatisfiable."] -> [Help 1] "org.eclipse.objectteams.otdt.core.patch.feature.group" should *not* be anywhere near us. Nick, any idea ? /max On Feb 9, 2012, at 19:11, jboss-qa-internal(a)redhat.com wrote: > jbosstools-3.3_trunk.aggregate - Build # 4170 - Still Failing: > > Check console output at http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.aggregate/4170/ to view the results. > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev /max http://about.me/maxandersen

There are no references to org.eclipse.jdt.core 3.7.3.v_OTDT_r202_201201310618 anywhere in org.jboss.tools.maven.jpa.feature, nor is it in the TP - .target or site. In fact, neither the org.jboss.tools.maven.jpa.feature nor the org.jboss.tools.maven.jpa plugin even reference org.eclipse.jdt.core. The only place in JBT Maven component that mentions o.e.jdt.core is ~/trunk/maven/plugins/org.jboss.tools.maven.core/META-INF/MANIFEST.MF, line 17: > org.eclipse.jdt.core;visibility:=reexport, So... is this coming in from org.eclipse.m2e.feature ? Unlikely... all I see there is: ./features/org.eclipse.m2e.feature_1.0.0.20110607-2117.jar <import feature="org.eclipse.jdt" version="3.4.0" match="greaterOrEqual"/> ./features/org.eclipse.m2e.feature_1.0.100.20110804-1717.jar <import feature="org.eclipse.jdt" version="3.6.0" match="greaterOrEqual"/> ... I'm stumped. On 02/09/2012 01:19 PM, Max Rydahl Andersen wrote: > Looks like we once again have broken JDT patch in our TP ? > > [ERROR] Internal error: java.lang.RuntimeException: "No solution found > because the problem is unsatisfiable.": ["Unable to satisfy dependency > from org.eclipse.jdt.core 3.7.3.v_OTDT_r202_201201310618 to > org.eclipse.objectteams.otdt.core.patch.feature.group [2.0.0,3.0.0).", > "Unable to satisfy dependency from org.jboss.tools.site.core > raw:0.0.2.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):0.0.2-SNAPSHOT to > org.jboss.tools.maven.jpa.feature.feature.group 0.0.0.", "No solution > found because the problem is unsatisfiable."] -> [Help 1] > > "org.eclipse.objectteams.otdt.core.patch.feature.group" should *not* > be anywhere near us. > > Nick, any idea ? > > /max > > On Feb 9, 2012, at 19:11, jboss-qa-internal(a)redhat.com wrote: > >> jbosstools-3.3_trunk.aggregate - Build # 4170 - Still Failing: >> >> Check console output at >> http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.aggregate/4170/ >> to view the results. >> _______________________________________________ >> jbosstools-dev mailing list >> jbosstools-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev > > /max > http://about.me/maxandersen > > > >

On Feb 9, 2012, at 21:42, Nick Boldt wrote: > So it seems the latest Indigo mirror actually includes this jar: > > $ cd ~/RHDS/updates/requirements/indigo/201202012328-SR1-M > $ find . -name "org.eclipse.jdt.core_*" > ./plugins/org.eclipse.jdt.core_3.7.3.v20120119-1537.jar > ./plugins/org.eclipse.jdt.core_3.7.3.v_OTDT_r202_201201310618.jar > > I guess I have to remove that so that nothing that relies on org.eclipse.jdt.core will pick up the wrong version... *sigh* Yes, just like discussed last time http://lists.jboss.org/pipermail/jbosstools-dev/2011-November/004288.html And yes, this patch is just evil and shouldn't be included. I wonder how it got "reintroduced" when we already removed it once ? /max > > N > > On 02/09/2012 02:10 PM, Nick Boldt wrote: >> There are no references to org.eclipse.jdt.core >> 3.7.3.v_OTDT_r202_201201310618 anywhere in >> org.jboss.tools.maven.jpa.feature, nor is it in the TP - .target or site. >> >> In fact, neither the org.jboss.tools.maven.jpa.feature nor the >> org.jboss.tools.maven.jpa plugin even reference org.eclipse.jdt.core. >> >> The only place in JBT Maven component that mentions o.e.jdt.core is >> ~/trunk/maven/plugins/org.jboss.tools.maven.core/META-INF/MANIFEST.MF, >> line 17: >> >>> org.eclipse.jdt.core;visibility:=reexport, >> >> So... is this coming in from org.eclipse.m2e.feature ? Unlikely... all I >> see there is: >> >> ./features/org.eclipse.m2e.feature_1.0.0.20110607-2117.jar >> <import feature="org.eclipse.jdt" version="3.4.0" match="greaterOrEqual"/> >> >> ./features/org.eclipse.m2e.feature_1.0.100.20110804-1717.jar >> <import feature="org.eclipse.jdt" version="3.6.0" match="greaterOrEqual"/> >> >> >> ... I'm stumped. >> >> On 02/09/2012 01:19 PM, Max Rydahl Andersen wrote: >>> Looks like we once again have broken JDT patch in our TP ? >>> >>> [ERROR] Internal error: java.lang.RuntimeException: "No solution found >>> because the problem is unsatisfiable.": ["Unable to satisfy dependency >>> from org.eclipse.jdt.core 3.7.3.v_OTDT_r202_201201310618 to >>> org.eclipse.objectteams.otdt.core.patch.feature.group [2.0.0,3.0.0).", >>> "Unable to satisfy dependency from org.jboss.tools.site.core >>> raw:0.0.2.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):0.0.2-SNAPSHOT to >>> org.jboss.tools.maven.jpa.feature.feature.group 0.0.0.", "No solution >>> found because the problem is unsatisfiable."] -> [Help 1] >>> >>> "org.eclipse.objectteams.otdt.core.patch.feature.group" should *not* >>> be anywhere near us. >>> >>> Nick, any idea ? >>> >>> /max >>> >>> On Feb 9, 2012, at 19:11, jboss-qa-internal(a)redhat.com wrote: >>> >>>> jbosstools-3.3_trunk.aggregate - Build # 4170 - Still Failing: >>>> >>>> Check console output at >>>> http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.aggregate/4170/ >>>> to view the results. >>>> _______________________________________________ >>>> jbosstools-dev mailing list >>>> jbosstools-dev(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >>> >>> /max >>> http://about.me/maxandersen >>> >>> >>> >>> >> > > -- > Nick Boldt :: JBoss by Red Hat > Productization Lead :: JBoss Tools& Dev Studio > http://nick.divbyzero.com /max http://about.me/maxandersen

> Last time I added it to the TP explicitly because it seemed to be needed by something in org.jboss.tools. I removed when I was told otherwise. Mea culpa. > > This time it appeared on the scene because Indigo includes it, and it's been upversioned w/ a newer version than the unpatched jdt.core plugin -- in ascii qualifier terms, "v_"> "v2". gotcha! > Can someone else report this on the cross-projects list? Not sure the rationale behind having two versions of jdt.core in Indigo - might have been accidental (like the first time *WE* included it). created https://issues.jboss.org/browse/JBIDE-10866 so don't forgetting it - anyone feel free to take it otherwise I will when things settles down. /max > On 02/10/2012 10:01 AM, Max Rydahl Andersen wrote: >> >> On Feb 9, 2012, at 21:42, Nick Boldt wrote: >> >>> So it seems the latest Indigo mirror actually includes this jar: >>> >>> $ cd ~/RHDS/updates/requirements/indigo/201202012328-SR1-M >>> $ find . -name "org.eclipse.jdt.core_*" >>> ./plugins/org.eclipse.jdt.core_3.7.3.v20120119-1537.jar >>> ./plugins/org.eclipse.jdt.core_3.7.3.v_OTDT_r202_201201310618.jar >>> >>> I guess I have to remove that so that nothing that relies on org.eclipse.jdt.core will pick up the wrong version... *sigh* >> >> Yes, just like discussed last time http://lists.jboss.org/pipermail/jbosstools-dev/2011-November/004288.html >> >> And yes, this patch is just evil and shouldn't be included. >> >> I wonder how it got "reintroduced" when we already removed it once ? >> >> /max >> >>> >>> N >>> >>> On 02/09/2012 02:10 PM, Nick Boldt wrote: >>>> There are no references to org.eclipse.jdt.core >>>> 3.7.3.v_OTDT_r202_201201310618 anywhere in >>>> org.jboss.tools.maven.jpa.feature, nor is it in the TP - .target or site. >>>> >>>> In fact, neither the org.jboss.tools.maven.jpa.feature nor the >>>> org.jboss.tools.maven.jpa plugin even reference org.eclipse.jdt.core. >>>> >>>> The only place in JBT Maven component that mentions o.e.jdt.core is >>>> ~/trunk/maven/plugins/org.jboss.tools.maven.core/META-INF/MANIFEST.MF, >>>> line 17: >>>> >>>>> org.eclipse.jdt.core;visibility:=reexport, >>>> >>>> So... is this coming in from org.eclipse.m2e.feature ? Unlikely... all I >>>> see there is: >>>> >>>> ./features/org.eclipse.m2e.feature_1.0.0.20110607-2117.jar >>>> <import feature="org.eclipse.jdt" version="3.4.0" match="greaterOrEqual"/> >>>> >>>> ./features/org.eclipse.m2e.feature_1.0.100.20110804-1717.jar >>>> <import feature="org.eclipse.jdt" version="3.6.0" match="greaterOrEqual"/> >>>> >>>> >>>> ... I'm stumped. >>>> >>>> On 02/09/2012 01:19 PM, Max Rydahl Andersen wrote: >>>>> Looks like we once again have broken JDT patch in our TP ? >>>>> >>>>> [ERROR] Internal error: java.lang.RuntimeException: "No solution found >>>>> because the problem is unsatisfiable.": ["Unable to satisfy dependency >>>>> from org.eclipse.jdt.core 3.7.3.v_OTDT_r202_201201310618 to >>>>> org.eclipse.objectteams.otdt.core.patch.feature.group [2.0.0,3.0.0).", >>>>> "Unable to satisfy dependency from org.jboss.tools.site.core >>>>> raw:0.0.2.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):0.0.2-SNAPSHOT to >>>>> org.jboss.tools.maven.jpa.feature.feature.group 0.0.0.", "No solution >>>>> found because the problem is unsatisfiable."] -> [Help 1] >>>>> >>>>> "org.eclipse.objectteams.otdt.core.patch.feature.group" should *not* >>>>> be anywhere near us. >>>>> >>>>> Nick, any idea ? >>>>> >>>>> /max >>>>> >>>>> On Feb 9, 2012, at 19:11, jboss-qa-internal(a)redhat.com wrote: >>>>> >>>>>> jbosstools-3.3_trunk.aggregate - Build # 4170 - Still Failing: >>>>>> >>>>>> Check console output at >>>>>> http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.aggregate/4170/ >>>>>> to view the results. >>>>>> _______________________________________________ >>>>>> jbosstools-dev mailing list >>>>>> jbosstools-dev(a)lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >>>>> >>>>> /max >>>>> http://about.me/maxandersen >>>>> >>>>> >>>>> >>>>> >>>> >>> >>> -- >>> Nick Boldt :: JBoss by Red Hat >>> Productization Lead :: JBoss Tools& Dev Studio >>> http://nick.divbyzero.com >> >> /max >> http://about.me/maxandersen >> >> >> > > -- > Nick Boldt :: JBoss by Red Hat > Productization Lead :: JBoss Tools& Dev Studio > http://nick.divbyzero.com /max http://about.me/maxandersen

I was trying to take care of emma coverage report generation problem for common component build and found that for running tests it uses org.jboss.tools.common-3.3.0.M3.jar :)