Well, flex-mojos is an independent tool. So I don't see the problem. What you can't do is create something based on flex-mojos (I mean another mojo using flex-mojos code) and change license. Is like an IDE licensed under GPL, it won't prevent you from licensing your code as you witch.
VELO On Thu, Jan 8, 2009 at 11:01 AM, Jaza <[email protected]> wrote: > > If any of those super poms depend on something gpl that is non-command > line then they would cause me to violate the gpl of the other stuff > because of the super-poms. This would make this project useless to me > even if I could I could use gpl libs in my build code. > > I can't make my build code gpl because I want all my project code to > be ISC Licensed (BSD Style). > > So basically it seems like you are forcing anybody that uses your > project to violate it's own license with mit licenced super-poms > depending on poms that depend on gpl maven mojos. > > I am not sure how clearly or narrowly the gpl defines linking, but > this sure seems to count. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Flex Mojos" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/flex-mojos?hl=en?hl=en http://blog.flex-mojos.info/ -~----------~----~----~----~------~----~------~--~---
