[jira] Commented: (MNG-4060) Remove support for profiles.xml

2010-08-20 Thread JIRA

[ 
http://jira.codehaus.org/browse/MNG-4060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=232652#action_232652
 ] 

Jörg Hohwiller commented on MNG-4060:
-

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

> Remove support for profiles.xml
> ---
>
> Key: MNG-4060
> URL: http://jira.codehaus.org/browse/MNG-4060
> Project: Maven 2 & 3
>  Issue Type: Task
>  Components: Profiles
>Reporter: Benjamin Bentmann
>Assignee: Shane Isbell
>Priority: Minor
> Fix For: 3.0-alpha-3
>
>
> As per [r748226|http://svn.eu.apache.org/viewvc?view=rev&revision=748226] 
> support for {{profiles.xml}} will be dropped. Tracking this here as a user 
> visible change for the release history.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] Commented: (MNG-4060) Remove support for profiles.xml

2009-11-27 Thread Milos Kleint (JIRA)

[ 
http://jira.codehaus.org/browse/MNG-4060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=199719#action_199719
 ] 

Milos Kleint commented on MNG-4060:
---

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..


> Remove support for profiles.xml
> ---
>
> Key: MNG-4060
> URL: http://jira.codehaus.org/browse/MNG-4060
> Project: Maven 2
>  Issue Type: Task
>  Components: Profiles
>Reporter: Benjamin Bentmann
>Assignee: Shane Isbell
>Priority: Minor
> Fix For: 3.0-alpha-3
>
>
> As per [r748226|http://svn.eu.apache.org/viewvc?view=rev&revision=748226] 
> support for {{profiles.xml}} will be dropped. Tracking this here as a user 
> visible change for the release history.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] Commented: (MNG-4060) Remove support for profiles.xml

2009-11-27 Thread Tuomas Kiviaho (JIRA)

[ 
http://jira.codehaus.org/browse/MNG-4060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=199718#action_199718
 ] 

Tuomas Kiviaho commented on MNG-4060:
-

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.

> Remove support for profiles.xml
> ---
>
> Key: MNG-4060
> URL: http://jira.codehaus.org/browse/MNG-4060
> Project: Maven 2
>  Issue Type: Task
>  Components: Profiles
>Reporter: Benjamin Bentmann
>Assignee: Shane Isbell
>Priority: Minor
> Fix For: 3.0-alpha-3
>
>
> As per [r748226|http://svn.eu.apache.org/viewvc?view=rev&revision=748226] 
> support for {{profiles.xml}} will be dropped. Tracking this here as a user 
> visible change for the release history.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] Commented: (MNG-4060) Remove support for profiles.xml

2009-11-27 Thread Milos Kleint (JIRA)

[ 
http://jira.codehaus.org/browse/MNG-4060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=199715#action_199715
 ] 

Milos Kleint commented on MNG-4060:
---

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)


> Remove support for profiles.xml
> ---
>
> Key: MNG-4060
> URL: http://jira.codehaus.org/browse/MNG-4060
> Project: Maven 2
>  Issue Type: Task
>  Components: Profiles
>Reporter: Benjamin Bentmann
>Assignee: Shane Isbell
>Priority: Minor
> Fix For: 3.0-alpha-3
>
>
> As per [r748226|http://svn.eu.apache.org/viewvc?view=rev&revision=748226] 
> support for {{profiles.xml}} will be dropped. Tracking this here as a user 
> visible change for the release history.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] Commented: (MNG-4060) Remove support for profiles.xml

2009-05-07 Thread Will Horn (JIRA)

[ 
http://jira.codehaus.org/browse/MNG-4060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=175461#action_175461
 ] 

Will Horn commented on MNG-4060:


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).

> Remove support for profiles.xml
> ---
>
> Key: MNG-4060
> URL: http://jira.codehaus.org/browse/MNG-4060
> Project: Maven 2
>  Issue Type: Task
>  Components: Profiles
>Reporter: Benjamin Bentmann
>Assignee: Shane Isbell
>Priority: Minor
> Fix For: 3.0-alpha-3
>
>
> As per [r748226|http://svn.eu.apache.org/viewvc?view=rev&revision=748226] 
> support for {{profiles.xml}} will be dropped. Tracking this here as a user 
> visible change for the release history.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira