On Dec 26, 2007 2:25 PM, aldana <[EMAIL PROTECTED]> wrote: > Heinrich Nirschl wrote: > > > > No, the optional library may be needed for compiling. It can still be > > optional if it is never loaded at runtime for a certain use case. > > > but how should someone know if a certain use case is not executed on runtime > (to me that sounds more like a hint to dead code...). do you know a real > maven2 project where this optional is used and makes sense?
A good example is commons-logging:commons-logging:1.1.1. It has optional dependencies on the logging frameworks it supports. When you actually use it, you want just one framework and not all. Previous versions did not have the dependencies declared as optional. As a consequence, users had to write a lot of exclusions in the POM (or to live with the unnecessary jars that were pulled in). --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
