[jira] Commented: (MNGECLIPSE-174) settings.xml ignored when building classpath
[ 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
[ 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
[jira] Commented: (MNGECLIPSE-174) settings.xml ignored when building classpath
[ 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
