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/~dennisl/maven-jar-plugin/examples/manifest-customization.html,
> you can see that the <archive> tags (e.g. <index>, <manifest> and
> <manifestEntries>) correspond to the methods in the
> MavenArchiveConfigurarion (setIndex(), setManifest() and
> addManifestEntries() respectively).
> Thus, the addManifestSections() in the MavenArchiveConfiguration is
> equivalent to the <manifestSections> element that Hendrik specified in his
> email. For the <manifestSection> element 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 <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
>>>  
>>>
>> 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:[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
>> 
>> 
>> 
> 
> 

Good day to you, Deng,

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

Thanks,
Franz

[1] http://jira.codehaus.org/browse/MJAR-58
-- 
View this message in context: 
http://www.nabble.com/%3Csection%3E-tf2271367.html#a6355940
Sent from the Maven - Users forum at Nabble.com.


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

Reply via email to