</la:link></li>
								</c:when>
							</c:choose>
							<li class="nav-item"><la:link href="/help"
									styleClass="nav-link help-link">
									<i class="fa fa-fw fa-question-circle" aria-hidden="true"></i>
									<la:message key="labels.index_help" />
								</la:link></li>
						</ul>
					</div>
				</div>
			</nav>
		</header>
		<div id="searchOptions" class="collapse">

										</la:link></li>
								</c:when>
							</c:choose>
							<li class="nav-item"><la:link href="/help"
									styleClass="nav-link help-link">
									<em class="fa fa-fw fa-question-circle">
									<la:message key="labels.index_help" />
								</la:link></li>
						</ul>
					</div>
				</div>
			</nav>
		</header>
		<div id="searchOptions" class="collapse">

                                + "request plugins be made thread-safe.",
                        "If reporting an issue, report it against the plugin in question, not against Apache Maven.")) {
                    logger.warn(s);
                }
                if (logger.isDebugEnabled()) {

the execution block we need to account for creating the right configuration element which includes only those configuration elements for a particular goal that that particular goal understands. We need to walk through the parameters of the Mojo in question and only take the configuration options that apply....

        // Setup minimal valid header
        src[0] = 0x00;
        src[1] = 0x01; // Transaction ID
        src[2] = 0x00; // Flags
        src[3] = 0x00; // Flags
        src[4] = 0x00;
        src[5] = 0x01; // Question count

        // Act
        int result = nodeStatusRequest.readWireFormat(src, 0);

        // Assert
        assertTrue(result >= NameServicePacket.HEADER_LENGTH);
    }

    @Test

                        /* JetDirect printer can respond to regular broadcast query
                         * with node status so we need to check to make sure that
                         * the record type matches the question type and if not,
                         * loop around and try again.
                         */
                        if (response.received && request.questionType == response.recordType) {

											<la:message key="labels.login" />
										</la:link></li>
								</c:when>
							</c:choose>
							<li class="nav-item"><la:link href="/help" styleClass="nav-link help-link">
									<i class="fa fa-fw fa-question-circle" aria-hidden="true"></i>
									<la:message key="labels.index_help" />
								</la:link></li>
						</ul>
					</div>
				</div>
			</nav>
		</header>

		<main id="content" class="container">

  <!-- interactiveMode
   | This will determine whether maven prompts you when it needs input. If set to false,
   | maven will use a sensible default value, perhaps based on some other setting, for
   | the parameter in question.
   |
   | Default: true
  <interactiveMode>true</interactiveMode>
  -->

  <!-- offline
   | Determines whether maven should attempt to connect to the network when executing a build.

  * Not all "remote" repositories will fail. Specifically, if the remote
    repo uses the file:// protocol, and it doesn't refer to a shared
    filesystem, it will continue to be available.

  The question remaining is: Which level of offline mode will we support? It
  seems reasonable to assume that users will be able to tell when localhost is
  not active (in most cases, localhost should be available, even if the rest of

        NameServicePacket.writeInt2(0, src, 6); // answerCount
        NameServicePacket.writeInt2(0, src, 8); // authorityCount
        NameServicePacket.writeInt2(0, src, 10); // additionalCount

        // Mock question name and its readWireFormat
        when(mockQuestionName.readWireFormat(any(byte[].class), anyInt())).thenReturn(10);
        NameServicePacket.writeInt2(NameServicePacket.NB, src, 12 + 10); // questionType