[EMAIL PROTECTED] wrote: ..
3. we need a manifest to handle versions and dependencies; it could be the normal manifest, or it is our own XML descriptor.
+1
With a very strong -1 on using (only ) a XML descriptor for things that are well-defined for the normal manifest - it is important that generic
tools are able to manipulate the jar.
I am a committer in Cocoon, Forrest, and have been using XML for quite some time.
This said, if I would have the right to vote, I'd vote -1 for the xml descriptor, which seems to fit in the typical everything-is-a-nail anti-pattern.
So I think all dependency, version, etc should go to MANIFEST.
The task=classname should go in a properties file ( and I think
we should settle on a default location and name - like
META-INF/ant.properties ). Everything else should go to the XML descriptor ( like docs, etc ).
+1
It would be fine if all the information are put in the XML descriptor
as long as the packaging process will generate MANIFEST and ant.properties from the XML.
+1 again
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
