You are viewing a plain text version of this content. The canonical link for it is here.
Posted to legal-discuss@apache.org by "Andreas Veithen (JIRA)" <ji...@apache.org> on 2010/05/24 19:28:24 UTC

[jira] Created: (LEGAL-74) Inclusion of Jaxen code in Axiom

Inclusion of Jaxen code in Axiom
--------------------------------

                 Key: LEGAL-74
                 URL: https://issues.apache.org/jira/browse/LEGAL-74
             Project: Legal Discuss
          Issue Type: Question
            Reporter: Andreas Veithen


The Axiom project includes the source code of two classes and a set of test files from Jaxen. The reason is that these files are part of the Jaxen test suite and are not available as Maven artifacts. An example can be found at [1]. These files were initially checked into SVN in 2005 [2] and we have no trace showing that the legal questions around these files have been addressed properly. There are several questions here:

* Is the license compatible (I guess yes because Jaxen is used by several ASF projects)?
* How to avoid legal issues caused by the inclusion of the code as sources into Axiom? In particular, should the Java classes keep their original license headers, and what files need to be added to the JAR artifact and source/binary distributions of the Axiom project?

[1] https://svn.apache.org/repos/asf/webservices/commons/trunk/modules/axiom/modules/axiom-api/src/test/java/org/jaxen/test/ExprComparator.java
[2] http://svn.apache.org/viewvc?view=revision&revision=210210

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org


[jira] Commented: (LEGAL-74) Inclusion of Jaxen code in Axiom

Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/LEGAL-74?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12870732#action_12870732 ] 

Davanum Srinivas commented on LEGAL-74:
---------------------------------------

http://jaxen.codehaus.org/license.html

> Inclusion of Jaxen code in Axiom
> --------------------------------
>
>                 Key: LEGAL-74
>                 URL: https://issues.apache.org/jira/browse/LEGAL-74
>             Project: Legal Discuss
>          Issue Type: Question
>            Reporter: Andreas Veithen
>
> The Axiom project includes the source code of two classes and a set of test files from Jaxen. The reason is that these files are part of the Jaxen test suite and are not available as Maven artifacts. An example can be found at [1]. These files were initially checked into SVN in 2005 [2] and we have no trace showing that the legal questions around these files have been addressed properly. There are several questions here:
> * Is the license compatible (I guess yes because Jaxen is used by several ASF projects)?
> * How to avoid legal issues caused by the inclusion of the code as sources into Axiom? In particular, should the Java classes keep their original license headers, and what files need to be added to the JAR artifact and source/binary distributions of the Axiom project?
> [1] https://svn.apache.org/repos/asf/webservices/commons/trunk/modules/axiom/modules/axiom-api/src/test/java/org/jaxen/test/ExprComparator.java
> [2] http://svn.apache.org/viewvc?view=revision&revision=210210

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org


[jira] Commented: (LEGAL-74) Inclusion of Jaxen code in Axiom

Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/LEGAL-74?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12870727#action_12870727 ] 

Davanum Srinivas commented on LEGAL-74:
---------------------------------------

https://issues.apache.org/jira/browse/AXIS2-70

> Inclusion of Jaxen code in Axiom
> --------------------------------
>
>                 Key: LEGAL-74
>                 URL: https://issues.apache.org/jira/browse/LEGAL-74
>             Project: Legal Discuss
>          Issue Type: Question
>            Reporter: Andreas Veithen
>
> The Axiom project includes the source code of two classes and a set of test files from Jaxen. The reason is that these files are part of the Jaxen test suite and are not available as Maven artifacts. An example can be found at [1]. These files were initially checked into SVN in 2005 [2] and we have no trace showing that the legal questions around these files have been addressed properly. There are several questions here:
> * Is the license compatible (I guess yes because Jaxen is used by several ASF projects)?
> * How to avoid legal issues caused by the inclusion of the code as sources into Axiom? In particular, should the Java classes keep their original license headers, and what files need to be added to the JAR artifact and source/binary distributions of the Axiom project?
> [1] https://svn.apache.org/repos/asf/webservices/commons/trunk/modules/axiom/modules/axiom-api/src/test/java/org/jaxen/test/ExprComparator.java
> [2] http://svn.apache.org/viewvc?view=revision&revision=210210

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org


