Have you tried this? Runtimr and compile scopes are both transitive, so
the situation you describe should work just as before
On 05/03/2013 07:23 AM, Strong Liu wrote:
On May 3, 2013, at 8:13 PM, Steve Ebersole <steven.ebersole(a)gmail.com
<mailto:steven.ebersole@gmail.com>> wrote:
> I dont understand what you mean with HHH-8220. OK its a change, but
> how is that breaking any builds?
>
suppose there is a WAR project that uses hibernate, and it has a
compile scope dependency of h-em
before this 4.3.0.Beta2, the HEM will brings all required dependencies
in ( for example, h-core )
but after upgrade to 4.3.0.Beta2, the build WAR will only contains HEM
and no H-Core since HEM now has a runtime scope dependency of h-core
then the WAR will fail when being deployed
> And for JDK 7 we have discussed that on this list already. Gunnar
> will work on integrating some checks into the build to make sure we
> are not using JDK 7 features…
>
I'm aware of this , just pointed out that this 4.3.0.Beta2 will fail
on JDK 6, and others who run into this issue will know the reason
>
> On 05/03/2013 02:08 AM, Strong Liu wrote:
>>
https://hibernate.atlassian.net/browse/HHH-8219
>>
>>
https://hibernate.atlassian.net/browse/HHH-8220
>>
>>
>> -------------------------
>> Best Regards,
>>
>> Strong Liu <stliu at hibernate.org>
>>
http://about.me/stliu/bio
>>
>>
>>
>> _______________________________________________
>> hibernate-dev mailing list
>> hibernate-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
-------------------------
Best Regards,
Strong Liu <stliu at
hibernate.org <
http://hibernate.org/>>
http://about.me/stliu/bio