> Agreed. I handled this in scripting by adding an element to each dependency > declaration marking it as optional or not. > I used this new element to create the release notes (combined with > changes.xml) as well as create website docs. > Perhaps we could do something similar in Maven 2.
Maven2 has a <provided> scope for dependencies. Maybe this is the right solution? We use it in MyFaces for the Tomahawk components which depend on a JSF implementation. We compile against the MyFaces implementation but we do not distribute this with Tomahawk. Its up to the end user to provide their own implementation. Of course I don't know much about the Struts/Tiles EL so maybe I am confused ... > Don Sean --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
