You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Peter Niederwieser <pn...@gmail.com> on 2009/11/19 11:46:31 UTC
Problem with maven-release-plugin
In my multi-module project, I have a Maven plugin A and a module B that uses
version ${project.version} of A (all modules have the same version number).
release:prepare changes version A from 0.3-SNAPSHOT to 0.3, but then fails
while processing B because it cannot find version 0.3 of A. Any ideas how to
solve this problem?
Cheers,
Peter
--
View this message in context: http://old.nabble.com/Problem-with-maven-release-plugin-tp26421272p26421272.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Problem with maven-release-plugin
Posted by Stevo Slavić <ss...@gmail.com>.
Maybe this <http://jira.codehaus.org/browse/MRELEASE-467> known issue is
related.
Regards,
Stevo.
On Thu, Nov 19, 2009 at 11:50 AM, Stephen Connolly <
stephen.alan.connolly@gmail.com> wrote:
> Two options:
>
> 1. change your build so that it will work with "clean verify" whenyour
> local repository has been blown away. Typically this is because you
> are using goals like dependency:copy and not
> dependency:copy-dependencies
>
> 2. change the preparation goals in the release plugin to "clean install".
>
> #2 is a hack, but may be necessary. In the long run #1 is to be preferred.
>
> -Stephen
>
> 2009/11/19 Peter Niederwieser <pn...@gmail.com>:
> >
> > In my multi-module project, I have a Maven plugin A and a module B that
> uses
> > version ${project.version} of A (all modules have the same version
> number).
> > release:prepare changes version A from 0.3-SNAPSHOT to 0.3, but then
> fails
> > while processing B because it cannot find version 0.3 of A. Any ideas how
> to
> > solve this problem?
> >
> > Cheers,
> > Peter
> > --
> > View this message in context:
> http://old.nabble.com/Problem-with-maven-release-plugin-tp26421272p26421272.html
> > Sent from the Maven - Users mailing list archive at Nabble.com.
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: Problem with maven-release-plugin
Posted by Stephen Connolly <st...@gmail.com>.
Two options:
1. change your build so that it will work with "clean verify" whenyour
local repository has been blown away. Typically this is because you
are using goals like dependency:copy and not
dependency:copy-dependencies
2. change the preparation goals in the release plugin to "clean install".
#2 is a hack, but may be necessary. In the long run #1 is to be preferred.
-Stephen
2009/11/19 Peter Niederwieser <pn...@gmail.com>:
>
> In my multi-module project, I have a Maven plugin A and a module B that uses
> version ${project.version} of A (all modules have the same version number).
> release:prepare changes version A from 0.3-SNAPSHOT to 0.3, but then fails
> while processing B because it cannot find version 0.3 of A. Any ideas how to
> solve this problem?
>
> Cheers,
> Peter
> --
> View this message in context: http://old.nabble.com/Problem-with-maven-release-plugin-tp26421272p26421272.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
AW: Problem with maven-release-plugin
Posted by Mark Struberg <st...@yahoo.de>.
Peter,
use the <dependencyManagement> section in the parent pom to pin down the versions of the single child modules.
LieGrue,
strub
--- Peter Niederwieser <pn...@gmail.com> schrieb am Do, 19.11.2009:
> Von: Peter Niederwieser <pn...@gmail.com>
> Betreff: Problem with maven-release-plugin
> An: users@maven.apache.org
> Datum: Donnerstag, 19. November 2009, 11:46
>
> In my multi-module project, I have a Maven plugin A and a
> module B that uses
> version ${project.version} of A (all modules have the same
> version number).
> release:prepare changes version A from 0.3-SNAPSHOT to 0.3,
> but then fails
> while processing B because it cannot find version 0.3 of A.
> Any ideas how to
> solve this problem?
>
> Cheers,
> Peter
> --
> View this message in context: http://old.nabble.com/Problem-with-maven-release-plugin-tp26421272p26421272.html
> Sent from the Maven - Users mailing list archive at
> Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org