*   <li><strong>Root Attribute</strong>: Adds {@code root="true"} attribute to root project</li>
 *   <li><strong>Parent Element Trimming</strong>:
 *     <ul>
 *       <li>Removes parent {@code <groupId>} when child has no explicit groupId</li>
 *       <li>Removes parent {@code <version>} when child has no explicit version</li>
 *       <li>Removes parent {@code <artifactId>} when it can be inferred from relativePath</li>
 *     </ul>

     *       <ul>
     *         <li>For {@link ProjectScope#MAIN}: typically {@code /path/to/project/target/classes}</li>
     *         <li>For {@link ProjectScope#TEST}: typically {@code /path/to/project/target/test-classes}</li>
     *       </ul></li>
     *   <li>If the configured target path is empty:
     *       <ul><li>Return the output directory as-is</li></ul></li>

	const readLock = true
	success := make([]int, len(li.paths))
	for i, path := range li.paths {
		if !li.ns.lock(ctx, li.volume, path, lockSource, li.opsID, readLock, timeout.Timeout()) {
			timeout.LogFailure()
			for si, sint := range success {
				if sint == 1 {
					li.ns.unlock(li.volume, li.paths[si], readLock)
				}
			}
			if err := ctx.Err(); err == context.Canceled {
				return LockContext{}, err
			}

 *
 * <p>This service allows implementations to:</p>
 * <ul>
 *   <li>Pool identical objects to reduce memory footprint</li>
 *   <li>Intern objects for faster equality comparisons</li>
 *   <li>Apply custom optimization strategies</li>
 *   <li>Transform or modify objects during building</li>
 * </ul>
 *
 * <p>Implementations are discovered via the Java ServiceLoader mechanism and should

 * <ul>
 *   <li>Access to the current {@link org.apache.maven.api.Project}</li>
 *   <li>Access to the {@link org.apache.maven.api.LocalRepository} and {@link org.apache.maven.api.RemoteRepository} configurations</li>
 *   <li>Access to Maven services through {@link org.apache.maven.api.Session#getService(Class)}</li>
 *   <li>Build configuration and settings</li>
 * </ul>
 *
 * <h3>Dependency management</h3>
 *

/**
 * Specific problems during resolution that we want to account for:
 * <ul>
 *   <li>missing metadata</li>
 *   <li>version range violations</li>
 *   <li>version circular dependencies</li>
 *   <li>missing artifacts</li>
 *   <li>network/transfer errors</li>
 *   <li>file system errors: permissions</li>
 * </ul>
 *
 * TODO carlos: all these possible has*Exceptions and get*Exceptions methods make the clients too

 *
 * <p>To add new upgrade strategies:</p>
 * <ol>
 *   <li>Implement {@link org.apache.maven.cling.invoker.mvnup.goals.UpgradeStrategy}</li>
 *   <li>Optionally extend {@link org.apache.maven.cling.invoker.mvnup.goals.AbstractUpgradeStrategy}</li>
 *   <li>Annotate with {@code @Named} and {@code @Singleton}</li>
 *   <li>Use {@code @Priority} to control execution order</li>
 * </ol>
 *
 * @since 4.0.0
 */

	    Parameter and result names are not required to match.</li>

	<li>Two interface types are identical if they define the same type set.
	</li>

	<li>Two map types are identical if they have identical key and element types.</li>

	<li>Two channel types are identical if they have identical element types and
	    the same direction.</li>

	<li>Two <a href="#Instantiations">instantiated</a> types are identical if

 *
 * <h2>Standard Packaging Types</h2>
 * <ul>
 *     <li>{@code jar}: Packages the project as a Java Archive (JAR) file.</li>
 *     <li>{@code war}: Packages the project as a Web Application Archive (WAR) file.</li>
 *     <li>{@code pom}: Indicates that the project does not produce a deployable artifact but is used for dependency management or as an aggregator.</li>
 *     <li>{@code maven-plugin}: Packages the project as a Maven plugin.</li>
 * </ul>

</p>

<ul>

<li>
<code>FP</code>: Frame pointer: arguments and locals.
</li>

<li>
<code>PC</code>: Program counter:
jumps and branches.
</li>

<li>
<code>SB</code>: Static base pointer: global symbols.
</li>

<li>
<code>SP</code>: Stack pointer: the highest address within the local stack frame.
</li>

</ul>

<p>