> > There would be other ways to accomplish this -- for instance, if Maven were > > aware of the license (if it were published in the POM), you could put > > You'd probably still have to cope with libraries that are (say) GPL, > but don't declare themselves in the pom as such.
Which is why people who are seriously concerned about these issues (and using the latest Maven2 for building their code) use multiple separate environments, each with their own repo manager, implement policies to manage what makes it into the repos, etc. This can be a full-time job in and of itself depending on the number of projects/artifacts you are supporting. I agree that "building code" and "managing code licensing" are loosely-related concepts, but thus far, Maven is really only focused on the first aspect. If someone was really motivated to add the second, they could probably do it, but it would be nontrivial. Until then, most people will lock-down versions, use continuous integration, and maintain separate internal repos to deal with this situation. Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
