You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Andreas Guther <An...@markettools.com> on 2007/04/01 17:59:20 UTC
Maven release plug-in and SNAPSHOT dependencies
We are using the Maven 2 release plug-in for our release process.
The plug-in checks for SNAPSHOT dependencies and refuses to proceed in
case it finds a SNAPSHOT dependency. This makes perfectly sense and is
what is desired.
What I do not understand is the fact that it also checks in my reporting
section and if it finds there a SNAPSHOT dependency it applies the same
rule. The reporting is not needed or used for a release. My problem is
that we are using the stat-scm plug-in for our reports which is not
available as a full version, only as a SNAPSHOT.
Is there a way to tell the release plug-in to ignore specific profiles
or for example the reporting section for its SNAPSHOT dependency checks?
Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Maven release plug-in and SNAPSHOT dependencies
Posted by Andreas Guther <An...@markettools.com>.
I was thinking the same as a workaround solution. It is always possible
to use a classifier to mark the version as an internal release.
-----Original Message-----
From: Wayne Fay [mailto:waynefay@gmail.com]
Sent: Sunday, April 01, 2007 9:10 PM
To: Maven Users List
Subject: Re: Maven release plug-in and SNAPSHOT dependencies
The advice generally given in these kinds of situations is that you
create a "release" of the offending artifact either with your own fake
non-snapshot version or under your own groupId with a non-snapshot
version.
So in this case, I would probably create a release of the stat-scm
plugin with version 0.9.0 or something and specify that version in my
pom. This assumes of course that no 0.9.0 version is ever expected to
be released by the "official" provider of the stat-scm plugin.
Then when the official 1.0.0 release is available, you can start using
it instead by simply changing the version specified in the pom. But in
the meantime, you can cut releases of your own projects with this fake
non-snapshot build.
Wayne
On 4/1/07, Andreas Guther <An...@markettools.com> wrote:
> We are using the Maven 2 release plug-in for our release process.
>
> The plug-in checks for SNAPSHOT dependencies and refuses to proceed in
> case it finds a SNAPSHOT dependency. This makes perfectly sense and
is
> what is desired.
>
> What I do not understand is the fact that it also checks in my
reporting
> section and if it finds there a SNAPSHOT dependency it applies the
same
> rule. The reporting is not needed or used for a release. My problem
is
> that we are using the stat-scm plug-in for our reports which is not
> available as a full version, only as a SNAPSHOT.
>
> Is there a way to tell the release plug-in to ignore specific profiles
> or for example the reporting section for its SNAPSHOT dependency
checks?
>
> Andreas
>
>
>
> ---------------------------------------------------------------------
> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Maven release plug-in and SNAPSHOT dependencies
Posted by Wayne Fay <wa...@gmail.com>.
The advice generally given in these kinds of situations is that you
create a "release" of the offending artifact either with your own fake
non-snapshot version or under your own groupId with a non-snapshot
version.
So in this case, I would probably create a release of the stat-scm
plugin with version 0.9.0 or something and specify that version in my
pom. This assumes of course that no 0.9.0 version is ever expected to
be released by the "official" provider of the stat-scm plugin.
Then when the official 1.0.0 release is available, you can start using
it instead by simply changing the version specified in the pom. But in
the meantime, you can cut releases of your own projects with this fake
non-snapshot build.
Wayne
On 4/1/07, Andreas Guther <An...@markettools.com> wrote:
> We are using the Maven 2 release plug-in for our release process.
>
> The plug-in checks for SNAPSHOT dependencies and refuses to proceed in
> case it finds a SNAPSHOT dependency. This makes perfectly sense and is
> what is desired.
>
> What I do not understand is the fact that it also checks in my reporting
> section and if it finds there a SNAPSHOT dependency it applies the same
> rule. The reporting is not needed or used for a release. My problem is
> that we are using the stat-scm plug-in for our reports which is not
> available as a full version, only as a SNAPSHOT.
>
> Is there a way to tell the release plug-in to ignore specific profiles
> or for example the reporting section for its SNAPSHOT dependency checks?
>
> Andreas
>
>
>
> ---------------------------------------------------------------------
> 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