You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Olivier Dehon <od...@gmail.com> on 2010/07/18 03:39:41 UTC

Maven 2.2.1 - Test compilation classpath does not include dependencies with provided scope

Hello,

I came across what I think is a bug introduced in maven 2.2.x.
In my WAR project, I have a dependency with provided scope, which is
needed by both my classes and test-classes. With maven 2.1.0, everything
compiles ok, classes and test-classes alike. With maven 2.2.1, the test
classes do not compile anymore, complaining about a missing class from
the provided dependency.

I have browsed JIRA and found issues that sound similar, mentioning a
change of spec when dealing with the inheritance of the provided scope,
but this case seems a bit different, as no inheritance is involved.

Has anyone faced a similar issue? Is there a workaround?

Thanks in advance, -Olivier


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Maven 2.2.1 - Test compilation classpath does not include dependencies with provided scope

Posted by Anders Hammar <an...@hammar.net>.
I think a bug like this is very unlikely, as someone would have encountered
it already. You could try Maven 3.0-beta-1 to see if it makes a difference.
Or provide a sample project that illustrates the issue.

/Anders

On Sun, Jul 18, 2010 at 03:39, Olivier Dehon <od...@gmail.com> wrote:

> Hello,
>
> I came across what I think is a bug introduced in maven 2.2.x.
> In my WAR project, I have a dependency with provided scope, which is
> needed by both my classes and test-classes. With maven 2.1.0, everything
> compiles ok, classes and test-classes alike. With maven 2.2.1, the test
> classes do not compile anymore, complaining about a missing class from
> the provided dependency.
>
> I have browsed JIRA and found issues that sound similar, mentioning a
> change of spec when dealing with the inheritance of the provided scope,
> but this case seems a bit different, as no inheritance is involved.
>
> Has anyone faced a similar issue? Is there a workaround?
>
> Thanks in advance, -Olivier
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>