I had a look into the CXF archetype (for jaxws) and I think they have a good solution. The source files have the Apache license header in the properties file format (## prefix) which are filtered out in the generated files if we enable filtering (what we already did for most of the generated files) by executing the archetype. At the end, we have source files with the Apache license header (which is required) and without any license headers in the generated files (I think this is the solution we are looking for). And if we want, we could include a statement in the generated files like "generated by Apache Maven" or "generated by the Apache Camel camel-archetype-java plugin" or so like suggested by Lawrence Rosen. I will go ahead and update the archetypes today or tomorrow...
@Dan: Thanks for the hint. And by the the way, the jaxrs archetype doesn't have the Apache license header in its sources... ;-) Best, Christian On Thu, Jul 5, 2012 at 10:42 PM, Daniel Kulp <dk...@apache.org> wrote: > On Thursday, July 05, 2012 12:29:48 PM Claus Ibsen wrote: > > On Wed, Jul 4, 2012 at 11:05 AM, Guillaume Nodet <gno...@gmail.com> > wrote: > > > There's a mailing list specific for legal matters, there's no need to > > > get > > > the board involved with that. > > > We should rather look for archives in legal-disc...@apache.org and in > > > the > > > jira https://issues.apache.org/jira/browse/LEGAL > > > and if we can't find anything, raise a JIRA issue there. > > > My guts feeling is that is has already been discussed somewhere. > > > > Yeah it must have. > > > > Because basically all the existing Apache products that have Maven > > Archetypes I have tried, generate source code with *NO* license > > headers. > > > > For example from Karaf, Maven, CXF etc. > > > > You can just try using mvn archetype:generate, and chose any of the > > Apache Project archetypes such as for example: > > org.apache.cxf.archetype:cxf-jaxrs-service > > Had a similar discussion as part of: > > https://issues.apache.org/jira/browse/CXF-4375 > > about removing the license header things. > > In anycase, I'm +1 to removing the header from the generated code, but -1 > to > removing them from the initial templates. > > Dan > > > > > > > > On Wed, Jul 4, 2012 at 10:39 AM, Christian Schneider < > > > > > > ch...@die-schneider.net> wrote: > > >> So my proposal is that I organize a statement from the board before > our > > >> next release and we already remove the license headers. > > >> In the worst case I think we have to add a license file to the > > >> generated > > >> code and in the best case we are fine. > > >> > > >> Christian > > >> > > >> Am 04.07.2012 10:30, schrieb Christian Schneider: > > >> This is already a good tendency that generated code is unproblematic. > > >> To > > >> > > >>> make sure I propose we get a statement from the board then we are on > > >>> the > > >>> safe side. > > >>> Perhaps this can then also be written down so other projects can > > >>> simply > > >>> follow. > > >>> > > >>> Christian > > >>> > > >>> Am 04.07.2012 10:24, schrieb Rob Davies: > > >>>> I think this thread is helpful - its from Eclipse - > > >>>> http://www.eclipsezone.com/**eclipse/forums/t116081.html< > http://www.e > > >>>> clipsezone.com/eclipse/forums/t116081.html>>>>> > > >>>> On 4 Jul 2012, at 09:19, Christian Schneider wrote: > > >>>> My current understanding is that you can not assume you are allowed > > >>>> to > > >>>> > > >>>>> use code if it has no license. Is there an exception for > > >>>>> generated/template code? > > >>>>> If yes then I am supporting this but we should make sure this works > > >>>>> legally. Can we get some confirmation about this from some license > > >>>>> specialist from apache or is this written down somehere already? > > >>>>> > > >>>>> Christian > > >>>>> > > >>>>> Am 04.07.2012 10:12, schrieb Guillaume Nodet: > > >>>>>> Generated code should not be licensed or copyrighted. It's up to > > >>>>>> the > > >>>>>> user > > >>>>>> to decide which license to use. > > >>>>>> So +1 for removing any header from generated code. > > >>>>>> > > >>>>>> On Wed, Jul 4, 2012 at 8:33 AM, Claus Ibsen < > claus.ib...@gmail.com> > > >>>>>> > > >>>>>> wrote: > > >>>>>> Hi > > >>>>>> > > >>>>>>> When end users of Camel uses the Camel Maven Archetypes to create > > >>>>>>> new > > >>>>>>> projects > > >>>>>>> http://camel.apache.org/camel-**maven-archetypes.html< > http://camel > > >>>>>>> .apache.org/camel-maven-archetypes.html> > > >>>>>>> > > >>>>>>> Then we generate a new skeleton Maven project for them. > > >>>>>>> > > >>>>>>> Currently these *generated* source files contains ASF license > > >>>>>>> headers. > > >>>>>>> > > >>>>>>> I want to discuss if we should remove these ASF headers from the > > >>>>>>> *generated* files. > > >>>>>>> Our end users works in organization that build software, and they > > >>>>>>> may > > >>>>>>> not use any license headers, > > >>>>>>> or use their own license headers, or use another kind of header. > > >>>>>>> > > >>>>>>> I think we should not include any license headers at all, and > > >>>>>>> leave it > > >>>>>>> for the end users to decide for that. > > >>>>>>> > > >>>>>>> Any thoughts? > > >>>>>>> > > >>>>>>> > > >>>>>>> -- > > >>>>>>> Claus Ibsen > > >>>>>>> ----------------- > > >>>>>>> FuseSource > > >>>>>>> Email: cib...@fusesource.com > > >>>>>>> Web: http://fusesource.com > > >>>>>>> Twitter: davsclaus, fusenews > > >>>>>>> Blog: http://davsclaus.com > > >>>>>>> Author of Camel in Action: http://www.manning.com/ibsen > > >>>>> > > >>>>> -- > > >>>>> Christian Schneider > > >>>>> http://www.liquid-reality.de > > >>>>> > > >>>>> Open Source Architect > > >>>>> Talend Application Integration Division http://www.talend.com > > >> > > >> -- > > >> Christian Schneider > > >> http://www.liquid-reality.de > > >> > > >> Open Source Architect > > >> Talend Application Integration Division http://www.talend.com > > > > > > -- > > > ------------------------ > > > Guillaume Nodet > > > ------------------------ > > > Blog: http://gnodet.blogspot.com/ > > > ------------------------ > > > FuseSource, Integration everywhere > > > http://fusesource.com > -- > Daniel Kulp > dk...@apache.org - http://dankulp.com/blog > Talend Community Coder - http://coders.talend.com >
