João Antonio Ferreira created MASSEMBLY-967:
-----------------------------------------------
Summary: maven-assembly-plugin doesn't add target/class artifacts
in generated jarfat but META-INF/MANIFEST.MF seems to be correct
Key: MASSEMBLY-967
URL: https://issues.apache.org/jira/browse/MASSEMBLY-967
Project: Maven Assembly Plugin
Issue Type: Bug
Components: maven-archiver
Affects Versions: 3.4.0, 3.3.0
Environment: MacOS Catalina and others Linux flavours
Reporter: João Antonio Ferreira
See below the relevant build segment extracted from pom.xml:
{code:xml}
<plugin>
<artifactId>maven-assembly-plugin</artifactId>
<version>3.4.0</version>
<configuration>
<archive>
<manifest>
<addClasspath>true</addClasspath>
<mainClass>my_package.Main</mainClass>
</manifest>
</archive>
<descriptorRefs>
<descriptorRef>jar-with-dependencies</descriptorRef>
</descriptorRefs>
</configuration>
</plugin>
{code}
this command below does not show anything
{code:bash}
jar -tvf target/my-fat-jar.jar | grep Main.class
{code}
My main class and other project artifacts are not added in fatjar by
maven-assembly-plugin
*Edit:* I tested it with other versions of the plugin (3.2.0, 2.2, ...) and it
didn't work. However if I change the version from 3.4.0 to *2.2-beta-5 the
fatjar is generated correctly*. Version 2.2-beta-5 is from 12/06/2009, ie very
old. I would like to use a newer version. Any idea ?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
