I would suspect the jdk compiler is doing this.
On Wed, May 20, 2009 at 5:19 PM, Michael Guyver michael.guy...@gmail.comwrote:
Hi Max,
2009/5/20 Max Bowsher m...@mxtelecom.com:
Investigate the possibility that .java *source* files corresponding to
those classes somehow exist in one of
I don't see anything in particular in your file listing nor in the
effective pom that would make me instantly say oh that's it.
Does this happen repeatedly? Can you replicate it on another computer,
ideally with a completely different operating system and JDK version?
If you had to, could you
Hi Wayne,
Thanks for having a look for me.
2009/5/20 Wayne Fay wayne...@gmail.com:
Does this happen repeatedly?
It happens every time that Maven performs a compile of any of that
project's source code. By that I mean that if I delete the javax
directory from target/classes and run mvn compile,
Michael Guyver wrote:
Hi there,
I'm experiencing some very very strange behaviour in my project. The
mvn compile goal is somehow generating/unpacking the following files
into my target/classes directory:
javax/servlet/ServletRequest.class
javax/servlet/RequestDispatcher.class
Hi Max,
2009/5/20 Max Bowsher m...@mxtelecom.com:
Investigate the possibility that .java *source* files corresponding to
those classes somehow exist in one of your dependency jar files. I've
occasionally encountered weirdness where in such a circumstance, those
.java files can get compiled
bump?
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
2009/5/16 Wayne Fay wayne...@gmail.com:
How on earth do you explain javax/servlet/**/*.class files appearing
in your output directory that are not in your source tree?
dependency:unpack would do that.
As far as I can tell, it's not present. I've attached the
effective-pom.xml for anyone
Hi there,
I'm experiencing some very very strange behaviour in my project. The
mvn compile goal is somehow generating/unpacking the following files
into my target/classes directory:
javax/servlet/ServletRequest.class
javax/servlet/RequestDispatcher.class
javax/servlet/ServletContext.class
Well, at first sight, it seems totally normal. So I guess this would help
what command you're running, in which context and what you thought you would
get, and if you're beginning to use maven or already have been using it for
some time (to know where the resulting explanations should start).
2009/5/15 Baptiste MATHUS m...@batmat.net:
Well, at first sight, it seems totally normal.
Are you sure about that?
So I guess this would help [to know] what command you're running,
mvn -o compile
in which context
not sure what you mean by context
and what you thought you would get
my
Posting your pom may aid folks in assisting you better...
On 5/15/09, Michael Guyver michael.guy...@gmail.com wrote:
2009/5/15 Baptiste MATHUS m...@batmat.net:
Well, at first sight, it seems totally normal.
Are you sure about that?
So I guess this would help [to know] what command you're
How on earth do you explain javax/servlet/**/*.class files appearing
in your output directory that are not in your source tree?
dependency:unpack would do that.
Check the pom for odd configuration. Also check profiles.xml in the same dir.
Then check the pom's parent for odd configuration, and
12 matches
Mail list logo
