>Doh! That makes sense. Our organization doesn't distribute software, thus >we don't worry as much about such issues.
It is prudent to pay attention to this for internal only software as well. > 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. How do you disable the local repository? Craig --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
