You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Daniel Clemente (JIRA)" <ji...@codehaus.org> on 2007/08/13 17:49:47 UTC
[jira] Created: (MNG-3148) Write at the debug output the name of
the used settings.xml and the path of the repository
Write at the debug output the name of the used settings.xml and the path of the repository
------------------------------------------------------------------------------------------
Key: MNG-3148
URL: http://jira.codehaus.org/browse/MNG-3148
Project: Maven 2
Issue Type: Improvement
Components: Settings
Affects Versions: 2.0.7
Reporter: Daniel Clemente
Priority: Minor
When used with the -X option (debug), Maven should also say at least:
- which configuration file (settings.xml) it's trying to use, or if it hasn't found anyone
- the path of the repository which will be used
That's important since a lot of problems occur when you think that you (and Eclipse) are using a repository but Maven is saving all new things in other place. I experienced these problems after a move of the repository and the settings.xml and it was very hard to discover that Maven wasn't really using my ~/.m2/settings.xml
--
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] Closed: (MNG-3148) Write at the debug output the name of the
used settings.xml and the path of the repository
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter closed MNG-3148.
-----------------------------
Resolution: Duplicate
Fix Version/s: (was: 2.2.x)
already done in at least 3.0-alpha-5
> Write at the debug output the name of the used settings.xml and the path of the repository
> ------------------------------------------------------------------------------------------
>
> Key: MNG-3148
> URL: http://jira.codehaus.org/browse/MNG-3148
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Settings
> Affects Versions: 2.0.7
> Reporter: Daniel Clemente
> Priority: Minor
>
> When used with the -X option (debug), Maven should also say at least:
> - which configuration file (settings.xml) it's trying to use, or if it hasn't found anyone
> - the path of the repository which will be used
> That's important since a lot of problems occur when you think that you (and Eclipse) are using a repository but Maven is saving all new things in other place. I experienced these problems after a move of the repository and the settings.xml and it was very hard to discover that Maven wasn't really using my ~/.m2/settings.xml
--
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] Updated: (MNG-3148) Write at the debug output the name of
the used settings.xml and the path of the repository
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MNG-3148:
------------------------------
Fix Version/s: 2.0.x
> Write at the debug output the name of the used settings.xml and the path of the repository
> ------------------------------------------------------------------------------------------
>
> Key: MNG-3148
> URL: http://jira.codehaus.org/browse/MNG-3148
> Project: Maven 2
> Issue Type: Improvement
> Components: Settings
> Affects Versions: 2.0.7
> Reporter: Daniel Clemente
> Priority: Minor
> Fix For: 2.0.x
>
>
> When used with the -X option (debug), Maven should also say at least:
> - which configuration file (settings.xml) it's trying to use, or if it hasn't found anyone
> - the path of the repository which will be used
> That's important since a lot of problems occur when you think that you (and Eclipse) are using a repository but Maven is saving all new things in other place. I experienced these problems after a move of the repository and the settings.xml and it was very hard to discover that Maven wasn't really using my ~/.m2/settings.xml
--
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