[
http://opencast.jira.com/browse/MH-8950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=32037#comment-32037
]
John King edited comment on MH-8950 at 10/24/12 12:44 AM:
----------------------------------------------------------
Here is the email exchange with Anthony Whyte of the Sakai OAE project:
Answers to your questions together with a recommendation:
1. there are any licensing issues involved with reuse?
2. can the Matterhorn team install the bundle in their own repo?
3. recommendation (read this first if you want to save time reading an
otherwise tedious email)
1. no licensing issues in the opinion of Ian Boston and myself as regards
reuse. Matterhorn is licensed ECL 2.0. Nakamura is licensed Apache 2.0. No
problems there although it should be noted that the merged mail-activation jar
is licensed CDDL, 1.0 and below it GPL, 2.0 along with the Sun classpath
exception (crack the jar open and have a look at LICENSE.txt) [1]. This is how
it should be. It's the same license for both the javax activation jar 1.1.1
and mail-1.4.2 libraries. Combining the two unmodified libraries into a single
distributable jar does not appear to violate the terms of the Sun stewarded
license. I use the qualifier "appear" because neither Ian nor I are attorneys
specializing software licensing. Likewise, I see no problems with reuse of the
existing bundle.
Of minor importance (if you explode the jar and have a peek inside) is what I
take to be a cut-and-paste error in the
org.sakaiproject.nakamura.javax-activation-mail bundle pom license header
created by Carl. The header states "Licensed to the Apache Software Foundation
. . . ." when it should really read "Licensed to the Sakai Foundation . . . ."
[2] Interpreted narrowly the Matterhorn folks may not need to list the Sakai
Foundation in its licenses.txt file (see below) since it already lists the ASF
[3]. So you may not have to add to your licenses.txt file:
"This product includes software developed by the Sakai Foundation
(http://sakaiproject.org), licensed under the terms of the Apache Software
License 2.0."
All we did was pull two libraries together in a distributable bundle in order
to address a classloader issue and crafted a maven pom.xml file to define the
bundle. That I suppose counts for something. As Carl noted in 2009: "I have,
to my surprise, been able to get activation-1.1.1 and mail-1.4.2 to play nice
in OSGi. Adding sun.security.util;resolution;=optional to Import-Package
worked for this. I was hesitant to do this until I read through the javamail
code and found that they use reflection to pick up sun.security.util and do not
rely on it." [4]
<Import-Package>
!javax.activation.*,
!com.sun.activation.*,
!javax.mail.*,
!com.sun.mail.*,
sun.security.util;resolution:=optional,
*
</Import-Package>
However, it was not our idea. Carsten Ziegeler recommended the approach on the
Sling users list on 27 Oct 2009 [5]. The Felix team had earlier encountered
the same problem and created a merged bundle for themselves. See their pom for
the approach they took [6].
2. Sure, if you think it necessary. The Sakai Maven2 repo has a history of
high availability and simply adding a <repository> entry for the Sakai Maven2
repo in Matterhorn's base pom <repositories> section is all you really need to
do. But if you want to pop a copy of the jar into your repo feel free.
3. Now for the recommendation. Nakamura is a moribund project (which is not
the same as saying OAE is dead--it ain't). We see no benefit in Matterhorn
binding to any of Nakamura's artifacts, especially in this case as the Felix
guys solved it first and the recommended approach has been around since at
least 2009. Ian and I suggest that you simply replicate what Carl did in 2009
and create your own merged mail and activation bundle. Use Carl's pom as a
guide. Note the importance of adding the
sun.security.util;resolution;=optional to <Import-Package>.
Cheers,
Anth
[1] http://opensource.org/licenses/cddl-1.0
[2]
http://source.sakaiproject.org/maven2/org/sakaiproject/nakamura/javax.activation-mail/1.1.1.1.4.2-1.4.2/
[3] https://opencast.jira.com/svn/MH/trunk/docs/licenses.txt
[4] http://bit.ly/Tgsrss
[5]
http://mail-archives.apache.org/mod_mbox/sling-dev/200910.mbox/%[email protected]%3E
[6] http://svn.apache.org/repos/asf/felix/trunk/commons/commons-email/pom.xml
On Oct 17, 2012, at 5:02 PM, John King wrote:
> Hello Anthony,
>
> I am currently working on UC Berkeley's local implementation of Opencast
> Matterhorn. As part of my initial work on the project I found a fix for a
> bug that was preventing upload of videos to YouTube.
>
> See http://opencast.jira.com/browse/MH-8950.
>
> The bug was caused by the use of the javax.mail and javax.activation
> libraries in two separate OSGI bundles where they were unable to load static
> resources between bundles. The fix was to package both libraries in one OSGI
> bundle.
>
> By happenstance, Carl Hall solved the very same problem in Sakai Nakamura in
> 2009.
> See http://thecarlhall.wordpress.com/2009/10/27/javamail-in-osgi/ and
> https://groups.google.com/forum/?fromgroups=#!topicsearchin/sakai-kernel/group:sakai-kernel$20AND$20subject:email$20AND$20Carl$20AND$20Hall/sakai-kernel/dG7kUdkP5Ec
>
> The artifact Carl created is nakamura/bundles/activation-mail. Its maven
> repository location is, for the 1.4.2 release version,
> http://source.sakaiproject.org/maven2/org/sakaiproject/nakamura/javax.activation-mail/1.1.1.1.4.2-1.4.2.
>
> We would like to reuse that bundle and install it into the Matterhorn maven
> repository. I am writing to be sure there would not be licensing issues with
> doing that and, if there are issues, to resolve them so we may use the
> activation-mail bundle in Matterhorn.
>
> I did chat with Carl after I, fortuitously, found his solution and he
> indicated that he thought this type of reuse would be allowed under Sakai
> licensing.
>
> Could you confirm that for us or let us know how we need to proceed so as to
> be in compliance with Sakai licensing?
>
> Thanks for you time on this and hope you are doing well.
>
was (Author: johnk):
Here is the email exchange with Anthony Whyte of the Sakai OAE project:
Answers to your questions together with a recommendation:
1. there are any licensing issues involved with reuse?
2. can the Matterhorn team install the bundle in their own repo?
3. recommendation (read this first if you want to save time reading an
otherwise tedious email)
1. no licensing issues in the opinion of Ian Boston and myself as regards
reuse. Matterhorn is licensed ECL 2.0. Nakamura is licensed Apache 2.0. No
problems there although it should be noted that the merged mail-activation jar
is licensed CDDL, 1.0 and below it GPL, 2.0 along with the Sun classpath
exception (crack the jar open and have a look at LICENSE.txt) [1]. This is how
it should be. It's the same license for both the javax activation jar 1.1.1
and mail-1.4.2 libraries. Combining the two unmodified libraries into a single
distributable jar does not appear to violate the terms of the Sun stewarded
license. I use the qualifier "appear" because neither Ian nor I are attorneys
specializing software licensing. Likewise, I see no problems with reuse of the
existing bundle.
Of minor importance (if you explode the jar and have a peek inside) is what I
take to be a cut-and-paste error in the
org.sakaiproject.nakamura.javax-activation-mail bundle pom license header
created by Carl. The header states "Licensed to the Apache Software Foundation
. . . ." when it should really read "Licensed to the Sakai Foundation . . . ."
[2] Interpreted narrowly the Matterhorn folks may not need to list the Sakai
Foundation in its licenses.txt file (see below) since it already lists the ASF
[3]. So you may not have to add to your licenses.txt file:
"This product includes software developed by the Sakai Foundation
(http://sakaiproject.org), licensed under the terms of the Apache Software
License 2.0."
All we did was pull two libraries together in a distributable bundle in order
to address a classloader issue and crafted a maven pom.xml file to define the
bundle. That I suppose counts for something. As Carl noted in 2009: "I have,
to my surprise, been able to get activation-1.1.1 and mail-1.4.2 to play nice
in OSGi. Adding sun.security.util;resolution;=optional to Import-Package
worked for this. I was hesitant to do this until I read through the javamail
code and found that they use reflection to pick up sun.security.util and do not
rely on it." [4]
<Import-Package>
!javax.activation.*,
!com.sun.activation.*,
!javax.mail.*,
!com.sun.mail.*,
sun.security.util;resolution:=optional,
*
</Import-Package>
However, it was not our idea. Carsten Ziegeler recommended the approach on the
Sling users list on 27 Oct 2009 [5]. The Felix team had earlier encountered
the same problem and created a merged bundle for themselves. See their pom for
the approach they took [6].
2. Sure, if you think it necessary. The Sakai Maven2 repo has a history of
high availability and simply adding a <repository> entry for the Sakai Maven2
repo in Matterhorn's base pom <repositories> section is all you really need to
do. But if you want to pop a copy of the jar into your repo feel free.
3. Now for the recommendation. Nakamura is a moribund project (which is not
the same as saying OAE is dead--it ain't). We see no benefit in Matterhorn
binding to any of Nakamura's artifacts, especially in this case as the Felix
guys solved it first and the recommended approach has been around since at
least 2009. Ian and I suggest that you simply replicate what Carl did in 2009
and create your own merged mail and activation bundle. Use Carl's pom as a
guide. Note the importance of adding the
sun.security.util;resolution;=optional to <Import-Package>.
Cheers,
Anth
[1] http://opensource.org/licenses/cddl-1.0
[2]
http://source.sakaiproject.org/maven2/org/sakaiproject/nakamura/javax.activation-mail/1.1.1.1.4.2-1.4.2/
[3] https://opencast.jira.com/svn/MH/trunk/docs/licenses.txt
[4] http://bit.ly/Tgsrss
[5]
http://mail-archives.apache.org/mod_mbox/sling-dev/200910.mbox/%[email protected]%3E
[6] http://svn.apache.org/repos/asf/felix/trunk/commons/commons-email/pom.xml
On Oct 17, 2012, at 5:02 PM, John King wrote:
> Hello Anthony,
>
> I am currently working on UC Berkeley's local implementation of Opencast
> Matterhorn. As part of my initial work on the project I found a fix for a
> bug that was preventing upload of videos to YouTube.
>
> See http://opencast.jira.com/browse/MH-8950.
>
> The bug was caused by the use of the javax.mail and javax.activation
> libraries in two separate OSGI bundles where they were unable to load static
> resources between bundles. The fix was to package both libraries in one OSGI
> bundle.
>
> By happenstance, Carl Hall solved the very same problem in Sakai Nakamura in
> 2009.
> See http://thecarlhall.wordpress.com/2009/10/27/javamail-in-osgi/ and
> https://groups.google.com/forum/?fromgroups=#!topicsearchin/sakai-kernel/group:sakai-kernel$20AND$20subject:email$20AND$20Carl$20AND$20Hall/sakai-kernel/dG7kUdkP5Ec
>
> The artifact Carl created is nakamura/bundles/activation-mail. Its maven
> repository location is, for the 1.4.2 release version,
> http://source.sakaiproject.org/maven2/org/sakaiproject/nakamura/javax.activation-mail/1.1.1.1.4.2-1.4.2.
>
> We would like to reuse that bundle and install it into the Matterhorn maven
> repository. I am writing to be sure there would not be licensing issues with
> doing that and, if there are issues, to resolve them so we may use the
> activation-mail bundle in Matterhorn.
>
> I did chat with Carl after I, fortuitously, found his solution and he
> indicated that he thought this type of reuse would be allowed under Sakai
> licensing.
>
> Could you confirm that for us or let us know how we need to proceed so as to
> be in compliance with Sakai licensing?
>
> Thanks for you time on this and hope you are doing well.
>
> --
> John King
> Applications Programmer
> Learning Systems Group
> Educational Technology Services
> 9 Dwinelle Hall - Mail
> 117 Dwinelle Hall - Office
> University of California
> Berkeley, CA 94720-2535
> Phone: 510-529-5074
> Email: [email protected]
>
> Youtube distribution service does not work anymore
> ---------------------------------------------------
>
> Key: MH-8950
> URL: http://opencast.jira.com/browse/MH-8950
> Project: Matterhorn Project
> Issue Type: Bug
> Components: Distribution
> Affects Versions: 1.4
> Reporter: Xavier Butty
> Assignee: John King
> Fix For: 1.4
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
http://opencast.jira.com/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn
To unsubscribe please email
[email protected]
_______________________________________________
