On 15 Apr 2010, at 12:19, Jozef Hartinger wrote:
Done, the problems are:
ShrinkWrap API (alpha5) targets Java 1.6
- currently breaks drools, international and jms modules
Andy, what do you think about making Shrinkwrap target Java 5, not Java 6?
If you don't want to do this, I think we can still have the modules target Java 5 for
runtime, but require Java 6 for testing. It's just harder in the Hudson setup :-)
jboss-ejb3-api-3.1.0.jar targets Java 1.6
- currently breaks envconfig module
Shelly, is it possible we can compile this API with Java 5? Or have a Java 5 version?
Are your new spec APIs (which we should switch to...) Java 5 or Java 6?
Other compilation problems
- Faces
https://jira.jboss.org/jira/browse/SEAMFACES-13
- Remoting
https://jira.jboss.org/jira/browse/SEAMREMOTING-3
On 04/15/2010 12:23 PM, Pete Muir wrote:
> Yes.
>
> On 15 Apr 2010, at 08:54, Jozef Hartinger wrote:
>
>> I set the CI jobs to run on JDK 5. Should also the snapshots that are published
to the maven repository be built with JDK 5?
>>
>> On 04/13/2010 03:32 PM, Pete Muir wrote:
>>> Just to remind everyone (not sure if this is a problem or not atm ;-) but all
Seam modules should be developed using Java 5 unless there is a strong reason to use Java
6. We should used the Hudson jobs to ensure that the code builds with Java 5.
>>> _______________________________________________
>>> seam-dev mailing list
>>> seam-dev(a)lists.jboss.org
>>>
https://lists.jboss.org/mailman/listinfo/seam-dev
>