of the ASM project at <a href="http://asm.ow2.org/">http://asm.ow2.org/</a>.</p>

<p>A subset of ASM is re-packaged within the source and binary of the plug-in (org.eclipse.sisu.space.asm.*)
to avoid version collisions with other usage and is also available from the plug-in's github repository.</p>

<p>Your use of the ASM code is subject to the terms and conditions of the ASM License

```
[MNG-XXX] - Subject of the JIRA Ticket
 Optional supplemental description.
```
+ Make sure you have added the necessary tests (JUnit/[Core IT tests][core-it]) for your changes.
+ Run all the tests with `mvn -Prun-its verify` to assure nothing else was accidentally broken.
+ Submit a pull request to the repository in the Apache organization.

/**
 * A container for data that is specific to a session.
 * All components may use this storage to associate arbitrary data with a session.
 * <p>
 * Unlike a cache, this session data is not subject to purging. For this same reason, session data should also not be
 * abused as a cache (i.e. for storing values that can be re-calculated) to avoid memory exhaustion.
 * <p>

## under the License.
##


Apache Maven includes a number of components and libraries with separate
copyright notices and license terms. Your use of those components are
subject to the terms and conditions of the following licenses:
##
#set ( $apacheMavenGroupIds = [ "org.apache.maven", "org.apache.maven.wagon", "org.apache.maven.resolver",
                                "org.apache.maven.shared" ] )

  <artifactId>child</artifactId>
  <version>1.0-SNAPSHOT</version>

  <name>Maven Integration Test :: MNG-4034</name>
  <description>
    Verify that dependencies defined in profiles are subject to the dependency management of the parent.
  </description>

  <profiles>
    <profile>
      <id>maven-core-it</id>
      <activation>
        <activeByDefault>true</activeByDefault>
      </activation>

       require a JIRA issue. Your pull request should address just this issue, without
       pulling in other changes.
 - [ ] Each commit in the pull request should have a meaningful subject line and body.
 - [ ] Format the pull request title like `[MNG-XXX] SUMMARY`,
       where you replace `MNG-XXX` and `SUMMARY` with the appropriate JIRA issue.

    }

    public Future<ProjectSegment> submit(Callable<ProjectSegment> task) {
        FutureTask<ProjectSegment> projectBuildFutureTask = new FutureTask<>(task);
        projectBuildFutureTasks.add(projectBuildFutureTask);
        if (finishImmediately) {
            projectBuildFutureTask.run();
        }
        return projectBuildFutureTask;
    }

    public Future<ProjectSegment> submit(Runnable task, ProjectSegment result) {

  <artifactId>parent</artifactId>
  <version>1.0-SNAPSHOT</version>
  <packaging>pom</packaging>

  <name>Maven Integration Test :: MNG-4034</name>
  <description>
    Verify that dependencies defined in profiles are subject to the dependency management of the parent.
  </description>

  <modules>
    <module>sub</module>
  </modules>

  <dependencyManagement>
    <dependencies>
      <dependency>

 without limitation  the rights to  use, copy, modify,  merge, publish,
 distribute,  sublicense, and/or sell  copies of  the Software,  and to
 permit persons to whom the Software  is furnished to do so, subject to
 the following conditions:

 The  above  copyright  notice  and  this permission  notice  shall  be
 included in all copies or substantial portions of the Software.

            Callable<ProjectSegment> cb = createBuildCallable(
                    rootSession, projectSegment, reactorContext, taskSegment, muxer, duplicateArtifactIds);
            service.submit(cb);
        }

        // for each finished project
        for (int i = 0; i < analyzer.getNumberOfBuilds(); i++) {
            try {
                ProjectSegment projectBuild = service.take().get();