You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Richard S. Hall (JIRA)" <ji...@apache.org> on 2006/09/18 07:48:24 UTC
[jira] Created: (FELIX-147) Determine how to handle OSGi source and
classes for release
Determine how to handle OSGi source and classes for release
-----------------------------------------------------------
Key: FELIX-147
URL: http://issues.apache.org/jira/browse/FELIX-147
Project: Felix
Issue Type: Task
Reporter: Richard S. Hall
Priority: Blocker
Fix For: 0.8.0
We need to make sure we understand what we can and cannot do with the OSGi sources and/or class files. For example, can we include the OSGi source in our release...I assume we can include the OSGi binaries without any issue. This is a third-party issue, so we need to make sure that we understand what is necessary with respect to our NOTICE file, etc. Most of this is discussed in http://www.apache.org/legal/src-headers.html and also in http://people.apache.org/~cliffs/3party.html.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FELIX-147) Determine how to handle OSGi source
and classes for release
Posted by "Francesco Furfari (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FELIX-147?page=comments#action_12439422 ]
Francesco Furfari commented on FELIX-147:
-----------------------------------------
Hi folks,
I would like to discuss about the Notice file we shuold include in the release of our sub-projects. As may you know the UPnP projects are based on a code derived by the Cyberlink library released under BSD licence. This situation is similar for other projects.
The ASF policy says to add in the Notice file any reference to third-party notices. Moreover the BSD license says:
...
# Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
# Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
...
So concerning the UPnP stuff I was thinking to a main Notice file like:
Apache Felix UPnP Base Driver
Copyright 2006 The Apache Software Foundation
This product includes software developed at
The Apache Software Foundation (http://www.apache.org/).
This software contains code derived from the Cyberlink library
and licensed under the same license as the original work
I think we should also add a *Notice-Cyberlink* file repporting the original license.
We didn't discuss yet how all our project will be packaged and released so far,
here an initial list of questions.
1. should we add the various Notice files in our CVS for each subproject ?
2. should we add the same files in the bundle (as redistribution unit) ?
3. should every subproject have its own release ? or is better topackage all the related stuff toghether?
> Determine how to handle OSGi source and classes for release
> -----------------------------------------------------------
>
> Key: FELIX-147
> URL: http://issues.apache.org/jira/browse/FELIX-147
> Project: Felix
> Issue Type: Task
> Reporter: Richard S. Hall
> Priority: Blocker
> Fix For: 0.8.0
>
>
> We need to make sure we understand what we can and cannot do with the OSGi sources and/or class files. For example, can we include the OSGi source in our release...I assume we can include the OSGi binaries without any issue. This is a third-party issue, so we need to make sure that we understand what is necessary with respect to our NOTICE file, etc. Most of this is discussed in http://www.apache.org/legal/src-headers.html and also in http://people.apache.org/~cliffs/3party.html.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FELIX-147) Determine how to handle OSGi source
and classes for release
Posted by "Richard S. Hall (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FELIX-147?page=comments#action_12438542 ]
Richard S. Hall commented on FELIX-147:
---------------------------------------
This appears to also be an issue for http.jetty since it includes interfaces from the OSGi Alliance.
> Determine how to handle OSGi source and classes for release
> -----------------------------------------------------------
>
> Key: FELIX-147
> URL: http://issues.apache.org/jira/browse/FELIX-147
> Project: Felix
> Issue Type: Task
> Reporter: Richard S. Hall
> Priority: Blocker
> Fix For: 0.8.0
>
>
> We need to make sure we understand what we can and cannot do with the OSGi sources and/or class files. For example, can we include the OSGi source in our release...I assume we can include the OSGi binaries without any issue. This is a third-party issue, so we need to make sure that we understand what is necessary with respect to our NOTICE file, etc. Most of this is discussed in http://www.apache.org/legal/src-headers.html and also in http://people.apache.org/~cliffs/3party.html.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FELIX-147) Determine how to handle OSGi source
and classes for release
Posted by "Richard S. Hall (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FELIX-147?page=comments#action_12439832 ]
Richard S. Hall commented on FELIX-147:
---------------------------------------
I think creating a wiki page to keep track of this would be fine. Perhaps we can just extend the current wiki page to have additional columns corresponding to the different issues that need to be addressed.
> Determine how to handle OSGi source and classes for release
> -----------------------------------------------------------
>
> Key: FELIX-147
> URL: http://issues.apache.org/jira/browse/FELIX-147
> Project: Felix
> Issue Type: Task
> Reporter: Richard S. Hall
> Priority: Blocker
> Fix For: 0.8.0
>
>
> We need to make sure we understand what we can and cannot do with the OSGi sources and/or class files. For example, can we include the OSGi source in our release...I assume we can include the OSGi binaries without any issue. This is a third-party issue, so we need to make sure that we understand what is necessary with respect to our NOTICE file, etc. Most of this is discussed in http://www.apache.org/legal/src-headers.html and also in http://people.apache.org/~cliffs/3party.html.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FELIX-147) Determine how to handle OSGi source
and classes for release
Posted by "Richard S. Hall (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FELIX-147?page=comments#action_12439490 ]
Richard S. Hall commented on FELIX-147:
---------------------------------------
I am not exactly sure what should go in the NOTICE files yet, but I will attempt to answer your other three questions:
1) I think each subproject should have its own NOTICE file in the root of its subproject directory in the repo.
2) I think the bundle JAR will need a NOTICE and LICENSE file too.
3) I think that bundles should be released independently. However, that does not mean that we still cannot take snapshots of the current bundle versions each time a new framework is released, if we want to have some record. Personally, I don't see the point. I think everything has its own release schedule and should evolve independently. The only argument I can see is that we could set up some extensive test suite that somehow tests all the bundles that comprise the "OSGi Service Platform" and we test and release a packaged snapshot as some sort of "sanctioned" service platform release, but I don't think we will be doing that for a while. So, for the time being, I think we should have independent releases.
> Determine how to handle OSGi source and classes for release
> -----------------------------------------------------------
>
> Key: FELIX-147
> URL: http://issues.apache.org/jira/browse/FELIX-147
> Project: Felix
> Issue Type: Task
> Reporter: Richard S. Hall
> Priority: Blocker
> Fix For: 0.8.0
>
>
> We need to make sure we understand what we can and cannot do with the OSGi sources and/or class files. For example, can we include the OSGi source in our release...I assume we can include the OSGi binaries without any issue. This is a third-party issue, so we need to make sure that we understand what is necessary with respect to our NOTICE file, etc. Most of this is discussed in http://www.apache.org/legal/src-headers.html and also in http://people.apache.org/~cliffs/3party.html.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FELIX-147) Determine how to handle OSGi source
and classes for release
Posted by "Francesco Furfari (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FELIX-147?page=comments#action_12439868 ]
Francesco Furfari commented on FELIX-147:
-----------------------------------------
Exactly, what do you think about the following additions:
*subproject*, *updated source headers*, *notice file*, *third-party license* (if required), *documentation*, *ready for release*, *checked*
Where "notice file", "third-party license", and "documantation" could be pointers to the cvs/wiki site,
"ready for release" a flag indicating that all the needed actions have been completed by some guy,
and "checked" a double check done by another person.
Ya, a double check could be an excessive prudence ... you know in Italy we have a lot of bureaucracy ;-)
> Determine how to handle OSGi source and classes for release
> -----------------------------------------------------------
>
> Key: FELIX-147
> URL: http://issues.apache.org/jira/browse/FELIX-147
> Project: Felix
> Issue Type: Task
> Reporter: Richard S. Hall
> Priority: Blocker
> Fix For: 0.8.0
>
>
> We need to make sure we understand what we can and cannot do with the OSGi sources and/or class files. For example, can we include the OSGi source in our release...I assume we can include the OSGi binaries without any issue. This is a third-party issue, so we need to make sure that we understand what is necessary with respect to our NOTICE file, etc. Most of this is discussed in http://www.apache.org/legal/src-headers.html and also in http://people.apache.org/~cliffs/3party.html.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FELIX-147) Determine how to handle OSGi source
and classes for release
Posted by "Richard S. Hall (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FELIX-147?page=comments#action_12439934 ]
Richard S. Hall commented on FELIX-147:
---------------------------------------
Sounds like a good start at least. Go ahead an edit the wiki page and add some documentation for the purpose of each column and their expected values.
> Determine how to handle OSGi source and classes for release
> -----------------------------------------------------------
>
> Key: FELIX-147
> URL: http://issues.apache.org/jira/browse/FELIX-147
> Project: Felix
> Issue Type: Task
> Reporter: Richard S. Hall
> Priority: Blocker
> Fix For: 0.8.0
>
>
> We need to make sure we understand what we can and cannot do with the OSGi sources and/or class files. For example, can we include the OSGi source in our release...I assume we can include the OSGi binaries without any issue. This is a third-party issue, so we need to make sure that we understand what is necessary with respect to our NOTICE file, etc. Most of this is discussed in http://www.apache.org/legal/src-headers.html and also in http://people.apache.org/~cliffs/3party.html.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FELIX-147) Determine how to handle OSGi source
and classes for release
Posted by "Richard S. Hall (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FELIX-147?page=comments#action_12438535 ]
Richard S. Hall commented on FELIX-147:
---------------------------------------
This is also an issue for the bundle repository subproject since it contains some interface classes from the OSGi Alliance.
> Determine how to handle OSGi source and classes for release
> -----------------------------------------------------------
>
> Key: FELIX-147
> URL: http://issues.apache.org/jira/browse/FELIX-147
> Project: Felix
> Issue Type: Task
> Reporter: Richard S. Hall
> Priority: Blocker
> Fix For: 0.8.0
>
>
> We need to make sure we understand what we can and cannot do with the OSGi sources and/or class files. For example, can we include the OSGi source in our release...I assume we can include the OSGi binaries without any issue. This is a third-party issue, so we need to make sure that we understand what is necessary with respect to our NOTICE file, etc. Most of this is discussed in http://www.apache.org/legal/src-headers.html and also in http://people.apache.org/~cliffs/3party.html.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (FELIX-147) Determine how to handle OSGi source and
classes for release
Posted by "Richard S. Hall (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FELIX-147?page=all ]
Richard S. Hall closed FELIX-147.
---------------------------------
Resolution: Fixed
Assignee: Richard S. Hall
We have OSGi copyright notices in the NOTICE file, I think we are okay here so I will close this issue.
> Determine how to handle OSGi source and classes for release
> -----------------------------------------------------------
>
> Key: FELIX-147
> URL: http://issues.apache.org/jira/browse/FELIX-147
> Project: Felix
> Issue Type: Task
> Reporter: Richard S. Hall
> Assigned To: Richard S. Hall
> Priority: Blocker
> Fix For: 0.8.0
>
>
> We need to make sure we understand what we can and cannot do with the OSGi sources and/or class files. For example, can we include the OSGi source in our release...I assume we can include the OSGi binaries without any issue. This is a third-party issue, so we need to make sure that we understand what is necessary with respect to our NOTICE file, etc. Most of this is discussed in http://www.apache.org/legal/src-headers.html and also in http://people.apache.org/~cliffs/3party.html.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FELIX-147) Determine how to handle OSGi source
and classes for release
Posted by "Francesco Furfari (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FELIX-147?page=comments#action_12439681 ]
Francesco Furfari commented on FELIX-147:
-----------------------------------------
I've surfed alittle bit in some apache cvs :-).
Take a look at http://svn.apache.org/viewvc/ant/core/trunk/ , there are the licences of the redistribuited code as well as a Notice file amended with references of third-party copyright .
I suggest, like for the source file headers, to create another wiki page to keep track of these concerns for each subproject.
> Determine how to handle OSGi source and classes for release
> -----------------------------------------------------------
>
> Key: FELIX-147
> URL: http://issues.apache.org/jira/browse/FELIX-147
> Project: Felix
> Issue Type: Task
> Reporter: Richard S. Hall
> Priority: Blocker
> Fix For: 0.8.0
>
>
> We need to make sure we understand what we can and cannot do with the OSGi sources and/or class files. For example, can we include the OSGi source in our release...I assume we can include the OSGi binaries without any issue. This is a third-party issue, so we need to make sure that we understand what is necessary with respect to our NOTICE file, etc. Most of this is discussed in http://www.apache.org/legal/src-headers.html and also in http://people.apache.org/~cliffs/3party.html.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira