Many “META-INF/ already added, skipping” warnings when building assembly

maven-2maven-assembly-plugin

when building a jar-with-dependencies with the assembly plugin, I get many, many messages like this:

META-INF/ already added, skipping

It seems to mee, that maven is warning me, that I already have a META-INF in my to-be-created jar, and therefore the META-INF of the to-be-included dependant jar file is not included in my to-be-created jar. Well, this is exactly what I want, and I want to ged rid of those messages. Is there a way to achieve this?

Regards,
Martin.

Best Answer

The info messages are coming from the Plexus Archiver. There is an open bug report on this issue:

http://jira.codehaus.org/browse/PLXCOMP-129

Related Solutions

R – maven javaee application client plugin

You should only need to define the project with jar packaging (and as it is the default you don't need to declare it). If you define the application-client.xml in the src/main/resources/META-INF folder it will be included in the META-INF folder of the final jar.

To define additional information you need to configure the jar plugin as below.

<project>
...
  <build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-jar-plugin</artifactId>
        <version>2.2</version>
        <configuration>
          <archive>
            <manifest>
              <mainClass>com.mycompany.app.App</mainClass>
              <addClasspath>true</addClasspath>
            </manifest>
            <manifestFile>src/main/resources/META-INF/MANIFEST.MF</manifestFile>
          </archive>
        </configuration>
      </plugin>
    </plugins>
  </build>
  ...
</project>

Check out the guide to working with manifests for full details

Spring – Idea to avoid that spring.handlers/spring.schemas get overwritten when merging multiple spring dependencies in a single jar

I managed to get rid of the bug using the shader plugin instead of the (buggy) assembler plugin:

        <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-shade-plugin</artifactId>
            <executions>
                <execution>
                    <phase>package</phase>
                    <goals>
                        <goal>shade</goal>
                    </goals>
                    <configuration>
                        <transformers>
                            <transformer implementation="org.apache.maven.plugins.shade.resource.ManifestResourceTransformer">
                                <mainClass>at.seresunit.lecturemanager_connector.App</mainClass>
                            </transformer>
                            <transformer implementation="org.apache.maven.plugins.shade.resource.AppendingTransformer">
                                <resource>META-INF/spring.handlers</resource>
                            </transformer>
                            <transformer implementation="org.apache.maven.plugins.shade.resource.AppendingTransformer">
                                <resource>META-INF/spring.schemas</resource>
                            </transformer>
                        </transformers>
                    </configuration>
                </execution>
            </executions>
        </plugin>

I think I found the solution on the springsource forums.. it has been quite some time since I looked it up.. can't really remember the author. Kudos to him anyways :p

cheers

Best Answer

Related Solutions

R – maven javaee application client plugin

Spring – Idea to avoid that spring.handlers/spring.schemas get overwritten when merging multiple spring dependencies in a single jar

Related Topic