> ... and the user would be able to invoke ant like this: > $ ant -Dmanifest.Foo=bar -Dmanifest.Color=green > > The build.xml should find every property with the "manifest." prefix, > ... > Foo: Bar > Color: Green > > The only thing I can think of is to use a property set like this: > <propertyset id="manifest-properties"> > <propertyref prefix="manifest."> > </propertyset> > > ... and extend Manifest.java to take a propertyref id. > > Does anyone have any better ideas/suggestions?? Thanks.
I never needed something like this, but why not... Note though that I feel you might be better served by creating a new file (a .properties for example) in META-INF, using a conventional name, that's very easy to load as a resource. Maybe you are "abusing" the manifest by wanting to add your own meta-data no? If you persist in the manifest route, then taking a <propertyset> is a good idea. The problem with <manifest> is that there are 2 of them. The stand-alone one, and the one nested in <jar>. If I recall correctly, you'd need to modify both to have a consistent behavior. --DD --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
