Because the code I'm writing is internal and proprietary in nature. Using maven to build it generates no licensing obligations on my code. Linking against any of the libraries that maven uses does generate licensing obligations on my code.
We are looking at setting up an interanl repository where all of our shared libraries will reside. This will allow us control and tracking over licensing. It would be against company policy to use any libraries outside our central repository while writing your code. The build tool should have no requirements about what's in my repository it should only be about what my code needs. Craig -----Original Message----- From: Jarrell, Maury [mailto:[EMAIL PROTECTED] Sent: Thursday, August 26, 2004 10:55 AM To: 'Maven Users List' Subject: RE: Is there a way to separate maven's repository from my reposit ory? Hi, Craig, Doesn't Maven's use imply "certification" of the libraries it uses? In other words, why would you approve Maven's use, and thus its dependencies, and not certify those dependencies for use in other ways? I am very new to Maven and may not understand your issue at all, but I run Maven on a server with no internet access. I, somewhat tediously, downloaded all the jars Maven needed to a local repository and then manually added dependencies from my project. If my organization dictated that there was to be only one repository, then the only way for any other developer to add a library would be to go through whatever process we set up to get one manually added. Thoughts? Maury --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
