Maybe try something like:
<build>
[...]
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-scm-plugin</artifactId>
<version>1.0-SNAPSHOT</version>
<executions>
<execution
<http://maven.apache.org/ref/2.0.4/maven-model/maven.html#class_execution>>
<id>Update scm</id>
<phase>validate</phase>
<goals>update</goals>
</execution>
</executions>
</plugin>
[...]
</plugins
[...]
</build>
But I don't think it is recommended to do it this way, maybe activate it
with a profile or indeed looking into a real continuous build server.
Hth,
Nick Stolwijk
Eric Miles wrote:
I'd recommend automating that via a system like Continuum or Cruise
Control. I'm not sure there's any other way to do that directly with
the POM or not...
On Fri, 2007-09-07 at 10:06 -0400, Mark Eramo wrote:
Hello,
Can anyone point me to detailed information and maybe some examples
on how to integrate maven and subversion. Ideally I would like to be
able to have the build fetch the latest code from subversion before I do
the build. I have looked at the documentation on the Maven site but I am
looking for more information then that on how to actually use the commands.
Regards,
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]