Well thank you Mauro for taking some time on a non-jbehave related problem.
2012/11/18 Mauro Talevi <[email protected]> > Hi Louis, > > the root of the problem is in your configuration of the resources plugin: > > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-resources-plugin</artifactId> > <version>${maven-resources-plugin.version}</version> > <configuration> > <encoding>${project.build.sourceEncoding}</encoding> > > <outputDirectory>${project.build.outputDirectory}</outputDirectory> > </configuration> > </plugin> > > > You're forcing mvn to always copy to the outputDirectory (i.e. > target/classes), whereas mvn will by default choose to copy to the > testOutputDirectory (i.e. target/test-classes) for the test resources. > > Just remove the <outputDirectory> and it'll work. > > Cheers > > > On 13/11/2012 18:01, louis gueye wrote: > > Thx Mauro. > It's true. The weird thing is that they are copied to target/classes > I could not manage to copy them to target/test-classes so I referenced a > class present in target/classes so that jbehave could find my .story files. > Seems to be a maven issue/misuage ... > If I get any insight on the topic I'll update the post. > > Louis > -- > Cordialement/Regards, > > Louis GUEYE > linkedin <http://fr.linkedin.com/in/louisgueye> | > blog<http://deepintojee.wordpress.com/> > | twitter <http://twitter.com/#%21/lgueye> > > > 2012/11/13 Mauro Talevi <[email protected]> > >> It's looking for the .story files in target/test-classes/... but it's >> not finding them. >> >> You have modified the default test-resources handling of Maven and you >> need to ensure that the test-resources are copied to target/test-classes. >> >> > > -- Cordialement/Regards, Louis GUEYE linkedin <http://fr.linkedin.com/in/louisgueye> | blog<http://deepintojee.wordpress.com/>| twitter <http://twitter.com/#%21/lgueye>