[jira] Closed: (LEGAL-74) Inclusion of Jaxen code in Axiom

Posted by "Henri Yandell (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/LEGAL-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Henri Yandell closed LEGAL-74.
------------------------------

    Resolution: Fixed

+1 to Kevan's comment. That's BSD, no concerns over licensing provided you follow the attribution requirements. i.e Make sure it's in your LICENSE/NOTICE.

I would suggest making these files a decoupled project build (if that's not already done). Then I would have the axis-jaxen-type jar built have its own LICENSE. With respect to Kevan's last paragraph, I'm a strong fan of this approach when the included work is a decoupled dependency (be it dll, jar, so etc).

If you treat this BSD code as akin to your Apache source code; keep the headers at the top, add an Apache header as well if you modify and put the license attribution in LICENSE or NOTICE.

Resolving as Kevan and I show consensus :) Please reopen if you've more questions or any of the above isn't clearly explained.

> Inclusion of Jaxen code in Axiom
> --------------------------------
>
>                 Key: LEGAL-74
>                 URL: https://issues.apache.org/jira/browse/LEGAL-74
>             Project: Legal Discuss
>          Issue Type: Question
>            Reporter: Andreas Veithen
>
> The Axiom project includes the source code of two classes and a set of test files from Jaxen. The reason is that these files are part of the Jaxen test suite and are not available as Maven artifacts. An example can be found at [1]. These files were initially checked into SVN in 2005 [2] and we have no trace showing that the legal questions around these files have been addressed properly. There are several questions here:
> * Is the license compatible (I guess yes because Jaxen is used by several ASF projects)?
> * How to avoid legal issues caused by the inclusion of the code as sources into Axiom? In particular, should the Java classes keep their original license headers, and what files need to be added to the JAR artifact and source/binary distributions of the Axiom project?
> [1] https://svn.apache.org/repos/asf/webservices/commons/trunk/modules/axiom/modules/axiom-api/src/test/java/org/jaxen/test/ExprComparator.java
> [2] http://svn.apache.org/viewvc?view=revision&revision=210210

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org


[jira] Commented: (LEGAL-74) Inclusion of Jaxen code in Axiom

Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/LEGAL-74?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12870736#action_12870736 ] 

Davanum Srinivas commented on LEGAL-74:
---------------------------------------

Jaxen license is in SVN and from what i remember was being shipped with axiom - http://svn.apache.org/viewvc/webservices/commons/trunk/modules/axiom/legal/

> Inclusion of Jaxen code in Axiom
> --------------------------------
>
>                 Key: LEGAL-74
>                 URL: https://issues.apache.org/jira/browse/LEGAL-74
>             Project: Legal Discuss
>          Issue Type: Question
>            Reporter: Andreas Veithen
>
> The Axiom project includes the source code of two classes and a set of test files from Jaxen. The reason is that these files are part of the Jaxen test suite and are not available as Maven artifacts. An example can be found at [1]. These files were initially checked into SVN in 2005 [2] and we have no trace showing that the legal questions around these files have been addressed properly. There are several questions here:
> * Is the license compatible (I guess yes because Jaxen is used by several ASF projects)?
> * How to avoid legal issues caused by the inclusion of the code as sources into Axiom? In particular, should the Java classes keep their original license headers, and what files need to be added to the JAR artifact and source/binary distributions of the Axiom project?
> [1] https://svn.apache.org/repos/asf/webservices/commons/trunk/modules/axiom/modules/axiom-api/src/test/java/org/jaxen/test/ExprComparator.java
> [2] http://svn.apache.org/viewvc?view=revision&revision=210210

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org


[jira] Commented: (LEGAL-74) Inclusion of Jaxen code in Axiom

Posted by "Kevan Miller (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/LEGAL-74?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12870917#action_12870917 ] 

