Hi,
I was wondering that if you make an application for a large corporate firm
using Maven 2, what problems can you expect regarding licenses of (transitive)
dependencies. Some licenses force you to make the application you made, based
on their open source product, open source and make it available to the
community. The corporate firm probably will not be amused by this but it could
lead to legal issues. I'm not too familair with all licenses but this point was
made by someone who does know a lot.
Is there a way to enforce this with Maven (probably not) or should you do
something with the blacklist of say Archiva.
Your thoughts on this?
Maarten
____________________________________________________________________________________
Get easy, one-click access to your favorites.
Make Yahoo! your homepage.
http://www.yahoo.com/r/hs
