Community
Participate
Working Groups
maven 3.5.0 CLI no longer looks for global toolchains configuration in ${maven.home}/conf, instead looking in ${maven.conf} https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commitdiff;h=be5caccaff3d00ffca4b3cefe9665b6106bc44bf It appears m2e must set property maven.conf prior to invoking MavenCli This appears to apply to the following three classes: m2e-core/org.eclipse.m2e.core/src/org/eclipse/m2e/core/internal/launch/MavenExternalRuntime.java m2e-core/org.eclipse.m2e.core/src/org/eclipse/m2e/core/internal/launch/MavenEmbeddedRuntime.java m2e-core/org.eclipse.m2e.core/src/org/eclipse/m2e/core/internal/launch/MavenWorkspaceRuntime.java Further, the comments in MavenWorkspaceRuntime that appear to show contents of m2.conf no longer match the contents of the latest m2.conf, specifically as it relates to the newly introduced maven.conf property https://git-wip-us.apache.org/repos/asf?p=maven.git;a=blob_plain;f=apache-maven/src/bin/m2.conf === main is org.apache.maven.cli.MavenCli from plexus.core set maven.conf default ${maven.home}/conf [plexus.core] load ${maven.conf}/logging optionally ${maven.home}/lib/ext/*.jar load ${maven.home}/lib/*.jar ===
I've upgraded to Eclipse Photon, external Maven 3.5.4 and verified the global toolchains.xml file is not located. A fix is to add -Dmaven.conf=<path to maven>/conf when invoking the m2e external maven runtime. This fix is not scalable, as we have over 250 developers that would be affected. If there is a way to set maven.conf in a way that could be bundled with Eclipse, I would welcome that as an interim solution. I've looked at <maven>/conf/m2.conf which appears to set maven.conf, but the property is apparently used only for creating the classpaths; the property is not currently added to System properties
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
Eclipse m2e is moving away from this bugs.eclipse.org issue tracker to https://github.com/eclipse-m2e/m2e-core/issues/ instead. If this issue is relevant to you, your action is required. 0. Verify this issue is still happening with latest Eclipse Platform and m2e release if issue has disappeared, please change status of this issue to "CLOSED WORKFORME" with some details about your testing environment and how you did verify the issue; and you're done if issue is still present when latest release: * Create a new issue at https://github.com/eclipse-m2e/m2e-core/issues/ ** Use as title in GitHub the title of this Bugzilla ticket (may include the bug number or not, at your own convenience) ** In the GitHub description, start with a link to this bugzilla ticket ** Optionally add new content to the description if it can helps towards resolution ** Submit GitHub issue * Update bugzilla ticket ** Add to "See also" property (up right column) the link to the newly created GitHub issue ** Add a comment "Migrated to <link-to-newly-created-GitHub-issue>" ** Set status as CLOSED MOVED ** Submit All issues that remain open will be automatically closed next week or so. Then the m2e component for m2e will be made read-only.
Moved to https://github.com/eclipse-m2e/m2e-core/issues/
