I tried the m2eclipse, but that also seems to import a wrong build path.

I have the following entry on my parent pom.xml

<build>
<testResources>
      <testResource>
        <directory>src/test/scenarios</directory>
      </testResource>
    </testResources>
<plugins>
 <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-surefire-plugin</artifactId>
        <configuration>
          <testResources>
            <testResource>
              <directory>src/test/scenarios</directory>
            </testResource>
          </testResources>
          <excludes>
            <exclude>**/*Steps.java</exclude>
            <exclude>../*Steps.java</exclude>
          </excludes>
          <testFailureIgnore>true</testFailureIgnore>
        </configuration>
      </plugin>
      <plugin>
<plugin>
        <groupId>org.codehaus.mojo</groupId>
        <artifactId>build-helper-maven-plugin</artifactId>
        <version>1.5</version>
        <executions>
          <execution>
            <id>add-source</id>
            <phase>generate-sources</phase>
            <goals>
              <goal>add-source</goal>
            </goals>
            <configuration>
              <sources>
                <source>/src/test/scenarios</source>
              </sources>
            </configuration>
          </execution>
        </executions>
      </plugin>


When I import the project using eclipse2m, the source folder entry for
the src/test/scenarios have Included: (All) and Excluded: **

That causes the jbehave tests to not to run properly, which is even
worse than using the maven eclipse plugin to generate the eclipse
files.

Any idea if I'm doing something wrong?

Also an unrelated question, is it really necessary to add the
build-helper-maven-plugin and the maven-surefire-plugin bits of
configuration for tests to read from the scenarios folder?

Regards
Emerson

On 13 October 2010 13:39, Antonio Petrelli <antonio.petre...@gmail.com> wrote:
> 2010/10/13 emerson <echofloripa.y...@gmail.com>:
>> Does the m2eclipse creates eclipse config from the pom, ina
>> multi-module configuration?
>
> it creates one Eclipse project per module, plus the project for the master 
> pom.
> And, obviously, the config files.
>
> Antonio
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Reply via email to