Re: Maven compiler plugin adds unnecessary dependent classes to output folder

2009-08-31 Thread Andrey Razumovsky
BWT, is it possible to include *only* classes I specify in tag and dependent from my classpath? E.g. my structure is mypackage client A.java B.java server C.java --> C extends A and maven-compiler-plugin contains mypackage/server/** then I want my resulting jar co

Re: Maven compiler plugin adds unnecessary dependent classes to output folder

2009-08-31 Thread Andrey Razumovsky
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 org.apache.maven.plugins maven-compiler-plugin

Re: Maven compiler plugin adds unnecessary dependent classes to output folder

2009-08-30 Thread Stephen Connolly
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, Wen

Re: Maven compiler plugin adds unnecessary dependent classes to output folder

2009-08-30 Thread Wendy Smoak
On Sun, Aug 30, 2009 at 1:15 PM, Andrey Razumovsky 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.MyServl

Maven compiler plugin adds unnecessary dependent classes to output folder

2009-08-30 Thread Andrey Razumovsky
Hi Maven guru, 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