[jboss-jira] [JBoss JIRA] Issue Comment Edited: (JBBUILD-690) The JBoss parent pom should be dual licenced under LGPL and ASL (not just LGPL)

[ https://issues.jboss.org/browse/JBBUILD-690?page=com.atlassian.jira.plugi... ] Paul Gier edited comment on JBBUILD-690 at 8/3/11 3:23 PM: ----------------------------------------------------------- Here is a summary of the discussion with legal: The license header (XML comments) is not necessary in the POM because the POM is likely not copyrightable or has only a weak copyright. The license configuration in the POM is used both for information about the license of the current project, and as a default license for any projects which inherit from this POM. This causes a concern that the license of the parent itself may not be the correct default for JBoss projects. Changing the license of the jboss-parent (options 1, 2, and 3) does not completely solve the problem that projects which consume this POM may have incompatible licenses. Therefore, it was decided to change the jboss-parent to public domain (no copyright). This solves the problem of license concerns for projects which use the jboss-parent. However, there is still a concern that some JBoss projects which inherit from the jboss-parent will accidentally forget to override this configuration and cause some project reports to show "public domain" as the license. These cases should be handled by the license file included with the software, and the source file headers to show that these projects are not actually public domain. was (Author: pgier): Here is a summary of the discussion with legal. The license header (XML comments) is not necessary in the POM because the POM is likely not copyrightable or has only a weak copyright. The license configuration in the POM is used both for information about the license of the current project, and as a default license for any projects which inherit from this POM. This causes a concern that the license of the parent itself may not be the correct default for JBoss projects. Changing the license of the jboss-parent does not completely solve the problem that projects which consume this POM may have incompatible licenses. Therefore, it was decided to change the jboss-parent to public domain (no copyright). This solves the problem of license concerns for projects which use the jboss-parent. However, there is still a concern that some JBoss projects which inherit from the jboss-parent will accidentally forget to override this configuration and cause some project reports to show "public domain" as the license. These cases should be handled by the license file included with the software, and the source file headers to show that these projects are not actually public domain. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira