Maven 2 & 3

Remove support for profiles.xml

Details

  • Type: Task Task
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: 3.0-alpha-3
  • Component/s: Profiles
  • Labels:
    None
  • Complexity:
    Intermediate
  • Number of attachments :
    0

Description

As per r748226 support for profiles.xml will be dropped. Tracking this here as a user visible change for the release history.

Issue Links

is depended upon by

Bug - A problem which impairs or prevents the functions of the product. MNBMODULE-94 Do not use separate profiles.xml

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Will Horn added a comment -

Is there any documentation about this change? I don't see any here or in the commit log to explain the reason or the suggested alternatives. My use case of profiles.xml is to separate certain project settings out of the pom. These are mostly properties that change regularly from user to user and should not be committed to version control (e.g. custom output directory, build number).

Show
Will Horn added a comment - Is there any documentation about this change? I don't see any here or in the commit log to explain the reason or the suggested alternatives. My use case of profiles.xml is to separate certain project settings out of the pom. These are mostly properties that change regularly from user to user and should not be committed to version control (e.g. custom output directory, build number).
Hide
Permalink
Milos Kleint added a comment -

this doesn't sound like a "minor task" to me. The only way to have per-project non-sharable settings has been removed. Now only global per project settings are available in settings.xml.

It will cause me headaches in netbeans IDE integration eg. the deployment server TYPE is noted in the pom.xml as it's something that is usually shared across all developers, but the deployment server ID is stored in profiles.xml file because the ID token value is user installation based (can include path to the server installation)

Show
Milos Kleint added a comment - this doesn't sound like a "minor task" to me. The only way to have per-project non-sharable settings has been removed. Now only global per project settings are available in settings.xml. It will cause me headaches in netbeans IDE integration eg. the deployment server TYPE is noted in the pom.xml as it's something that is usually shared across all developers, but the deployment server ID is stored in profiles.xml file because the ID token value is user installation based (can include path to the server installation)
Hide
Permalink
Tuomas Kiviaho added a comment -

I think that the feature has become obsolete because it can be replaced with mixins (http://markmail.org/thread/6qqccwkrry5up2un). I just don't know how to do this.

Show
Tuomas Kiviaho added a comment - I think that the feature has become obsolete because it can be replaced with mixins ( http://markmail.org/thread/6qqccwkrry5up2un ). I just don't know how to do this.
Hide
Permalink
Milos Kleint added a comment -

the fact that mixins are mentioned to be placed in repository, doesn't make them a proper replacement of profiles.xml file for user-private settings..

Show
Milos Kleint added a comment - the fact that mixins are mentioned to be placed in repository, doesn't make them a proper replacement of profiles.xml file for user-private settings..
Hide
Permalink
Jörg Hohwiller added a comment - - edited

Please also note that profiles.xml was the suggested workaround to solve MNG-624.

Show
Jörg Hohwiller added a comment - - edited Please also note that profiles.xml was the suggested workaround to solve MNG-624 .

People

  • Assignee:
    Shane Isbell
    Reporter:
    Benjamin Bentmann
Vote (0)
Watch (5)

Dates

  • Created:
    Updated:
    Resolved: