[MASSEMBLY-1] assembly jar-with-dependencies does not utilize or provide for manifest configuration

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed

Environment

$ uname -a
Darwin xxx 8.2.0 Darwin Kernel Version 8.2.0: Fri Jun 24 17:46:54 PDT 2005; root:xnu-792.2.4.obj~3/RELEASE_PPC Power Macintosh powerpc

$ java -version
java version "1.5.0_05"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_05-72)
Java HotSpot(TM) Client VM (build 1.5.0_05-44, mixed mode, sharing)

$ mvn -version
Maven version: 2.0

maven-assembly-plugin version 2.0

• Assignee: Brett Porter
• Reporter: Michael Heuer
• Created: 31/Oct/05 10:31
• Updated: 01/Aug/10 13:40
• Resolved: 07/Apr/06 20:59

Description

Date: Mon, 31 Oct 2005 17:04:21 +1100
From: Brett Porter <[e-mail]>
To: Maven Users List <[e-mail]>
Subject: Re: [m2] manifest for assembly jar-with-dependencies

Yes, that's an issue with the assembly plugin. If there is no
corresponding JIRA issue, please file one.

• Brett

On 10/28/05, Michael Heuer <[e-mail]> wrote:
> Hello,
>
> I followed the guide at
>
> > http://maven.apache.org/guides/mini/guide-manifest.html
>
> to add entries to my MANIFEST.MF, and that works fine with
>
> $ mvn package
>
> However, it seems that the assembly plugin does not reuse the
> configuration information when building the jar-with-dependencies jar, so
> I'm left with a default manifest in that jar.
>
> michael

Issue Links

• relates to: MASSEMBLY-74 MANIFEST.MF is not used when specified in configuration.