On Wed, Jul 4, 2012 at 9:14 AM, Christian Schneider <[email protected]> wrote: > Basically I agree that we should not have Apache License headers as people > will have to manually remove them. > On the other hand it is important that we have a license for the code the > archetype generates. Without > a license people might be insecure what they may do with the code. >
Frankly I that the current situation is worse, as the generated code is licensed to ASF by one of the contributor agreements. And the person generated that code is very very likely not already an ASF contributor. And the source code is not intended to be contributed to ASF and included in the ASF organization, eg in any of the ASF projects. Instead the person want to use the generated code as a base for a new project. And therefore he/she would in a better position if there was NO licenses generated at all. Then its 100% clean. Otherwise that person most likely need to remove the licenses to make it comply with his organization. Any why do you think its important that generated code from a maven tooling *must* have licenses. The tool is for end users to create new projects, and to make their life easier. Not harder / more confusing / annoying. What they do with the code is their business. We should just be happy that there is a demand for this tool, and we should make the lives of our end users easier. > I think the Apache license might still be ok for the archetypes but we could > simply put it in the base dir of the generated code. > Other ASF projects do *NOT* include license headers. For example I tried the Karaf 2.2.8 commands You can try it by mvn archetype:generate and in the interactive mode type: karaf ENTER And select this archetype and version karaf-blueprint-archetype:2.2.8 And you get a new project generated that is 100% license header free. That is good for end users. > Christian > > Am 04.07.2012 08:33, schrieb Claus Ibsen: > >> Hi >> >> When end users of Camel uses the Camel Maven Archetypes to create new >> projects >> 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? >> >> > > > -- > Christian Schneider > http://www.liquid-reality.de > > Open Source Architect > Talend Application Integration Division http://www.talend.com > -- Claus Ibsen ----------------- FuseSource Email: [email protected] Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
