This isn't a solution, but may help narrow down the scope of the issue:
Have you tried deleting your local repository before building the
snapshot version? My guess is that that will fail like the release
fails; if so, this suggests that the only reason the snapshot is
building is because the module dependencies are getting resolved
against a core snapshot from your local repository. (At least, this
would correspond with other behavior I've seen -- and would love to
know the solution for!)
Keith
On Tue, May 13, 2008 at 8:39 AM, Richard Chamberlain
<[EMAIL PROTECTED]> wrote:
> Hi,
>
>
>
> I've got a multi-module project set out like:
>
>
>
> Parent
>
> +-Module A
>
> +-Module B
>
> +-Core
>
>
>
> - Both module A and Module B are separate artefacts that need to be in
> sync with each other.
>
> - Both A and B depend on core
>
>
>
> The problem
>
> ----------------
>
> If the current version is 1.0-SNAPSHOT, this builds quite happily.
>
> When I do a release I get the error that the dependency core-1.0 cannot
> be found. But 1.0 hasn't had the chance to build yet!
>
>
>
> My project layout
>
> ---------------------
>
> Parent:
>
> <modules>
>
> <module>Core</module>
>
> <module>ModuleA</module>
>
> <module>ModuleB</module>
>
> </modules>
>
>
>
> Core
>
> ------
>
> <parent>
>
> <artifactId>Parent</artifactId>
>
> <groupId>com.myapp</groupId>
>
> <version>1.0-SNAPSHOT</version>
>
> </parent>
>
>
>
> Module A & B
>
> ------------
>
> <parent>
>
> <artifactId>Parent</artifactId>
>
> <groupId>com.myapp</groupId>
>
> <version>1.0-SNAPSHOT</version>
>
> <relativePath>../pom.xml</relativePath>
>
> </parent>
>
> ...
>
> <dependency>
>
> <groupId>com.myapp</groupId>
>
> <artifactId>core</artifactId>
>
> <version>${project.version}</version>
>
> </dependency>
>
>
>
> Thanks,
>
>
>
> Rich
>
>
>
>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
