Hi Bengt-Erik, Ran into the same one : http://www.mail-archive.com/[email protected]/msg31444.html
Try and relocate the jspapi:jsp-api to javax.servlet:jsp-api in your local repository - take example on what has been done for servlet-api : http://www.ibiblio.org/maven2/servletapi/servlet-api/2.4/servlet-api-2.4.pom If it's working for you, I'll file an issue to relocate jspapi:jsp-api in central repository. Maybe I'll do it anyway, since it looks like having to be done... -- Yann 2006/1/9, Wendy Smoak <[EMAIL PROTECTED]>: > > On 1/9/06, Bengt-Erik Fröberg <[EMAIL PROTECTED]> wrote: > > > Addendum: > > I've tried > > <dependency> > > <groupId>jspapi</groupId> > > <artifactId>jsp-api</artifactId> > > <version>2.0</version> > > <scope>provided</scope> > > </dependency> > > To find out which of your dependencies is causing the problem, use -X > on the mvn command line. If necessary, you can to redirect the output > to a file with '> filename.txt' . > > Then add an exclusion to that dependency in your pom.xml. Here's a > post with some examples of exclusions: > http://article.gmane.org/gmane.comp.jakarta.tapestry.devel/9103 > > (Depending on how the dependency was originally declared, and whether > I'm remembering correctly, you might need to use either groupId jspapi > or javax.servlet for the JSP API.) > > Finally, open a JIRA ticket under MEV so that the pom for that > dependency can be fixed. Or at least reply here and tell us which one > it was. :) > > -- > Wendy > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
