Thanks for your answers.
Stephen, you are right. javax.servlet is coming from GWT-dev jar, and others
from my GWT-based libraries, which must contain sources. How can I exclude
them from compilation? Adding
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<configuration>
<includes>
<include>mypackage/**</include>
</includes>
</configuration>
</plugin>
didn't help...
2009/8/31 Stephen Connolly <stephen.alan.conno...@gmail.com>
> is this not the bug where if the dependent jar contains .java files, then
> javac decides to compile them?
>
> check the jar that you think the classes are coming from and see if that
> jar also has the source of the classes within
>
> Sent from my [rhymes with myPod] ;-)
>
>
> On 30 Aug 2009, at 22:06, Wendy Smoak <wsm...@gmail.com> wrote:
>
> On Sun, Aug 30, 2009 at 1:15 PM, Andrey
>> Razumovsky<razumovsky.and...@gmail.com> wrote:
>>
>> I've got a project with e.g. jar packaging. All my dependencies have
>>> "provided" scope. My problem is that Maven compiler plugin adds
>>> unnecessary
>>> classes from dependent library to output folder - e.g. if I have a class
>>> mypack.MyServlet extends HttpServlet, javax.servlet package will be
>>> present
>>> in compile output directory and therefore will be added to resulting JAR.
>>>
>>
>> Can you reproduce this with a simple project started from the
>> quickstart archetype? I've never seen the jar plugin package up
>> dependencies. (You can do it with the assembly plugin.) Without
>> seeing the pom it's hard to guess what you've done so far.
>>
>> --
>> Wendy
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
