On Jul 25, 2005, at 12:06 PM, Marcus Brito wrote:

At runtime, Tapestry would load all MANIFEST.MF files, and check if any of them contains Tapestry-Component-Library attributes, and automatically add any
libraries found to the current application.

What do you propose should happen when two JARs set the same Tapestry- Component-Library value?

--
Kevin

Reply via email to