Mailing-List: contact users-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Users List" <users@maven.apache.org>
Received-SPF: pass (athena.apache.org: domain of Roland.Asmann@adesso.at
 designates 86.59.33.198 as permitted sender)
Message-ID: <50320.85.127.78.221.1262270526.squirrel@cfc.at>
In-Reply-To: <88c1b40912310634y1a4c774eub14a9747e69b933a@mail.gmail.com>
References: <62056.85.127.78.221.1262186811.squirrel@cfc.at>
    <4B3B7528.30402@gmail.com>
    <88c1b40912300750r5dd6a099xe76c0357abc0ca4f@mail.gmail.com>
    <52185.85.127.78.221.1262191742.squirrel@cfc.at>
    <88c1b40912300854t3b96f887t41588301f453fcf9@mail.gmail.com>
    <50049.85.127.78.221.1262193398.squirrel@cfc.at>
    <52bab8690912301152x66973ca3ifaf3e083d5e5068e@mail.gmail.com>
    <64056.85.127.78.221.1262263633.squirrel@cfc.at>
    <88c1b40912310634y1a4c774eub14a9747e69b933a@mail.gmail.com>
Date: Thu, 31 Dec 2009 15:42:06 +0100 (CET)
Subject: Re: Plugins and their versions
From: "Roland Asmann" <Roland.Asmann@adesso.at>
To: "Maven Users List" <users@maven.apache.org>
User-Agent: SquirrelMail/1.4.9a
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Importance: Normal

> 2009/12/31 Roland Asmann <Roland.Asmann@adesso.at>:
>> Indeed it does! Works like a charm!
>>
>> Only one problem now: it reports on several SNAPSHOT plugins, which I
>> actually DO want! I know it's not good practice to use snapshots, but
>> let
>> me explain my case here:
>>
>> I have a multi-module build, which is ALWAYS released in a single go.
>> One
>> of my modules is a plug-in that I actually need in the build, and I
>> always
>> want to use it in the same version as the whole project is in.
>>
>
> That is not allowed.
>
> All the plugins must be resolved before the build starts.
>
> When you start a release, the plugin will not have been built, so will
> not be available prior to setting up the build plan.
>
> in m3 IIRC your build will refuse to work full stop.
>
> You must release plugins separately from builds that consume them
>
> -Stephen

That sucks... But in m2.0.10 it still works, so I'll keep it in for now.

Roland

>
>> Now, during development, this would lead to a snapshot version, which at
>> time of release would make it a release version (I use the property
>> 'project.version' as a reference for the plug-in.
>>
>> Now, how can I explain to the enforcer-plugin that this single plug-in
>> indeed is allowed to be a snapshot? I'm hoping for a solution that
>> doesn't
>> mean implementing my own enforcer-rule... But if that what it takes,
>> I'll
>> do that. Just wanted to check if this is already possible, because I
>> think
>> this is not a very unusual use-case...
>>
>> Roland
>>
>>
>>>> Understood, but I'm not interested in the updates, I'm trying to track
>>>> down the plugins that have no version configured.
>>>>
>>>
>>> The enforcer plugin can help you find plugins with missing versions,
>>> too.
>>>
>>> Wayne
>>>
>>> ---------------------------------------------------------------------
>>> 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
>
>
>


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