« Return to Thread: User's project-specific properties ability disabled after MNG-4060

Re: User's project-specific properties ability disabled after MNG-4060

by Robert Scholte :: Rate this Message:

In the settings.xml it's not possible to activate a profile by project. Then again: I believe settings.xml are actually maven-settings and not project-settings. For most users it's a big step to dive into the settings.xml. For them there are only a few reasons to access the settings file:
- to setup a proxy repository like nexus (which is often done by a more experienced user)
- to set username+pw for a specific server.
If they don't have to touch the file then leave it, 'cause changes here might break maven.
And a user-specific project-profile has to be located on a very logic and easy to access location, so the best option is next to the pom I guess.

-regards,

Robert Scholte

BRIAN FOX-5 wrote:

Why not just put those values into the settings.xml?

On Wed, Jun 24, 2009 at 4:31 AM, Robert Scholte<rfscholte@codehaus.org> wrote:
>
> I heard some time ago that the profiles.xml were removed in Maven3. Although I'm still using 2.1.0 I want to be prepared for such changes.
>
> IMHO I think it's a bad choice to remove this option.
>
>
>
> Maven should provide some sort of way where developers can set/change project properties without having to change the pom.xml.
>
> I believe the pom should not contain developer-specific properties and which can or will end up in any scm. Think of datasource-properties.
>
>
>
> There are three degrees of properties:
>
> - the global properties (combined with the activeByDefault-profile)
>
> - profile-properties (where profiles cover multiple users. By OS, 'stage')
>
> - personal properties.
>
>
>
> These personal properties can only be used with a personal profile. A personal profile is the best example of data which doesn´t belong in a pom but in a separate file (and probably not in scm).
>
> Personal properties should be somewhere close to the project, like in the root of the project (yes, like the profiles.xml).
>
> The both settings.xml is too far from the project and there's no option in the (user's) settings.xml to set project-specific properties.
>
>
>
> I think that if there was a vote concerning this issue it might result in a long discussion. It's never too late for that, so let's give it a try.
>
>
>
> _________________________________________________________________
> Express yourself instantly with MSN Messenger! Download today it's FREE!
> http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

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

« Return to Thread: User's project-specific properties ability disabled after MNG-4060