changing to el-api 2.2 to avoid tomcat problems

[Turini]

as discussed here #328

[garcia-jj]

This is not a problem, it's only a Tomcat warning. And it's not caused by this artifact, but CDI dependency. I don't know if this is the solution. I'll test this.

More info here: https://groups.google.com/forum/#!topic/caelum-vraptor/BtnJ6N6ATh4

[dipold]

In tomcat is a warning, but In musicjungle I need to do this because tomcat-maven-plugin was generating conflict:

java.lang.LinkageError: loader constraint violation: when resolving interface method
"javax.servlet.jsp.JspApplicationContext.getExpressionFactory()Ljavax/el/ExpressionFactory;" the class loader 
(instance of org/apache/jasper/servlet/JasperLoader) of the current class, 
org/apache/jsp/WEB_002dINF/jsp/home/login_jsp, and the class loader (instance of 
org/codehaus/plexus/classworlds/realm/ClassRealm) for resolved class, javax/servlet/jsp/JspApplicationContext, 
have different Class objects for the type avax/el/ExpressionFactory; used in the signature

[garcia-jj]

Using dependency:tree, this artifact is already declared by cdi:

[INFO] +- javax.enterprise:cdi-api:jar:1.1:provided
[INFO] |  \- javax.el:el-api:jar:2.2:provided

So you're right.

🚀

[garcia-jj]

Thank you @dipold

[Turini]

tks @dipold !