[jbosstools-dev] ACTION REQUIRED: Can we move up to requiring JUnit 4.12 instead of 3.8? (4.50.0.Beta1-SNAPSHOT target platform w/ Mars M7)

[George Gastaldi]

Another hint as Nick proposed is to remove the JUnit version constraint. 
I'm doing that for Forge

On 05/22/2015 12:16 PM, Nick Boldt wrote:
> Some PRs to consider, which fix MANIFEST.MF and feature.xml files to
> depend on 4.12.0 instead of 3.8.x:
>
> https://github.com/jbosstools/jbosstools-forge/pull/140
> https://github.com/jbosstools/jbosstools-vpe/pull/311
> https://github.com/jbosstools/jbosstools-portlet/pull/33
> https://github.com/jbosstools/jbosstools-jst/pull/487
> https://github.com/jbosstools/jbosstools-javaee/pull/340
> https://github.com/jbosstools/jbosstools-hibernate/pull/73
> https://github.com/jbosstools/jbosstools-bpel/pull/25
> https://github.com/jbosstools/jbosstools-base/pull/407
>
> I've omitted changing anything in poms that declare a MAVEN dependency
> to JUnit 3.8, since that should still be resolved by Maven (not by p2).
>
> Lookin' at you, Central (Maven), JavaEE (CDI & JSF), and VPE.
>
> On 05/21/2015 09:20 PM, Nick Boldt wrote:
>> The following projects have plugins or features which depend on JUnit 3.8.
>>
>> Can they be changed to use JUnit 4.12, which is the version included in
>> the latest 4.50.0.Beta1-SNAPSHOT target platform and Mars M7?
>>
>> * base
>> * bpel
>> * central
>> * forge
>> * hibernate
>> * javaee
>> * jst
>> * portlet
>> * vpe
>>
>> Or do we need to find a way to include JUnit 3.8 as well as JUnit 4.12?
>>
>> Details here: https://issues.jboss.org/browse/JBIDE-19836
>>