Hi, in Maven, we have only one way of specifying dependency. In some cases, a project may have different dependencies at runtime and at compile time. I can think of two examples:
1. A project that uses a dependent library that guarantees backward API compatibility. The project may not want to use any new API but they want to run against any improved code. 2. A dependency library can be split into an API portion and an implementation portion. To prevent anyone from using the implementation portion, one may NOT want to have any implementation class in the compile classpath. Do you think they are valid scenarios? How would Maven deal with them? Charles __________________________________________________ Do you Yahoo!? Yahoo! Web Hosting - establish your business online http://webhosting.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
