Hey Martin, +1 to <scoped>provided</scope>, the Java EE dependency can be provided by Apache Geronimo.
Thoughts? Cheers, Chris ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: [email protected] WWW: http://sunset.usc.edu/~mattmann/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -----Original Message----- From: Martin Desruisseaux <[email protected]> Organization: Geomatys Reply-To: "[email protected]" <[email protected]> Date: Monday, April 15, 2013 7:03 AM To: Apache SIS <[email protected]> Subject: Would like to replace servlet-api dependency by javaee-api >Hello all > >The sis-webapp module currently depends on javax.servlet.javax-api >version 2.4. I would like to make two changes: > >* Replace this dependency by javaee-api version 6.0. >* Declare <scope>provided</scope> > >The reason is that the servlet API is now in version 3.0, but no 3.0 >version is going to be deployed on Maven central. Instead, the whole >stack (servlet-api and other dependencies) has been replaced by a single >javaee-api dependency, which I agree make things simpler :-). > >The <scope>provided</scope> is because those classes are supposed to be >provided by the JEE container rather than by the application. > >There is nothing to change in the source code. I verified that the Maven >tests continue to pass. Is there any objection against this change? > > Martin >
