I thought I had solved it, but I didn't. The solution lay in moving the particular troublesome module higher up in the build order. I couldn't find any conflicts, but there must have been some. I did not use the specification of the version in a parent pom.
Hope this helps someone. johoso wrote: > > It seems like it works when I run it in Eclipse (Version: 3.4.1 Build id: > M20080911-1700, Maven plugin: Maven Integration for Eclipse by Sonatype > v0.9.6) > > But not in the following environment: > @mvn -version > Maven version: 2.0.9 > Java version: 1.6.0_06 > OS name: "sunos" version: "5.10" arch: "sparc" Family: "unix" > > However the workaround by Rémy works for the unix environment. > -- View this message in context: http://www.nabble.com/It%27s-works%2C-but-I-don%27t-understand-why...-tp21215546p25492254.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
