Dennis Geurts wrote:
Thanks Emmanuel,
If I'm not mistaken, the spring-1.0.2.tld is not added to the war at all... I'll check as soon as possible...

Add a jira issue

I also notice that the maven-eclipse-plugin will add the dependency of type 'tld' to the classpath, resulting in an incorrect build classpath in eclipse. (but I'll look into this first in more detail)

Add a jira issue

 pertaining question #2:
You mention the word 'workaround'. Does this mean you consider it a bug that jar of scope 'provided'
are not available in 'test' scope ??

It isn't a bug. I don't know for the moment if we'll extend this scope for tests or if we'll create a new scope.

 (btw, thanks: the workaround will resolve the issue !!!)
 Dennis
On 7/12/05, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:


Dennis Geurts wrote:

Hi all,
I'm using maven 2.0-alpha-3.
To get used to the new structure in maven2 I started converting some of

my

projects to maven2 and came up with the following:
1)
Suppose I want to package a war file and want to include the
spring-1.0.2.tld in /WEB-INF
how do I go about automatically inserting this file at all ?
I added the dependency as follows:

<dependency>
<groupId>spring</groupId>
<artifactId>spring</artifactId>
<version>1.0.2</version>
<type>tld</type>
<scope>runtime</scope>
</dependency>

it's correct. Do you have an error? a wrong destination?


Did I miss a feature in the maven-war-plugin ?
Should I use the maven-resource-plugin ?
2)
the second thing I noticed was the fact that
when I set the scope of the *servletapi* dependency to 'provided' (to
prevent inclusion in the war file), my tests that contain references
to the 'javax.servlet' packages fail to compile. Is there a workaround

to

include the dependencies in the 'provided' scope
into the 'test' scope ?

The workaround is to split your war files and your sources. Put all your
java sources in an other projet and add them in the new jar dep of your war.

Emmanuel


---------------------------------------------------------------------
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