Community
Participate
Working Groups
To maximize how cache is reused in ProjectRegistryManager, it would be good to make that ProjectRegistryManager.getMavenProject(facade, ...) looks for descendents of the project (if they share the same ResolverConfiguration) and reuse the parent MavenProject from the descendant. For example, if we have only a "child" project in the cache, and this project has a "parent" and both share equivalent ResolverConfiguration (profiles, settings and so on); then asking for "parent" with getMavenProject(...) should detect that there is "child" and return child.getParent() as MavenProject instead of returning null and populating the cache for a value we already have.
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/
