>> Not including .java files in wars is the default for Maven. ... > Yes, that appears to be what happens here... but -DskipSource=false > doesn't make any difference. Is there some other option to control this?
Maven is not just a build tool, it is also a collection of best practices. One of those best practices is that Java code should be in Jar projects, and then War projects should depend on one or more Jar projects to pull in (compiled) Java code to use in your Webapp. You can see this for yourself if you build a new project using the j2ee archetype. So the "right" approach would be to move your Java code to a Jar project and then maybe try building again, and specifying the -DskipSource=false at that point. Alternatively, you should be able to configure a <resource> in the War project that includes src/main/java, and the java files should land in your War file. Not sure why you'd want this unless you're working on a GWT project, though. And in that case, you might want to have a look at the gwt-maven-plugin. Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
