You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Justin Edelson (JIRA)" <ji...@codehaus.org> on 2006/08/03 18:32:01 UTC
[jira] Created: (MNGECLIPSE-174) settings.xml ignored when building
classpath
settings.xml ignored when building classpath
--------------------------------------------
Key: MNGECLIPSE-174
URL: http://jira.codehaus.org/browse/MNGECLIPSE-174
Project: Maven 2.x Extension for Eclipse
Issue Type: Bug
Affects Versions: 0.0.10
Reporter: Justin Edelson
Assigned To: Eugene Kuleshov
Attachments: m2eclipse.patch
It appears that the current trunk (targetting 0.0.10) fixes most of the bugs related to using the user settings.xml file when running a maven 2 build. However, it still does not use settings.xml when building the classpath entries. I first encountered this problem when the parent pom was contained in a repository added by my settings.xml.
In any case, the solution seems to be to create a MavenEmbedRequest object with the user settings file and pass it to embedder.start().
Patch attached.
This did make me wonder if the plugin should lose the local repository preference and instead have a user settings file preference. Thoughts?
--
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: (MNGECLIPSE-174) settings.xml ignored when
building classpath
Posted by "Justin Edelson (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNGECLIPSE-174?page=comments#action_77180 ]
Justin Edelson commented on MNGECLIPSE-174:
-------------------------------------------
So with Embedder 2.1, DefaultMavenEmbedRequest will automatically use the default user settings and global settings files? But that change hasn't been made already? Is there a JIRA for that change I can watch?
> settings.xml ignored when building classpath
> --------------------------------------------
>
> Key: MNGECLIPSE-174
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-174
> Project: Maven 2.x Extension for Eclipse
> Issue Type: Bug
> Affects Versions: 0.0.10
> Reporter: Justin Edelson
> Assigned To: Eugene Kuleshov
> Attachments: m2eclipse.patch, plugintest.zip, settings.xml
>
>
> It appears that the current trunk (targetting 0.0.10) fixes most of the bugs related to using the user settings.xml file when running a maven 2 build. However, it still does not use settings.xml when building the classpath entries. I first encountered this problem when the parent pom was contained in a repository added by my settings.xml.
> In any case, the solution seems to be to create a MavenEmbedRequest object with the user settings file and pass it to embedder.start().
> Patch attached.
> This did make me wonder if the plugin should lose the local repository preference and instead have a user settings file preference. Thoughts?
--
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: (MNGECLIPSE-174) settings.xml ignored when building
classpath
Posted by "Eugene Kuleshov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNGECLIPSE-174?page=all ]
Eugene Kuleshov closed MNGECLIPSE-174.
--------------------------------------
Resolution: Fixed
Justin, thanks for the test case. Closing this issue as duplicate of MNGECLIPSE-29, which should fix your issue when resolved. Though we are still waiting for new Embedder.
> settings.xml ignored when building classpath
> --------------------------------------------
>
> Key: MNGECLIPSE-174
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-174
> Project: Maven 2.x Extension for Eclipse
> Issue Type: Bug
> Affects Versions: 0.0.10
> Reporter: Justin Edelson
> Attachments: m2eclipse.patch, plugintest.zip, settings.xml
>
>
> It appears that the current trunk (targetting 0.0.10) fixes most of the bugs related to using the user settings.xml file when running a maven 2 build. However, it still does not use settings.xml when building the classpath entries. I first encountered this problem when the parent pom was contained in a repository added by my settings.xml.
> In any case, the solution seems to be to create a MavenEmbedRequest object with the user settings file and pass it to embedder.start().
> Patch attached.
> This did make me wonder if the plugin should lose the local repository preference and instead have a user settings file preference. Thoughts?
--
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: (MNGECLIPSE-174) settings.xml ignored when building
classpath
Posted by "Justin Edelson (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNGECLIPSE-174?page=all ]
Justin Edelson updated MNGECLIPSE-174:
--------------------------------------
Attachment: settings.xml
plugintest.zip
Basic steps to reproduce:
install this settings.xml file
ensure there's nothing in org/apache/maven/maven directory in your local repository
add the zipped project to your Eclipse workspace
Observe this error in the M2 console:
8/3/06 1:07:14 PM EDT: Project build error Cannot find parent: org.apache.maven:maven for project: test:plugintest:jar:2.1-SNAPSHOT
> settings.xml ignored when building classpath
> --------------------------------------------
>
> Key: MNGECLIPSE-174
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-174
> Project: Maven 2.x Extension for Eclipse
> Issue Type: Bug
> Affects Versions: 0.0.10
> Reporter: Justin Edelson
> Assigned To: Eugene Kuleshov
> Attachments: m2eclipse.patch, plugintest.zip, settings.xml
>
>
> It appears that the current trunk (targetting 0.0.10) fixes most of the bugs related to using the user settings.xml file when running a maven 2 build. However, it still does not use settings.xml when building the classpath entries. I first encountered this problem when the parent pom was contained in a repository added by my settings.xml.
> In any case, the solution seems to be to create a MavenEmbedRequest object with the user settings file and pass it to embedder.start().
> Patch attached.
> This did make me wonder if the plugin should lose the local repository preference and instead have a user settings file preference. Thoughts?
--
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: (MNGECLIPSE-174) settings.xml ignored when
building classpath
Posted by "Justin Edelson (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNGECLIPSE-174?page=comments#action_77173 ]
Justin Edelson commented on MNGECLIPSE-174:
-------------------------------------------
does that mean this is fixed in trunk (using the snapshot of the embedder)?
> settings.xml ignored when building classpath
> --------------------------------------------
>
> Key: MNGECLIPSE-174
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-174
> Project: Maven 2.x Extension for Eclipse
> Issue Type: Bug
> Affects Versions: 0.0.10
> Reporter: Justin Edelson
> Assigned To: Eugene Kuleshov
> Attachments: m2eclipse.patch, plugintest.zip, settings.xml
>
>
> It appears that the current trunk (targetting 0.0.10) fixes most of the bugs related to using the user settings.xml file when running a maven 2 build. However, it still does not use settings.xml when building the classpath entries. I first encountered this problem when the parent pom was contained in a repository added by my settings.xml.
> In any case, the solution seems to be to create a MavenEmbedRequest object with the user settings file and pass it to embedder.start().
> Patch attached.
> This did make me wonder if the plugin should lose the local repository preference and instead have a user settings file preference. Thoughts?
--
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: (MNGECLIPSE-174) settings.xml ignored when
building classpath
Posted by "Eugene Kuleshov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNGECLIPSE-174?page=comments#action_71546 ]
Eugene Kuleshov commented on MNGECLIPSE-174:
--------------------------------------------
Please attach Eclipse Eclipse project, settings.xml and exact steps to reproduce this issue. Thanks.
> settings.xml ignored when building classpath
> --------------------------------------------
>
> Key: MNGECLIPSE-174
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-174
> Project: Maven 2.x Extension for Eclipse
> Issue Type: Bug
> Affects Versions: 0.0.10
> Reporter: Justin Edelson
> Assigned To: Eugene Kuleshov
> Attachments: m2eclipse.patch
>
>
> It appears that the current trunk (targetting 0.0.10) fixes most of the bugs related to using the user settings.xml file when running a maven 2 build. However, it still does not use settings.xml when building the classpath entries. I first encountered this problem when the parent pom was contained in a repository added by my settings.xml.
> In any case, the solution seems to be to create a MavenEmbedRequest object with the user settings file and pass it to embedder.start().
> Patch attached.
> This did make me wonder if the plugin should lose the local repository preference and instead have a user settings file preference. Thoughts?
--
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] Reopened: (MNGECLIPSE-174) settings.xml ignored when
building classpath
Posted by "Eugene Kuleshov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNGECLIPSE-174?page=all ]
Eugene Kuleshov reopened MNGECLIPSE-174:
----------------------------------------
Assignee: Eugene Kuleshov
> settings.xml ignored when building classpath
> --------------------------------------------
>
> Key: MNGECLIPSE-174
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-174
> Project: Maven 2.x Extension for Eclipse
> Issue Type: Bug
> Affects Versions: 0.0.10
> Reporter: Justin Edelson
> Assigned To: Eugene Kuleshov
> Attachments: m2eclipse.patch, plugintest.zip, settings.xml
>
>
> It appears that the current trunk (targetting 0.0.10) fixes most of the bugs related to using the user settings.xml file when running a maven 2 build. However, it still does not use settings.xml when building the classpath entries. I first encountered this problem when the parent pom was contained in a repository added by my settings.xml.
> In any case, the solution seems to be to create a MavenEmbedRequest object with the user settings file and pass it to embedder.start().
> Patch attached.
> This did make me wonder if the plugin should lose the local repository preference and instead have a user settings file preference. Thoughts?
--
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: (MNGECLIPSE-174) settings.xml ignored when building
classpath
Posted by "Eugene Kuleshov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNGECLIPSE-174?page=all ]
Eugene Kuleshov updated MNGECLIPSE-174:
---------------------------------------
Assignee: (was: Eugene Kuleshov)
> settings.xml ignored when building classpath
> --------------------------------------------
>
> Key: MNGECLIPSE-174
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-174
> Project: Maven 2.x Extension for Eclipse
> Issue Type: Bug
> Affects Versions: 0.0.10
> Reporter: Justin Edelson
> Attachments: m2eclipse.patch, plugintest.zip, settings.xml
>
>
> It appears that the current trunk (targetting 0.0.10) fixes most of the bugs related to using the user settings.xml file when running a maven 2 build. However, it still does not use settings.xml when building the classpath entries. I first encountered this problem when the parent pom was contained in a repository added by my settings.xml.
> In any case, the solution seems to be to create a MavenEmbedRequest object with the user settings file and pass it to embedder.start().
> Patch attached.
> This did make me wonder if the plugin should lose the local repository preference and instead have a user settings file preference. Thoughts?
--
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: (MNGECLIPSE-174) settings.xml ignored when building
classpath
Posted by "Eugene Kuleshov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNGECLIPSE-174?page=all ]
Eugene Kuleshov closed MNGECLIPSE-174.
--------------------------------------
Resolution: Duplicate
Ops. Wrong resolution.
> settings.xml ignored when building classpath
> --------------------------------------------
>
> Key: MNGECLIPSE-174
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-174
> Project: Maven 2.x Extension for Eclipse
> Issue Type: Bug
> Affects Versions: 0.0.10
> Reporter: Justin Edelson
> Assigned To: Eugene Kuleshov
> Attachments: m2eclipse.patch, plugintest.zip, settings.xml
>
>
> It appears that the current trunk (targetting 0.0.10) fixes most of the bugs related to using the user settings.xml file when running a maven 2 build. However, it still does not use settings.xml when building the classpath entries. I first encountered this problem when the parent pom was contained in a repository added by my settings.xml.
> In any case, the solution seems to be to create a MavenEmbedRequest object with the user settings file and pass it to embedder.start().
> Patch attached.
> This did make me wonder if the plugin should lose the local repository preference and instead have a user settings file preference. Thoughts?
--
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: (MNGECLIPSE-174) settings.xml ignored when
building classpath
Posted by "Eugene Kuleshov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNGECLIPSE-174?page=comments#action_77176 ]
Eugene Kuleshov commented on MNGECLIPSE-174:
--------------------------------------------
No, it is not fixed in the trunk, because there is still no Embedder. Embedder code in its own trunk does not have these fixes either.
> settings.xml ignored when building classpath
> --------------------------------------------
>
> Key: MNGECLIPSE-174
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-174
> Project: Maven 2.x Extension for Eclipse
> Issue Type: Bug
> Affects Versions: 0.0.10
> Reporter: Justin Edelson
> Assigned To: Eugene Kuleshov
> Attachments: m2eclipse.patch, plugintest.zip, settings.xml
>
>
> It appears that the current trunk (targetting 0.0.10) fixes most of the bugs related to using the user settings.xml file when running a maven 2 build. However, it still does not use settings.xml when building the classpath entries. I first encountered this problem when the parent pom was contained in a repository added by my settings.xml.
> In any case, the solution seems to be to create a MavenEmbedRequest object with the user settings file and pass it to embedder.start().
> Patch attached.
> This did make me wonder if the plugin should lose the local repository preference and instead have a user settings file preference. Thoughts?
--
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