> -----Original Message----- > From: Courtney, Craig [mailto:[EMAIL PROTECTED] > Sent: Thursday, August 26, 2004 10:02 AM > To: Maven Users List > Subject: RE: Is there a way to separate maven's repository from my reposit > ory? > > 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.
Doh! That makes sense. Our organization doesn't distribute software, thus we don't worry as much about such issues. > > 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. It sounds like you might already be doing this, or have already determined this wouldn't work, but if you used the maven.repo.local property to point to maven's build repository and maven.repo.remote to point to an internal repository that housed only libraries you use and can successfully license, then wouldn't solve most of the issue? I guess it would still be possible for a developer to use a Maven dependency, but his folly would get exposed when you only allowed the remote jars to be included in a distribution. Take care, Maury --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
