Markus Karg wrote:

I need to add the following information to the MANIFEST.MF file of a JAR:

Name: S1
N1: V1

Name: S2
N2: V2

How can I do that?

I tried it this way but it doesn't work:

<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
<configuration>
<archive>
<index>true</index>
<manifest>
<addClasspath>true</addClasspath>
</manifest>
<manifestEntries>
<section name="S1"><N1>V1</N1></section>
<section name="S2"><N2>V2</N2></section>
</manifestEntries>
</archive>
</configuration>
</plugin>
</plugins>
</build>

What is the correct way to configure the pom.xml that get the above
sections and entries?

Thanks
Markus

begin:vcard
fn:Markus KARG
n:KARG;Markus
org:QUIPSY QUALITY GmbH;Entwicklung / R & D
adr:;;Stuttgarter Strasse
23;Pforzheim;Baden-Wuerttemberg;75179;Bundesrepublik Deutschland
email;internet:karg (AT) quipsy (DOT) de
title:Staatl. gepr. Inf.
tel;work:+49-7231-9189-52
tel;fax:+49-7231-9189-59
note:QUIPSY(R) Entwicklung / R & D
x-mozilla-html:TRUE
url:http://www.quipsy.de
version:2.1
end:vcard

Good day to you, Markus,

Not exactly sure how, but you want to take a look at [1] and [2] ^_^ This
documentation is still under review though, so feel free to post any
comments that you may have so that we can update it ^_^

Thanks,
Franz

[1]
http://people.apache.org/~
[2]
http://people.apache.org/~

Hi!

Franz, are you joking?
Do you see any <sectiontags on the URLs you posted?
Maybe I am blind, but I don't see any, actually.

The text may not mention it, but the JavaDocs show it. You have got to
abstract a little from the example and the docs.

Just make your PM look like this:

<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
<configuration>
<archive>
<index>true</index>
<manifest>
<addClasspath>true</addClasspath>
</manifest>
<manifestSections>
<manifestSection>
<name>S1</name>
<manifestEntries>
<N1>V1</N1>
</manifestEntries>
</manifestSection>
</manifestSections>
</archive>
</configuration>
</plugin>

This will result in a manifest like this:

Manifest-Version: 1.0
Archiver-Version: Plexus Archiver
Created-By: Apache Maven
Built-By: hb
Build-Jdk: 1.5.0_06
Class-Path: commons-lang-2.1.jar

Name: S1
N1: V1

Enjoy!

Markus KARG-2 wrote:

Hendrik and Franz,

thanks a lot for your kind help! I indeed will try out tomorrow.

But please one more question: How is the relationship between javadocs
and pom structure? I did not yet understand how I can guess from the
javadocs to the pom structure actually.

Thanks a lot!
Markus

Hendrik Busch wrote:
>Hi!
>>
Franz, are you joking?
Do you see any <sectiontags on the URLs you posted?
Maybe I am blind, but I don't see any, actually.
>>
>The text may not mention it, but the JavaDocs show it. You have got to
>abstract a little from the example and the docs.
>>
>Just make your PM look like this:
>>
><plugin>
><groupId>org.apache.maven.plugins</groupId>
><artifactId>maven-jar-plugin</artifactId>
><configuration>
><archive>
><index>true</index>
><manifest>
><addClasspath>true</addClasspath>
></manifest>
><manifestSections>
><manifestSection>
><name>S1</name>
><manifestEntries>
><N1>V1</N1>
></manifestEntries>
></manifestSection>
></manifestSections>
></archive>
></configuration>
></plugin>
>>
>This will result in a manifest like this:
>>
>Manifest-Version: 1.0
>Archiver-Version: Plexus Archiver
>Created-By: Apache Maven
>Built-By: hb
>Build-Jdk: 1.5.0_06
>Class-Path: commons-lang-2.1.jar
>>
>Name: S1
>N1: V1
>>
>Enjoy!
>>

Good day to you, Markus,

I think what Hendrik meant to say is that [1] has a link to the
MavenArchiveConfiguration javadoc ([2]). And if you analyze it, it has
addManifestEntries and addManifestEntry for the <manifestEntriesand
<manifestEntrytags respecitvely. Thus, it is worth a try to see if
addManifestSections, and addManifestSection corresponds to
<manifestSectionsand <manifestSection>.

But point well taken :-) I've created now created an issue for that ([3])
:-)

Thanks,
Franz

[1]
http://people.apache.org/~
[2]

[3]

Hi,

Markus, were you able to get what Franz was saying about the relationship
between the MavenArchiveConfiguration javadoc
and archive configuration (for the jar plugin)? From the provided example in
the Jar Plugin docs, specifically
http://people.apache.org/~,
you can see that the <archivetags (e.g. <index>, <manifestand
<manifestEntries>) correspond to the methods in the
MavenArchiveConfigurarion (setIndex(), setManifest() and
addManifestEntries() respectively).
Thus, the addManifestSections() in the MavenArchiveConfiguration is
equivalent to the <manifestSectionselement that Hendrik specified in his
email. For the <manifestSectionelement on the other hand,
you can take a look at the ManifestSection parameter of the
addManifestSection(ManifestSection section) to get the elements that you
need to set. This is basically a mapping of the methods into xml :-)

Btw Franz, I think you got the jira issue mixed up. The jira issue you
created should probably be for the Jar Plugin, not for the Javadoc plugin
:-)

Hope this helps! :-)

Thanks,
Deng

Markus Karg wrote:

Franz,

>>I think what Hendrik meant to say is that [1] has a link to the
>>MavenArchiveConfiguration javadoc ([2]). And if you analyze it, it has
>>addManifestEntries and addManifestEntry for the <manifestEntriesand
>><manifestEntrytags respecitvely. Thus, it is worth a try to see if
>>addManifestSections, and addManifestSection corresponds to
>><manifestSectionsand <manifestSection>.
>>
>>But point well taken :-) I've created now created an issue for that ([3])
>>:-)
>>
>>Thanks,
>>Franz
>>
>>[1]
>>http://people.apache.org/~
>>[2]
>>
>>[3]
>
>>
Is this bean-like behaviour typical to all Mvn2 Plugins in common, or an
implementation specifica of this particular Plugin?

Markus

begin:vcard
fn:Markus KARG
n:KARG;Markus
org:QUIPSY QUALITY GmbH;Entwicklung / R & D
adr:;;Stuttgarter Strasse
23;Pforzheim;Baden-Wuerttemberg;75179;Bundesrepublik Deutschland
email;internet:karg (AT) quipsy (DOT) de
title:Staatl. gepr. Inf.
tel;work:+49-7231-9189-52
tel;fax:+49-7231-9189-59
note:QUIPSY(R) Entwicklung / R & D
x-mozilla-html:TRUE
url:http://www.quipsy.de
version:2.1
end:vcard

deng_ching wrote:

Hi,

Markus, were you able to get what Franz was saying about the relationship
between the MavenArchiveConfiguration javadoc
and archive configuration (for the jar plugin)? From the provided example
in the Jar Plugin docs, specifically
http://people.apache.org/~,
you can see that the <archivetags (e.g. <index>, <manifestand
<manifestEntries>) correspond to the methods in the
MavenArchiveConfigurarion (setIndex(), setManifest() and
addManifestEntries() respectively).
Thus, the addManifestSections() in the MavenArchiveConfiguration is
equivalent to the <manifestSectionselement that Hendrik specified in his
email. For the <manifestSectionelement on the other hand,
you can take a look at the ManifestSection parameter of the
addManifestSection(ManifestSection section) to get the elements that you
need to set. This is basically a mapping of the methods into xml :-)

Btw Franz, I think you got the jira issue mixed up. The jira issue you
created should probably be for the Jar Plugin, not for the Javadoc plugin
:-)

Hope this helps! :-)

Thanks,
Deng

Markus Karg wrote:
>
>Franz,
>
I think what Hendrik meant to say is that [1] has a link to the
MavenArchiveConfiguration javadoc ([2]). And if you analyze it, it has
addManifestEntries and addManifestEntry for the <manifestEntriesand
<manifestEntrytags respecitvely. Thus, it is worth a try to see if
addManifestSections, and addManifestSection corresponds to
<manifestSectionsand <manifestSection>.

But point well taken :-) I've created now created an issue for that ([3])
:-)

Thanks,
Franz

[1]
http://people.apache.org/~
[2]

[3]


>Is this bean-like behaviour typical to all Mvn2 Plugins in common, or an
>implementation specifica of this particular Plugin?
>
>Markus
>
>begin:vcard
>fn:Markus KARG
>n:KARG;Markus
>org:QUIPSY QUALITY GmbH;Entwicklung / R & D
>adr:;;Stuttgarter Strasse
>23;Pforzheim;Baden-Wuerttemberg;75179;Bundesrepublik Deutschland
>email;internet:karg (AT) quipsy (DOT) de
>title:Staatl. gepr. Inf.
>tel;work:+49-7231-9189-52
>tel;fax:+49-7231-9189-59
>note:QUIPSY(R) Entwicklung / R & D
>x-mozilla-html:TRUE
>url:http://www.quipsy.de
>version:2.1
>end:vcard
>
>
>

Good day to you, Deng,

Thanks for the correction ^_^ my bad :-P the correct jira issue is now in
[1]

Thanks,
Franz

[1]