On Mon, Oct 11, 2010 at 10:00 PM, emerson <[email protected]> wrote: > Hi > > I configured a integration test only project, in a way that every > module uses a configuration that is stored in the parent folder. > I implemented this way: > > In the parent pom (in the root of the tree): > > <properties> > <envType>local</envType> <!-- Default Environment value --> > <envProps>../autotestProperties/</envProps> > </properties> > <build> > <resources> > <resource> > <directory>${envProps}/resources</directory> > <filtering>true</filtering> > </resource> > </resources> > <filters> > <filter>${envProps}/env/${envType}.properties</filter> > </filters> > > Then each module will get the generated configuration at the classpath. > > As far as maven goes, it works fine, but when I generate the > correspondent eclipse project, it tries to add the resource entry, but > all it gets is a incorrect build path entry: > > "Build path entry is missing: > home/emerson/workspace/trunk/autotests/autotestProperties/resources" > > Is there anyway to stop eclipse from trying to create this entry? > > The normal use of this will be for the developers and qa to create the > project structure using "maven eclipse:eclipse install -DskipTests" > once via maven and then run the tests straight from eclipse.
The first step is to run eclipse:eclipse Then copy the generated files somewhere. The second step is to manually fix eclipse so that it is how you expect it. Then copy those files somewhere. Compare the two and file a bug report http://maven.apache.org/plugins/maven-eclipse-plugin/ Better yet, download the source, run a new integration test and then a fix for the problem before you submit the bug report. A lot of people are moving to m2eclipse http://m2eclipse.sonatype.org/. There are only a few developers looking at m-e-p. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
