Ok. I think I found the example, and it uses environment properties. Should
work.
Or, define a profile in your settings.xml that defines these properties. The
benefit of this approach is that they can easily be defined (or overridden)
through the command line as well.

/Anders

On Fri, Sep 25, 2009 at 11:07, Anders Hammar <and...@hammar.net> wrote:

> Hmm, I pretty sure I've seen an example of this somewhere. I'll have a
> look....
>
> /A
>
>
> On Fri, Sep 25, 2009 at 11:06, Todor Boev <t.b...@prosyst.bg> wrote:
>
>> That was my first idea. And I couldn't find a way to do it. All I find are
>> discussions on how people want not to have this in their settings.xml but in
>> an external properties file. How to put arbitrary properties in the
>> settings.xml remains a mistery to me.
>>
>>
>> Anders Hammar wrote:
>>
>>> Why not have two pre-define properties for this, which everyone needs to
>>> set
>>> up in their settings.xml?
>>>
>>> /Anders
>>>
>>> On Fri, Sep 25, 2009 at 10:48, Todor Boev <t.b...@prosyst.bg> wrote:
>>>
>>>  Hi,
>>>> I am using the release plugin with CVS. Is there a way to remove the CVS
>>>> user name and password from the pom.xml? I am setting up a maven project
>>>> for
>>>> 20+ developers and it would be bad if every one of them needs to keep a
>>>> modified pom.xml in their machine with their user name. I tried the
>>>> maven-properties-plugin but the problem I does not run when I do
>>>> "release:prepare". I can't discover the proper lifecycle phase where to
>>>> hook
>>>> the  properties plugin so it runs both on normal build and on release.
>>>>
>>>> Cheers,
>>>> Todor
>>>>
>>>> ---------------------------------------------------------------------
>>>> 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