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

[Robert Scholte]

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/

[BRIAN FOX-5]

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

On Wed, Jun 24, 2009 at 4:31 AM, Robert Scholte<rfscholte@...> 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@...
For additional commands, e-mail: dev-help@...

[Stan Devitt-3]

A major difference is that the settings.xml file is not stored with the project source.

If your project depends on the profile(s) in some crucial way the information should be archived with the project.  In that case the settings.xml is not an option.

Stan

----- Original Message -----
From: Brian Fox <brianf@...>
To: Maven Developers List <dev@...>
Sent: Wed Jun 24 12:22:33 2009
Subject: Re: User's project-specific properties ability disabled after MNG-4060

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

On Wed, Jun 24, 2009 at 4:31 AM, Robert Scholte<rfscholte@...> 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@...
For additional commands, e-mail: dev-help@...


---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.

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

[Robert Scholte]

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<[e-mail]> 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: [e-mail]
For additional commands, e-mail: [e-mail]

[BRIAN FOX-5]

Well, the mixin support should cover the profiles.xml and more....even
better it should be possible to resolve the mixins from the repository which
means they are versioned and deployed artifacts like everything else.

On Wed, Jun 24, 2009 at 11:41 AM, Robert Scholte <rfscholte@...>wrote:

>
> 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@...>
> > 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@...
> > For additional commands, e-mail: dev-help@...
> >
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/User%27s-project-specific-properties-ability-disabled-after-MNG-4060-tp24183522p24190525.html
> Sent from the Maven Developers mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>
>

[Robert Scholte]

I didn't say it's not possible without profiles.xml, but without it you have to make a choice between the best of the worst.
Let's stick to the passwords. You don't want to expose them in the pom.xml, right?
But what if project A en project B both have a ${password} in their pom.xml, from the settings.xml you can't figure out which password to use, UNLESS you have to keep settings the specific profile per project. Not really nice.
But let me reverse the question. Why was the profiles.xml introduced and what made it the team to say goodbye to this file?

Robert

BRIAN FOX-5 wrote:

Well, the mixin support should cover the profiles.xml and more....even
better it should be possible to resolve the mixins from the repository which
means they are versioned and deployed artifacts like everything else.

On Wed, Jun 24, 2009 at 11:41 AM, Robert Scholte <[e-mail]>wrote:

>
> 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<[e-mail]>
> > 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: [e-mail]
> > For additional commands, e-mail: [e-mail]
> >
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/User%27s-project-specific-properties-ability-disabled-after-MNG-4060-tp24183522p24190525.html
> Sent from the Maven Developers mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [e-mail]
> For additional commands, e-mail: [e-mail]
>
>