If mvn version is a problem, it's possible to have a mvn plugin that
guarantees that you're running "the right version" of mvn (and java,
for that matter).
Check it out:
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-enforcer-plugin</artifactId>
<executions>
<execution>
<id>enforce-versions</id>
<goals>
<goal>enforce</goal>
</goals>
<configuration>
<rules>
<requireMavenVersion>
<version>2.0.9</version>
</requireMavenVersion>
<requireJavaVersion>
<version>1.6</version>
</requireJavaVersion>
</rules>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
More details at
http://maven.apache.org/plugins/maven-enforcer-plugin/
Craig
On Dec 10, 2008, at 3:20 AM, Sahoo wrote:
> Wolfram Rittmeyer wrote:
>> Sahoo wrote:
>>> Are you using mvn 2.0.9 or not?
>>>
>>
>> No, it's mvn 2.0.8. This would solve the problem?
>>
> Yes, most likely. See [1]. BTW, the wikipage does mention the mvn
> version as 2.0.9. You might have missed that.
>
> Thanks,
> Sahoo
>
> [1] http://www.nabble.com/Does-the-trunk-build--tt20025310.html#a20077537
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>
Craig L Russell
Architect, Sun Java Enterprise System
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell_at_sun.com
P.S. A good JDO? O, Gasp!