Stephen Connolly wrote:
> On Tue, Sep 2, 2008 at 11:08 PM, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
>> Stephen Connolly wrote:
>>> On Tue, Sep 2, 2008 at 9:40 PM, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
>>>> Hi Stephen
>>>>
>>>> Great work on this plugin! This is a plugin that I plan to use extensively.
>>>>
>>>> I've read through the docs, which there are plenty of. Always a good
>>>> sign :-) There were however a couple of typos and broken links in there,
>>>> which I took the liberty of fixing in SVN. I also updated to mojo-parent 
>>>> 18.
>>>>
>>> Thanks, I forgot I had to switch back to mojo-parent 18
>>>
>>>> After playing around with the plugin a bit I found the results somewhat
>>>> confusing, so I started to read the goal parameter docs. There I found
>>>> the source of my confusion: the allowSnapshots parameter has true as
>>>> default value. In my opinion this should be set to false as default.
>>>> Using snapshots is something that should be avoided, if possible.
>>>> Showing snapshot versions by default therefor works against best
>>>> practices and might lure users to the dark side.
>>>>
>>> I'm 50:50 on this.
>>>
>>> I use it to switch all the suit of projects onto SNAPSHOT versions
>>> while I'm working on them.  When doing a release the release will be
>>> the newest version in the repo so puching back to SCM is fine in that
>>> case.
>>>
>>> However I can see the other side.
>> There are apparently different use cases for this goal. Here's my use
>> case. One step in our release process is to check to see if there are
>> any dependencies that should be updated. When doing that I don't want
>> any snapshots, because the release is near.
> 
> just add -DallowSnapshots=false

Yes, for me that's not a problem.

My main concern is the signals we will be sending to the users, telling
them to update to snapshot versions.


<snip/>

-- 
Dennis Lundberg

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to