You are viewing a plain text version of this content. The canonical link for it is here.
Posted to legal-discuss@apache.org by "Sandro Boehme (JIRA)" <ji...@apache.org> on 2015/03/24 15:57:52 UTC
[jira] [Resolved] (LEGAL-217) Use of npm with the Artistic License
2.0
[ https://issues.apache.org/jira/browse/LEGAL-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sandro Boehme resolved LEGAL-217.
---------------------------------
Resolution: Invalid
This was a misunderstanding. In it's license npm refers to a package as a general software package. Not as an npm package in its registry.
See Ians explaination here:
http://apache-sling.73963.n3.nabble.com/License-question-tt4047956.html#a4048702
Thanks for the feedback anyways!
> Use of npm with the Artistic License 2.0
> -----------------------------------------
>
> Key: LEGAL-217
> URL: https://issues.apache.org/jira/browse/LEGAL-217
> Project: Legal Discuss
> Issue Type: Question
> Reporter: Sandro Boehme
>
> npm (Node.js package manager) uses the Artistic License 2.0 and I would like to use it in the build process of an Apache Sling component. Would that be according to the ASF policies?
> Please see SLING-4463 and it's parent issue SLING-4462 for details.
> Thanks in advance,
> Sandro
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org