I have the same end result with IBM Rational Application Developer 7.0 which is based on Eclipse 3.4. When I bring a project into a workspace, either creating a new one, importing or whatever, I have to delete the .settings directory and then run Maven | Update Project Configuration so that deploying to Websphere doesn't deploy 2 copies of all my dependencies and resources. Once this issue is taken care of I keep a command window open and update my test resources as needed. Using Maven4MyEclipse/MyEclipse 7.0 (which is based on 0.9.6 I believe) I don't have this issue.
-- Regards, Randy Burgess On Fri, Jan 16, 2009 at 1:01 AM, Andrew Zahra <[email protected]> wrote: > When I import a maven project I am finding that the src/test/java > directory has everything excluded. I removed the exclusion and now I can > right click and run as junit test, but I have found that I also need to > manually run the process-test-resources goal to get my resources processed > and in the class path. > > > > Has anyone had these problems that can suggest a solution? >
