Franz,
Is this bean-like behaviour typical to all Mvn2 Plugins in common, or an implementation specifica of this particular Plugin?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 <manifestEntries> and <manifestEntry> tags respecitvely. Thus, it is worth a try to see if addManifestSections, and addManifestSection corresponds to <manifestSections> and <manifestSection>.But point well taken :-) I've created now created an issue for that ([3]) :-) Thanks, Franz [1] http://people.apache.org/~dennisl/maven-jar-plugin/examples/manifest-customization.html [2] http://maven.apache.org/ref/current/maven-archiver/apidocs/org/apache/maven/archiver/MavenArchiveConfiguration.html [3] http://jira.codehaus.org/browse/MJAVADOC-91
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:[EMAIL PROTECTED] 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
smime.p7s
Description: S/MIME Cryptographic Signature
