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.
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.
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
