Jozef Hartinger wrote:
Done, the problems are:
ShrinkWrap API (alpha5) targets Java 1.6
- currently breaks drools, international and jms modules
There was an alpha-6 (and
later versions) which targets Java 1.5:
http://community.jboss.org/thread/147880?tstart=0
https://jira.jboss.org/jira/browse/SHRINKWRAP-131
jboss-ejb3-api-3.1.0.jar targets Java 1.6
- currently breaks envconfig module
The jboss-ejb3-api artifact has been
deprecated. Please switch over to
org.jboss.spec.javax.ejb:jboss-ejb-api_3.1_spec artifact
http://repository.jboss.org/maven2/org/jboss/spec/javax/ejb/jboss-ejb-api....
That however is not going to solve the original issue, since it still
targets 1.6
-Jaikiran
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
_______________________________________________
seam-dev mailing list
seam-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/seam-dev