1) The Maven convention and good practice is to put ressources files like *.txt in src/main/resources. 2) The change you have is due to the new version 2.6 of the plugin which was released few days ago. To avoid such a surprise in the future, the good practice is to set the version of each plugin your are using the pluginsManagement of your (parent) pom. You can set it to 2.5.1 for the eclipse plugin to keep the old behavior. cheers
arnaud On Thu, Apr 9, 2009 at 5:28 AM, Zach Cox <zcox...@gmail.com> wrote: > Before this week, running "mvn eclipse:eclipse" would put a line like > this in .classpath: > > <classpathentry kind="src" path="src/main/java"/> > > Now this week it is putting this line in .classpath instead: > > <classpathentry kind="src" path="src/main/java" including="**/*.java"/> > > We have some .txt files that sit alongside .java files in the package > structure in src/main/java. When running "mvn compile" all of those > .txt files are copied into target/classes. Before this week, > rebuilding in Eclipse also copied those .txt files into > target/classes. However, now that the src/main/java line in > .classpath contains including="**/*.java", Eclipse no longer copies > the .txt files into target/classes. > > While I realize that technically only .java files should exist in > src/main/java, it's a pain to create a duplicate package hierarchy in > src/main/resources and this greatly reduces visibility of these .txt > files. > > Did something just recently change with eclipse:eclipse to cause it to > start putting including="**/*.java" in .classpath? Is there any way I > can get it to not put that in .classpath? > > Thanks, > Zach > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > -- Arnaud
