OK, that worked! Thanks so much, Mike.

On 6/29/06, Mike Perham <[EMAIL PROTECTED]> wrote:

http://svn.apache.org/repos/asf/maven/shared/trunk/maven-archiver/

See ManifestConfiguration.java.  So I think it would be:

<configuration>
  <archive>
    <manifest>
      <addClasspath>true</addClasspath>

<addDefaultImplementationEntries>true</addDefaultImplementationEntries>
    </manifest>
  </archive>
</configuration>

> -----Original Message-----
> From: news [mailto:[EMAIL PROTECTED] On Behalf Of Mark Reynolds
> Sent: Thursday, June 29, 2006 7:48 PM
> To: users@maven.apache.org
> Subject: Re: [m2] problem with manifest entries with new war plugin
>
> Thanks, Mike. I did spend some time rereading all the associated bugs
> and looking at some source code (though I don't know where in
> the source
> tree the archiver has moved to), but I didn't figure out the
> switch to
> turn on automatic entries or how to specify my own values.
>
> -- Mark R
>
> Mike Perham wrote:
> > Mark, there is a flag which you can specify to enable the
> old manifest
> > default values.  I'm not positive on the exact syntax so
> you'll need to
> > do some legwork to find this.  I think the plan was to
> document all this
> > in the jar plugin but I guess the war plugin snuck out first without
> > full documentation.
> >
> > This is all part of the recent changes to the shared maven-archiver
> > project and should be documented in MJAR-38 and MJAR-39 I believe.
> >
> >> -----Original Message-----
> >> From: news [mailto:[EMAIL PROTECTED] On Behalf Of Mark Reynolds
> >> Sent: Wednesday, June 28, 2006 3:45 PM
> >> To: users@maven.apache.org
> >> Subject: [m2] problem with manifest entries with new war plugin
> >>
> >> I see the war plugin was just updated to 2.0.1.
> >>
> >> It no longer automatically produces certain entries in the
> >> manifest that
> >> it did previously:
> >>
> >>      Extension-Name:
> >>      Specification-Title:
> >>      Specification-Vendor:
> >>      Implementation-Vendor:
> >>      Implementation-Title:
> >>      Implementation-Version:
> >>
> >> I read MWAR-34 and MWAR-35 but it is not clear to me what the
> >> intended
> >> behavior is as a result of fixing those bugs. Is it no longer
> >> supposed
> >> to add any of these by default?
> >>
> >> I tried to add these manually like this, for example:
> >>
> >>      <plugin>
> >>        <artifactId>maven-war-plugin</artifactId>
> >>        <configuration>
> >>           <archive>
> >>             <manifestEntries>
> >>               <Implementation-Version>abc</Implementation-Version>
> >>             </manifestEntries>
> >>           </archive>
> >>         </configuration>
> >>       </plugin>
> >>
> >> Previously adding  manual entries to a WAR did not seem to
> >> work (worked
> >> fine for JARs). Now it produces an exception no matter what
> >> entry I try
> >> to add, for example:
> >>
> >>      org.codehaus.plexus.archiver.jar.ManifestException:
> >>      The attribute "Implementation-Version" may not occur more than
> >>      once in the same section
> >>      at org.codehaus.plexus.archiver.jar.Manifest$Section.
> >>      addAttributeAndCheck(Manifest.java:727)
> >>
> >> I can write up a bug, if appropriate, but I'm not clear on
> what the
> >> intended behavior is now.
> >>
> >> -- Mark R
> >>
> >>
> >>
> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> For additional commands, e-mail: [EMAIL PROTECTED]
> >>
> >>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Reply via email to