My intention was to get Jena JDBC in this release.
The what's being distributed thing with the whole Apache L&N stuff is always an incomprehensible minefield IMO. Yes we are not distributing the source or even the binary but an end user requires AspectJ in order to compile the source which we release (which is done automatically via maven). If the dependency is compile time only then are the L&N entries actually unnecessary? Rob On 8/26/13 1:54 PM, "Andy Seaborne" <[email protected]> wrote: >On 26/08/13 21:23, Rob Vesse wrote: >> Ok I will copy the NOTICE and LICENSE into each module since they will >>be >> identical. >> >> I believe it is used for all the modules >> >> I found this thread re: AspectJ and an Apache project >> >> >>http://mail-archives.apache.org/mod_mbox/geronimo-dev/200710.mbox/%3C3604 >>FF >> [email protected]%3E >> >> And I quote: >> >>> The NOTICE file needs to inform users how to obtain aspectj source >>> code (this is a provision of the EPL). Typically this is >>> accomplished with a url to the project web site. > >The key factor is whether we distribute (source|binary) - EPL section 3. > As I understand the plan, we're not going in at this release. (If >it's in apache-jena then we are.) > >> >> >> Btw I found another thread that noted that Marmotta has some EPL >> dependencies so what do those guys do? > >Do they? > >https://git-wip-us.apache.org/repos/asf?p=incubator-marmotta.git;a=blob_pl >ain;f=NOTICE.txt;h=22f8d892a175ec28535480c75465323a19dc752d;hb=HEAD > >it's long because of all the javascript, and javascript is being shipped >as source code. > > Andy > >> Rob >> >> >> On 8/26/13 1:04 PM, "Andy Seaborne" <[email protected]> wrote: >> >>> On 26/08/13 19:08, Rob Vesse wrote: >>>> Response inlines: >>>> >>>> >>>> >>>> On 8/24/13 9:00 AM, "Andy Seaborne" <[email protected]> wrote: >>>> >>>>> Rob, >>>>> >>>>> There'll need to be NOTICE and LICENSE files in the modules. >>>> >>>> I have added these to the top level module, do they need to be in each >>>> sub-module? >>> >>> If the N&L files are in place, the build puts them in the jar as well >>>so >>> it helps to have them in each place. >>> >>> Is AspectJ used in all modules? >>> >>> (Clerezza doesn't seem to have any NOTICE files at all - I don't >>> undertand how that can be.) >>> >>>> >>>> They are identical throughout, I assume we don't need to include >>>> acknowledgements to ourselves in a NOTICE file since obviously the >>>> modules >>>> depend on other Jena modules. >>> >>> Yes. >>> >>>> >>>> There are no new runtime third party dependencies introduced, the >>>> modules >>>> depend only on other Jena modules, JUnit and Log4j >>>> >>>> >>>>> >>>>> Are the NOTICE and LICENSE that end up in the jars correct? >>>> >>>> Currently I'm not sure these end up in the JARs at all, I'll look into >>>> this. How do other modules achieve this? >>> >>> IIRC N&L go into the jar by maven. (No - I don't know how!) >>> >>>>> How does aspectj work? Does it cause anything to be shipped in the >>>>> jar(s)? >>>> >>>> AspectJ basically inserts additional code into the class files at >>>> compile >>>> time - essentially it is a code injection mechanism. This is used >>>>only >>>> to >>>> add TRACE level method entry and exit logging which is useful when >>>> debugging the use of the drivers with a new tool. Thus it is a >>>>compile >>>> time only dependency. >>>> >>>> However AspectJ is licensed under the Eclipse Public License which is >>>> Category B at Apache so I presume we need to add an entry to the >>>>NOTICE >>>> file for this and append the EPL to the License file? >>> >>> Does AspectJ make any statement as to the License on the modified >>> compiled output? >>> >>> No ... >>> http://eclipse.org/aspectj/doc/released/faq.php#q:license >>> >>> <opinion>We do not absolutely require to include a statement because we >>> do not include source material. >>> >>> If this is going to the distribution, then something needs to be in >>>that >>> NOTICE (not the module one). >>> >>> However, it is something the end user (rebuilder) may wish to be aware >>> of rebuilding from source and so, on balance, I'd put the statement in. >>> </opinion> >>> >>> As a general comment - a seep through all the N&L to check and update >>>to >>> current Apache practice would be good. There not so much "rules" as >>> "principles and practice". If we had an DEPENDENCES file we could use >>> that as a "long form" NOTICE area. >>> >>> Andy >>> >>>> >>>> Rob >>>> >>>>> >>>>> And since you've been through this more recently than anyone else, >>>>>any >>>>> experience (e.g. plugins) we can learn and roll back into the other >>>>> build stuff? >>>>> >>>>> Andy >>>> >>> >> >
