[ 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
