Tomcat – Maven fails with tomcat-maven-plugin since this morning

maven-2pluginstomcat

Since this morning Maven can not build any project that requires tomcat-maven-plugin. I tried with the minimalistic pom.xml, with just that one dependency, but in all cases I get the following:

[INFO] Error building POM (may not be
this project's POM).

Project ID:
org.codehaus.mojo:tomcat-maven-plugin

Reason: Error getting POM for
'org.codehaus.mojo:tomcat-maven-plugin'
from the repository: Unable to read
local copy of metadata: Cannot read
metadata from
'C:\Users\***\.m2\repository\org\codehaus\mojo\tomcat-maven-plugin\maven-metadata-codehaus releases.xml': end tag name
must match start tag name

from
line 7 (position: TEXT seen
…\n… @9:8)
org.codehaus.mojo:tomcat-maven-plugin:pom:LATEST

for project
org.codehaus.mojo:tomcat-maven-plugin

First, I tried deleting the local data and redownloading, but I just got checksum failures.
I opened maven-metadata-codehaus releases.xml just to see this inside:

301
Moved Permanently

Moved
Permanently

The document has
moved https://nexus.codehaus.org/content/repositories/releases/org/codehaus/mojo/tomcat-maven-plugin/maven-metadata.xml here.

Apache/2.0.52 (Red Hat)
Server at repository.codehaus.org Port
80

I tired changing versions and repositories, but nothing helped. Any ideas anyone?

P.S.
Here's the minimal pom I tried with:

<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>

<groupId>org.codehaus.mojo</groupId>
<artifactId>my-project</artifactId>
<version>1.0</version>

<pluginRepositories>
<pluginRepository>
<id>Codehaus Snapshots</id>
<url>http://snapshots.repository.codehaus.org/</url>
<snapshots>
<enabled>true</enabled>
</snapshots>
<releases>
<enabled>true</enabled>
</releases>
</pluginRepository>
</pluginRepositories>

<build>
<finalName>my-webapp</finalName>
<plugins>

<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>tomcat-maven-plugin</artifactId>
<version>1.0-SNAPSHOT</version>
</plugin>

</plugins>

</build>
</project>

Best Answer

It looks like the redirection is incorrect, Codehaus Snapshots are proxied by: https://nexus.codehaus.org/content/repositories/codehaus-snapshots/.

So declare the following pluginRepository to use SNAPSHOT versions of the tomcat-maven-plugin:

<pluginRepositories>
  <pluginRepository>
    <id>Codehaus Snapshots</id>
    <url>https://nexus.codehaus.org/content/repositories/codehaus-snapshots</url>
  </pluginRepository>
</pluginRepositories>

Related Solutions

Java – How to create an executable JAR with dependencies using Maven

<build>
  <plugins>
    <plugin>
      <artifactId>maven-assembly-plugin</artifactId>
      <configuration>
        <archive>
          <manifest>
            <mainClass>fully.qualified.MainClass</mainClass>
          </manifest>
        </archive>
        <descriptorRefs>
          <descriptorRef>jar-with-dependencies</descriptorRef>
        </descriptorRefs>
      </configuration>
    </plugin>
  </plugins>
</build>

and you run it with

mvn clean compile assembly:single

Compile goal should be added before assembly:single or otherwise the code on your own project is not included.

See more details in comments.

Commonly this goal is tied to a build phase to execute automatically. This ensures the JAR is built when executing mvn install or performing a deployment/release.

<plugin>
  <artifactId>maven-assembly-plugin</artifactId>
  <configuration>
    <archive>
      <manifest>
        <mainClass>fully.qualified.MainClass</mainClass>
      </manifest>
    </archive>
    <descriptorRefs>
      <descriptorRef>jar-with-dependencies</descriptorRef>
    </descriptorRefs>
  </configuration>
  <executions>
    <execution>
      <id>make-assembly</id> <!-- this is used for inheritance merges -->
      <phase>package</phase> <!-- bind to the packaging phase -->
      <goals>
        <goal>single</goal>
      </goals>
    </execution>
  </executions>
</plugin>

Maven include JavaDoc Jar in Assembly

Figured out a solution that seems like it works (at least on the sample app I posted). I modified the inclusion/exclusion entries in the assembly file to wildcard just the type, and the assembly now behaves exactly as expected. The JavaDoc JAR file is not placed in the lib directory, and the JavaDocs are unpacked as intended.

The final assembly file is as follows:

<assembly>
  <id>bin</id>
  <formats>
 <format>jar</format>
  </formats>
  <includeBaseDirectory>false</includeBaseDirectory>

  <dependencySets>
    <dependencySet>
      <excludes>
        <!-- Exclude the Jars that are included in later sections -->
        <exclude>test:module1:*:javadoc</exclude>
      </excludes>
      <outputDirectory>lib</outputDirectory>
      <unpack>false</unpack>
      <useTransitiveDependencies>true</useTransitiveDependencies>
      <useTransitiveFiltering>false</useTransitiveFiltering>
      <useProjectArtifact>false</useProjectArtifact>
    </dependencySet>

    <dependencySet>
      <includes>
        <include>test:module1:*:javadoc</include>
      </includes>
      <outputDirectory>docs</outputDirectory>
      <unpack>true</unpack>
      <useTransitiveDependencies>true</useTransitiveDependencies>
      <useProjectArtifact>false</useProjectArtifact>
      <useStrictFiltering>true</useStrictFiltering>
    </dependencySet>
  </dependencySets>
</assembly>

Update: Some quick testing has revealed that the type of JavaDoc Jar files, at least when referenced from a full build, is 'javadoc'. However, when the package module is run stand-alone, that type is not recognized and cannot be retrieved from the local repository. So, it seems that in order to get both build modes (as part of the overall build, and when built independently), you have to wildcard the type for the JavaDoc Jar files in the assembly.

Moved Permanently

Best Answer

Related Solutions

Java – How to create an executable JAR with dependencies using Maven

Maven include JavaDoc Jar in Assembly

Related Topic

Moved
Permanently