Kevan Miller commented on LEGAL-74:
-----------------------------------

My 2 cents...

That's a BSD License (specifically BSD without an advertising clause). It's classified as a "Category A" license (http://www.apache.org/legal/resolved.html#category-a). It's ok to include the source in an Apache release. 

Only the copyright holder should alter the license headers. So, unless the copyright holder agrees to relicense the files under the Apache License, you must not change them.

The source and jar files built from this source should include LICENSE files. These files should contain the Apache License with the JAXEN license appended to this file (along with any other licenses which might apply). IIUC, the LICENSE file should list the names of the BSD licensed files in the distribution (so that it is clear which files are BSD licensed).

My current understanding is that the NOTICE file need not refer to these JAXEN files or give any attribution to the JAXEN project. The LICENSE file already meets the requirements of the LICENSE.

I'm just recalling that some of the Axis projects contain multiple license files in a 'licenses' directory. I've never been a fan of this practice. IMO, it's more difficult for consuming projects. Also, I recall that jar files often end up with confusing/incorrect LICENSE files. However, in general, I believe the practice is acceptable. If this is the case, the JAXEN license would be placed in your 'licenses' directory. 

> Inclusion of Jaxen code in Axiom
> --------------------------------
>
>                 Key: LEGAL-74
>                 URL: https://issues.apache.org/jira/browse/LEGAL-74
>             Project: Legal Discuss
>          Issue Type: Question
>            Reporter: Andreas Veithen
>
> The Axiom project includes the source code of two classes and a set of test files from Jaxen. The reason is that these files are part of the Jaxen test suite and are not available as Maven artifacts. An example can be found at [1]. These files were initially checked into SVN in 2005 [2] and we have no trace showing that the legal questions around these files have been addressed properly. There are several questions here:
> * Is the license compatible (I guess yes because Jaxen is used by several ASF projects)?
> * How to avoid legal issues caused by the inclusion of the code as sources into Axiom? In particular, should the Java classes keep their original license headers, and what files need to be added to the JAR artifact and source/binary distributions of the Axiom project?
> [1] https://svn.apache.org/repos/asf/webservices/commons/trunk/modules/axiom/modules/axiom-api/src/test/java/org/jaxen/test/ExprComparator.java
> [2] http://svn.apache.org/viewvc?view=revision&revision=210210

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org


[jira] Commented: (LEGAL-74) Inclusion of Jaxen code in Axiom

Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/LEGAL-74?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12873261#action_12873261 ] 

Andreas Veithen commented on LEGAL-74:
--------------------------------------

Kevan,
Henri,

Thanks for your feedback. I indeed already moved [1] the Jaxen stuff to a separate Maven module (also because this prevents people from accidentally modifying these files, as happened in the past). The only remaining thing now is to add specific LICENSE/NOTICE files to that project.

[1] http://svn.apache.org/viewvc?view=revision&revision=948612

> Inclusion of Jaxen code in Axiom
> --------------------------------
>
>                 Key: LEGAL-74
>                 URL: https://issues.apache.org/jira/browse/LEGAL-74
>             Project: Legal Discuss
>          Issue Type: Question
>            Reporter: Andreas Veithen
>
> The Axiom project includes the source code of two classes and a set of test files from Jaxen. The reason is that these files are part of the Jaxen test suite and are not available as Maven artifacts. An example can be found at [1]. These files were initially checked into SVN in 2005 [2] and we have no trace showing that the legal questions around these files have been addressed properly. There are several questions here:
> * Is the license compatible (I guess yes because Jaxen is used by several ASF projects)?
> * How to avoid legal issues caused by the inclusion of the code as sources into Axiom? In particular, should the Java classes keep their original license headers, and what files need to be added to the JAR artifact and source/binary distributions of the Axiom project?
> [1] https://svn.apache.org/repos/asf/webservices/commons/trunk/modules/axiom/modules/axiom-api/src/test/java/org/jaxen/test/ExprComparator.java
> [2] http://svn.apache.org/viewvc?view=revision&revision=210210

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org