En l'instant précis du 19/01/2009 14:43, Jaikiran s'exprimait en ces termes: > I was working on a Maven project and was looking for a plugin which could > upload some documentation to some remote location. While searching this > mailing list i came across the maven-upload-plugin which is hosted at > http://repository.atlassian.com/maven2/com/atlassian/maven/plugins/maven-upload-plugin/1.1/ > http://repository.atlassian.com/maven2/com/atlassian/maven/plugins/maven-upload-plugin/1.1/ > > > Its exactly what i was looking for. But is that plugin meant to be used in a > open source project? I am curious since the plugin is hosted at a *.com > domain. Any inputs? > > > You should ask atlassian what are de licensing terms for this artifacts. Anyway, it's not because a plugin is commercial or closed source that it's use is incompatible with an open source project. What you can't do without atlassian authorisation is distribute their plugin, but as long as it's them distributing it, you are not impacted by licensing. What could be a problem to you is if atlassian stop distributing it :) The opensource nature of a project related to the distribution licences and execution of this project, not to it's build process. If you want to create an open source project that request an expensive development suite to be build, you can do it, you will just have more trouble finding developper in te open source communities :)
-- David Delbecq ICT Institut Royal Météorologique Ext:557 --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
