defined the maven.multiproject.includes property in any of his properties
 files for the current project. if yes. then I'm able to find projects that
 can be offered to be opened together with the current project.
 problems with the current solution are:
 1. information is duplicate. once in POM's dependencies and once in the
 maven.multiproject.includes property.

 * repository system instance(s) use {@link RepositorySystem#shutdown()} method on supplied instance(s).
 * <p>
 * Since Resolver 2.0 this class offers access to various components via public getters, and allows even partial object
 * graph construction.
 * <p>
 * Extend this class {@code createXXX()} methods and override to customize, if needed. The contract of this class makes

    ProjectBuildingRequest getProjectBuildingRequest();

    /**
     * @since 3.1
     * @deprecated Since 3.9 there is no direct Maven2 interop offered at LRM level. See
     * <a href="https://maven.apache.org/resolver/configuration.html">Resolver Configuration</a> page option
     * {@code aether.artifactResolver.simpleLrmInterop} that provides similar semantics. This method should

each major component of the server use its own Log instance. Cause messages to be logged (if the corresponding detail level is enabled) by calling appropriate methods (debug(), info(), warn(), error, and fatal()). For convenience, LogFactory also offers a static method getLog() that combines the typical two-step pattern: Log log = LogFactory.getFactory().getInstance("Foo"); into a single method call: Log log = LogFactory.getLog("Foo"); For example, you might use the following technique to initialize...

org.junit.runner.Description); protected final java.util.List orderItems(java.util.Collection); boolean validateOrderingIsCo(); static void <clinit>(); } org/junit/runner/manipulation/Orderer.class package org.junit.runner.manipulation; public final synchronized class Orderer { private final Ordering ordering; void Orderer(Ordering); public java.util.List order(java.util.Collection) throws InvalidOrderingExcep; public void apply(Object) throws InvalidOrderingExcep; } org/junit/runner/manipulation/Alphanumeric.class...

major component of the server use its own Log instance. Cause messages to be logged (if the corresponding detail level is enabled) by calling appropriate methods (trace(), debug(), info(), warn(), error, and fatal()). For convenience, LogFactory also offers a static method getLog() that combines the typical two-step pattern: Log log = LogFactory.getFactory().getInstance(Foo.class); into a single method call: Log log = LogFactory.getLog(Foo.class); For example, you might use the following technique to...