> I believe you would then propose we change 2.2 to 3.0?

If you simply change 2.2 to 3.0 in debian/rules in that stanze, then
it'll change the dependency on javax.el:el-api as well.

So, the dependencies should be the following:
javax.el:el-api:2.2 (same as it is now)
javax.servlet:servlet-api:3.0 (changed from 2.2 to 3.0)

You can consult the table of versions for jsp, servlet, etc. here:
http://stackoverflow.com/questions/2013879/the-ultimate-java-version-table-j2ee-java-ee-servlet-jsp-jstl

In case of libservlet2.5-java package maintainers have replaced the
actual versions to "debian", so it works properly.

For the case of libservlet3.1-java everything is also fine:
https://anonscm.debian.org/cgit/pkg-java/tomcat8.git/tree/debian/javaxpoms/jsp-api.pom
(compare it with the table).

Saying more general: Tomcat always provides a compatible set of versions
for jsp-api, servlet-api and el-api. So, POM dependencies within a
libservletXXX-java package have to point to the corresponding versions
of .jar-s that are placed in such package.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1664179

Title:
  Wrong POM dependency in javax.servlet.jsp:jsp-api:2.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tomcat7/+bug/1664179/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to