> 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 profiles.xml. Repeat until you get to "the top" pom, and profiles.xml. Then check settings.xml files that may be affecting the build. "mvn help:effective-pom" should also prove useful in your investigations. This is the kind of thing that we hear every now and then on this list and every time it turns out someone else (who controls a parent pom, perhaps) made a change that wasn't communicated, or SOMETHING along those lines. Maven would not just start doing this out of the blue. I'm not aware of any obvious "oh that's in JIRA" explanation for what you're seeing. Its possible but highly unlikely that you've stumbled into a very odd bug... Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
