Hi Yann and thanks!

It seems to be the exact same problem, yes, and it also involves
acegisecurity, but version 0.9.0 this time, which has a compile-dependency
on jsp.api 2.0. That causes it to be included in WEB-INF/lib, and Tomcat
5.5.11 does not approve.....

Thanks to all you other helpers out there (i.e Wendy), this snippet in my
POM seems to fix the acute problem:

<dependency>
        <groupId>org.springframework</groupId>
        <artifactId>spring</artifactId>
        <version>1.2.6</version>
        <scope>compile</scope>
        <exclusions>
                <exclusion>
                        <groupId>javax.servlet</groupId>
                        <artifactId>jsp-api</artifactId>
                </exclusion>
      </exclusions>                     
</dependency>
<dependency>
        <groupId>acegisecurity</groupId>
        <artifactId>acegi-security</artifactId>
        <version>0.9.0</version>
        <scope>compile</scope>
        <exclusions>
                <exclusion>
                        <groupId>javax.servlet</groupId>
                <artifactId>jsp-api</artifactId>
                </exclusion>
                <exclusion>
                <groupId>springframework</groupId>
                <artifactId>spring</artifactId>
                </exclusion>
                <exclusion>
                <groupId>springframework</groupId>
                <artifactId>spring-mock</artifactId>
                </exclusion>
      </exclusions>
</dependency>

(Acegi 0.9 is also depending on Spring 1.2.6, hence the Spring exclusions)

Regards,

/B-E

-----Ursprungligt meddelande-----
Från: Yann Le Du [mailto:[EMAIL PROTECTED] 
Skickat: den 9 januari 2006 17:42
Till: Maven Users List
Ämne: Re: How to prevent jar to be included in WEB-INF/lib?

Hi Bengt-Erik,

Ran into the same one :
http://www.mail-archive.com/users@maven.apache.org/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]
>
>



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to