import org.apache.maven.plugin.MojoExecution;
import org.apache.maven.project.MavenProject;

/**
 * <p>
 * Encapsulates parameters of MojoExecutionListener callback methods and is meant to provide API evolution path should
 * it become necessary to introduce new parameters in the existing callbacks in the future.
 * </p>
 * <strong>Note:</strong> This class is part of work in progress and can be changed or removed without notice.
 *

import org.apache.maven.project.MavenProject;

/**
 * <p>
 * Encapsulates parameters of ProjectExecutionListener callback methods and is meant to provide API evolution path
 * should it become necessary to introduce new parameters in the existing callbacks in the future.
 * </p>
 * <strong>Note:</strong> This class is part of work in progress and can be changed or removed without notice.
 *

   *
   * On the other hand, past underutilization could mean that "the server responsible for handling
   * the request has become less ready for future requests", i.e. its caches become stale, and
   * requests become more likely to trigger expensive operations (a more extreme case of this
   * example is when a server has just booted, and it is mostly busy with getting itself up to
   * speed).
   *

    See the License for the specific language governing permissions and
    limitations under the License.
 -->

# Apache Lucene and Solr have separate repositories now!

Solr has become a top-level Apache project and main line 
development for Lucene and Solr is happening in each 
project's git repository now:

- Lucene: <https://gitbox.apache.org/repos/asf/lucene.git>

 */

package jcifs.internal.smb1.trans;

import jcifs.Configuration;

/**
 * Response for SMB1 TRANS_WAIT_NAMED_PIPE transaction.
 *
 * This response is received after waiting for a named pipe to become available
 * for connection when the pipe server was busy.
 */
public class TransWaitNamedPipeResponse extends SmbComTransactionResponse {

    /**
     * Constructs a response for a wait named pipe request.
     *

package jcifs.internal.smb1.trans;

import jcifs.Configuration;

/**
 * SMB1 Transaction Wait Named Pipe request implementation.
 * Implements the TRANS_WAIT_NAMED_PIPE transaction to wait for a named pipe
 * to become available when the pipe server is busy or temporarily unavailable.
 *
 * @author mbechler
 */
public class TransWaitNamedPipe extends SmbComTransaction {

    /**
     * Constructs a wait request for a named pipe.

        // TODO: in a moment Maven stop pushing user properties to system properties (and maybe something more)
        // and allow multiple instances per JVM, this may become a pool? derive key based in invokerRequest?
        MavenContext result = residentContext.computeIfAbsent(
                "resident",
                k -> new MavenContext(invokerRequest, false, (MavenOptions)

We use *Specification* and *Discovery* documents stored in Google Drive, but they present some downsides:

* They are rarely updated after creation and initial review, and then become hard to follow, especially after important decisions are made
* They are not synced with the code to reflect the eventual solution that is committed
* Google Docs is not a "code-oriented" tool, like Markdown can be

authors:
  - family-names: Abadi

* PluginDescriptorBuilder

  s/getMojoConfiguration()/getConfiguration()/g

  That should be all there is to it.

* MojoDescriptor

  Remove set/getMojoConfiguration(..), as it will become obsolete.

* MavenSession

  We may need to enable the context injection here, since this will be
  instantiated per-project. If we always inject the same context parameters,