Release plugin cannot proceed with snapshot dependencies including
build plugin.
The main rational is it want to guarantee the release code is
producible.  Note snapshots
can go away any time and it can have behaviors changed any time.

-D


On Sun, Sep 6, 2009 at 9:52 PM, is_maximum<mnr...@gmail.com> wrote:
>
> Hi
> We are using Maven release plugin version 2 beta 9
> 1 - We've got some problem in releasing our applications. There are a bunch
> of projects defined in our company and each is being developed by a team.
> Because we are in developing phase for some dependencies we use SNAPSHOT
> versions and we don't want to provide release version for every small change
> but this plugin don't proceed if there is a SNAPSHOT dependency, however it
> asks if you want to check project dependency. Those dependencies need not to
> be released because they are used as library.
>
> 2 - The plugin will stop going if there is a SNAPSHOT plugin as well. I
> don't think this is good because the maven plugins we use might be in
> SNAPSHOT version. maven plugins are not project dependencies actually, they
> are maven dependencies. However in interactive mode it asks which dependency
> to be checked and I choose Project dependency but the plugin goes to
> investigate plugins as well
>
>
>
> -----
> --
> Regards
> Mohammad
> http://pixelshot.wordpress.com Pixelshot
> --
> View this message in context: 
> http://n2.nabble.com/problem-regarding-maven-release-plugin-tp3595500p3595500.html
> Sent from the maven users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Reply via email to