On 2011-02-16, David Weintraub wrote: >> On 2011-02-16, David Weintraub wrote:
>> I'd like a way to create a reference to this Manifest setup like you >> can with <patternsets> or <paths>, so I don't have to keep repeating >> this over and over > On Wed, Feb 16, 2011 at 10:57 AM, Stefan Bodewig <bode...@apache.org> wrote: >> Unfortunately <manifest> doesn't support the id/refid mechanism. >> You could use the manifest task to write your manifest to a (temporary) >> file and feed that to each jar task. > I saw that, but unfortunately I need to merge this information to the > manifest file in that project too. I don't believe I can specify two > manifest files and have the <jar> task merging them together. You can have one file and one nested <manifest> element and they get merged. Would it be possible to have the project's manifest be specified as nested element of the <jar> task? If not all other things I can come up with are kludges like copying the project's manifest to a temporary file, update it with the manifest task and then jar using the modified temporary file. Then you could package it up in a <macrodef>. If you go that far, it is probably a lot easier to create a presetdef for your jar task that contains the common manifest information and use it in the two places that currently hold the duplication. Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@ant.apache.org For additional commands, e-mail: user-h...@ant.apache.org
