(If I understand your problem correctly) by default release:prepare doesn't
run install goal which can cause issues like this, but you can configure
which preparation goals need to be run (also see my comment below from our
build why we need it):
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<configuration>
<!-- Needed because we use the dependency plugin to copy
native dependencies during the build, so they need to be available in the
local repository -->
<preparationGoals>clean install</preparationGoals>
Kalle
On Wed, Jun 18, 2008 at 5:46 PM, Hayes, Peter <[EMAIL PROTECTED]> wrote:
> I am using the checkstyle plugin for a multi-module build. As directed
> in the checkstyle documentation, I configured the checkstyle plugin to
> include a dependency on one of my sub projects like this :
>
> ...
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-checkstyle-plugin</artifactId>
> <dependencies>
> <dependency>
> <groupId>com.example.whizbang</groupId>
> <artifactId>build-tools</artifactId>
> <version>1.0-SNAPSHOT</version>
> </dependency>
> </dependencies>
> </plugin>
> ...
>
> When running a release build, the reference to the build tools version
> does not get updated to the target release version, even though the
> build-tools project is a sub-module of the project.
>
> Could the release plugin be enhanced to update this version?
>
> Checkstyle doc :
> http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/multi-m
> odule-config.html<http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/multi-module-config.html>
>
> Thanks,
>
> Peter Hayes
> Architecture & Shared Technology Services | Fidelity Investments
> Management Technology
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
