Unified source directory structure that is analogous to the repository
 itself. This way locations of intermediary artifacts of a build would be
 in a known location. This would also help with developer setup i.e. getting
 new developers up and running. They could run a maven command and have all
 their source trees set up in the same way as their colleagues.

 here's what I do currently in the netbeans part of the mavenide project to

    // checks for duplicate projects definitions in the build. Ideally this type of duplicate checking should be
    // part of getting the reactor projects in 6). The duplicate checking is conflated with getProjectMap(projects).
    //
    // 9) Execute AbstractLifecycleParticipant.afterProjectsRead(session)
    //

    <version>4.0.0-beta-1-SNAPSHOT</version>
  </parent>

  <artifactId>maven-builder-support</artifactId>

  <name>Maven Builder Support</name>
  <description>Support for descriptor builders (model, setting, toolchains)</description>

  <dependencies>
    <dependency>
      <groupId>org.junit.jupiter</groupId>
      <artifactId>junit-jupiter-api</artifactId>
      <scope>test</scope>
    </dependency>

        }

        /**
         * Wrap the specified root object, allowing the specified list of expression
         * prefixes and setting whether the {@link PrefixedValueSourceWrapper} allows
         * unprefixed expressions.
         * @param possiblePrefixes The possible prefixes.
         * @param root The root of the graph.

            if (session.getProjectBuildingRequest().getBuildStartTime() != null) {
                long buildStartTime =
                        session.getProjectBuildingRequest().getBuildStartTime().getTime();
                if (artifactLastModified > buildStartTime) {
                    return true;
                }
            }

            for (Path outputFile : (Iterable<Path>) outputFiles::iterator) {

** Accessibility of offline status

  Offline status should be indicated in the MavenSettings instance, since it
  can conceivably be set from either the settings.xml or the command-line.

  In the event the '-o' switch is the impetus for setting offline mode, this
  should result in modification of the active profile in the MavenSettings
  instance, just as definition of the active profile from the command-line

KIND, either express or implied.  See the License for the
specific language governing permissions and limitations
under the License.
-->

<settings>
  <localRepository>${user.home}/.m2/repository</localRepository>

    /**
     * Information about modules in the main output. This field is initially null and is set to a non-null
     * value when the output directories have been set, or when it is too late for setting them.
     */
    private PathModularization outputModules;

    /**
     * Creates an initially empty result. Callers should add path elements by calls

                }
            }
        } catch (IOException e) {
            throw new UncheckedIOException(e);
        }
    }

    @Override
    public Optional<String> getString(URI relativeSource, Charset charset) {
        requireNonNull(charset, "charset is null");
        Optional<byte[]> data = getBytes(relativeSource);
        return data.map(bytes -> new String(bytes, charset));
    }