CORUM, M E [AG/1000] wrote:
I assume that you would be replacing that with some equivalent functionality, right? Otherwise, you would be taking away the capability for large companies to use Maven. Let me give an example (actually two). We have jar files from vendors that our Maven projects must depend on. In one case, there is a licensing agreement that disallows us from putting these jars into Maven/Nexus. In another case, the jar is "security-sensitive" and must not be put in Maven due to audit or security requirements. The company I work at has over 200 Maven projects now. Taking out system scope would immediately cause us to have to look for an alternative to Maven due to legal, audit, and security requirements. System scope (or an equivalent capability) must stay in Maven for it to be used by many companies.
Or you could just patch maven to put the feature back ;) Regards, Graham --
smime.p7s
Description: S/MIME Cryptographic Signature
