I'm with the same problem. A simple hello world application gives an infamous:

"main" java.lang.UnsupportedClassVersionError: javax/el/ExpressionFactory : Unsupported major.minor version 51.0"

-- Code --

public class Hello {

          public static void main(String[] args) {

                    StartMain.main(args);

          }

          public void inicio(@Observes ContainerInitialized event){

                    System.out.println("Hello");

          }

}

I've done some testings, and found that the BETA3 version also works (didn't find your version on http://sourceforge.net/projects/jboss/files/Weld/)

Is that right, Weld2 isn't supposed to work on Java6?

Hi Mathias, Israel,

I filed an issue: https://issues.jboss.org/browse/WELD-1431

This should only affect "shaded uber jar", so as a temporary workaround you could work with individual dependencies, see also: http://docs.jboss.org/weld/reference/2.0.0.Final/en-US/html/environments.html#d0e5597 and http://search.maven.org/#artifactdetails|org.jboss.weld.se|weld-se-core|2.0.0.SP1|jar

It will be fixed in 2.0.1.Final (ETA release date: 04/Jun/13).

Thanks Martin, I removed the javax.el from the .jar and inserted the one bundled on jboss-7 for Java6 (nasty surgery) . Everything is working now.

Thanks again,

Mathias, use the BETA3 or 8 meanwhile, or do as myself and change de javax.el from the jar.

Is there a good reason for building dependencies as SHADED / UBER JAR with textual description into it, whereas you could let MAVEN do his job, and let us tweak the dependencies if we need to ??

I feel like I have been sent to a time where people are building WAR files manually ... nightmare.

Donatien,

you can tweak the dependencies even now - just don't use shaded jar but weld-se-core instead. I'm not sure whether shaded jar is a good idea, but it was probably a requirement at a time when weld 1.x was developed.

Okay ! Many thanks Martin, this is indeed much more clean and usefull with weld-se-core. I appreciate your quick answer !