Anybody got a chance to look into this? I am able to reproduce this on another system as well. So this does not seem to be my setup specific problem. It seems like a broken build unless there's a cached artifact on the build machine which lets the build succeed.
On Thu, Aug 20, 2015 at 5:26 PM, Satya Deep Maheshwari <connus...@gmail.com> wrote: > Hi > > While compiling launchpad/base, I am getting the following compilation > error: > > [INFO] ------------------------------------------------------------- > [ERROR] COMPILATION ERROR : > [INFO] ------------------------------------------------------------- > [ERROR] /home/satyadeep/git/ > github.com/sling/launchpad/base/src/main/java/org/apache/sling/launchpad/base/webapp/SlingHttpSessionListenerDelegate.java:[41,27] > <http://github.com/sling/launchpad/base/src/main/java/org/apache/sling/launchpad/base/webapp/SlingHttpSessionListenerDelegate.java:%5B41,27%5D> > cannot access javax.servlet.http.HttpSessionIdListener > class file for javax.servlet.http.HttpSessionIdListener not found > [INFO] 1 error > > > This error gets resolved if I fix the servlet-api version in pom from > 3.0.1 to 3.1.0 . And this change seems valid as well because > javax.servlet.http.HttpSessionIdListener is available since Servlet 3.1 > only. I wonder if others are facing this problem and if not, why? > > Regards > Satya Deep >
