Anderson Perrelli 4 Years Ago Awesome! Thanks for sharing. Please sign in to reply. Reply as... Cancel
David H Nebinger 4 Years Ago Hmm, just got this issue for 7.2 GA1, so it may not be limited to 7.1. But the same solution here worked in the 7.2 environ, so I'm good. Please sign in to reply. Reply as... Cancel
Lawrence Lee 4 Years Ago Another workaround would be to use "force = true". I found it easier to type and remember compile(group: "javax.servlet", name: "javax.servlet-api", version: "3.0.1") {force = true} Please sign in to reply. Reply as... Cancel
Sarath Chandra 4 Years Ago I have the same issue with Liferay 7.2 when using Maven. Any idea about how to fix it? I fixed this by adding the following lines in the bnd.bnd of the module and it works fine: -contract: JavaPortlet,JavaServlet Thoughts? Please sign in to reply. Reply as... Cancel
txapeldot . 5 Months Ago I've just run into the same problem on a DXP 7.1.10-ga1 (7.1.10.1 release from the Nexus Repository Manager, I guess). When you say "I happen to know that, with 7.1, the servlet spec jar version included is 3.0.1", I wonder how you know that. In other words, how can I know what is the actual version of an specific artifact my current DXP instance is working with? I'm asking that because when typing 'lb -s | grep javax.servlet' command on a Gogo shell, I get this result: 16|Active | 6|javax.servlet.jsp-api (2.3.2.b01) 17|Active | 6|javax.servlet.jsp.jstl (1.2.3.LIFERAY-PATCHED-2) 18|Active | 6|javax.servlet.jsp.jstl-api (1.2.1) From the results got, it doesn't seem the DXP server is providing the 'javax.servlet-api' artifact. Looking forward to reading any reply from you. Thanks. Please sign in to reply. Reply as... Cancel