Project specific alternate settings.xml

[Stevo Slavić <ss...@gmail.com>]

Hello Maven users,

Maven has notion of global (M2_HOME/conf/settings.xml), user settings
(typically in ~/.m2/settings.xml), and build specific alternate
settings (one specified in build command using -s switch).

What does community think, should there be a convention automated in
Maven logic of using project specific alternate settings?

E.g. settings.xml if present in same path as pom.xml from where build
is started could be used as alternate settings for that project build.

Dunno about community, but lots of my projects use project specific
Maven settings and repeating -s switch all the time is not nice, but
also merging multiple different project settings into user
settings.xml is even less desired - want to make sure that project
will build not just for my environment but for other devs and CI too.
Such project specific settings file could be used automatically buy CI
servers as well, just by checking out source code with settings.xml
included, and running Maven build.

Regards,
Stevo.

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

Re: Project specific alternate settings.xml

[Stevo Slavić <ss...@gmail.com>]

Server authentication for example, it can not be specified in pom.
Projects use project/client specific repository or repositories -
wouldn't like to mix settings of multiple projects in user settings,
to minimize chance of accessing repositories and resolving
dependencies from them in a project where they're not supposed to be
used from. Same project specific settings file used by all developers
on project, and CI, with credentials referenced via environment
variables - each developer specifies his own credentials, works for CI
build jobs.

Another one is to be able to specify project specific local repository
in project specific settings.xml, to minimize a chance of "it works
for me" scenario, just because someone was building another project
before build would pass for him but not for others.

Regards,
Stevo.

On Tue, Oct 11, 2011 at 6:32 PM, Ron Wheeler
<rw...@artifact-software.com> wrote:
> What sort of things do you want at the project level that can not be handled
> by a parent pom?
>
> Ron
>
> On 11/10/2011 9:56 AM, Stevo Slavić wrote:
>>
>> Hello Maven users,
>>
>> Maven has notion of global (M2_HOME/conf/settings.xml), user settings
>> (typically in ~/.m2/settings.xml), and build specific alternate
>> settings (one specified in build command using -s switch).
>>
>> What does community think, should there be a convention automated in
>> Maven logic of using project specific alternate settings?
>>
>> E.g. settings.xml if present in same path as pom.xml from where build
>> is started could be used as alternate settings for that project build.
>>
>> Dunno about community, but lots of my projects use project specific
>> Maven settings and repeating -s switch all the time is not nice, but
>> also merging multiple different project settings into user
>> settings.xml is even less desired - want to make sure that project
>> will build not just for my environment but for other devs and CI too.
>> Such project specific settings file could be used automatically buy CI
>> servers as well, just by checking out source code with settings.xml
>> included, and running Maven build.
>>
>> Regards,
>> Stevo.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
>
> --
> Ron Wheeler
> President
> Artifact Software Inc
> email: rwheeler@artifact-software.com
> skype: ronaldmwheeler
> phone: 866-970-2435, ext 102
>
>
>
>
> ---------------------------------------------------------------------
> 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: Project specific alternate settings.xml

[Ron Wheeler <rw...@artifact-software.com>]

What sort of things do you want at the project level that can not be 
handled by a parent pom?

Ron

On 11/10/2011 9:56 AM, Stevo Slavić wrote:
> Hello Maven users,
>
> Maven has notion of global (M2_HOME/conf/settings.xml), user settings
> (typically in ~/.m2/settings.xml), and build specific alternate
> settings (one specified in build command using -s switch).
>
> What does community think, should there be a convention automated in
> Maven logic of using project specific alternate settings?
>
> E.g. settings.xml if present in same path as pom.xml from where build
> is started could be used as alternate settings for that project build.
>
> Dunno about community, but lots of my projects use project specific
> Maven settings and repeating -s switch all the time is not nice, but
> also merging multiple different project settings into user
> settings.xml is even less desired - want to make sure that project
> will build not just for my environment but for other devs and CI too.
> Such project specific settings file could be used automatically buy CI
> servers as well, just by checking out source code with settings.xml
> included, and running Maven build.
>
> Regards,
> Stevo.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>


-- 
Ron Wheeler
President
Artifact Software Inc
email: rwheeler@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102