[JBoss JIRA] Created: (JBBUILD-690) The JBoss parent pom should be dual licenced under LGPL and ASL (not just LGPL)
8:28 a.m.
The JBoss parent pom should be dual licenced under LGPL and ASL (not just LGPL)
-------------------------------------------------------------------------------
Key: JBBUILD-690
URL: https://issues.jboss.org/browse/JBBUILD-690
Project: JBoss Build System
Issue Type: Bug
Components: JBoss Parent POM
Affects Versions: JBoss Parent POM - 6
Reporter: Geoffrey De Smet
Assignee: Paul Gier
Fix For: JBoss Parent POM - 6
Drools and jBPM are ASL licensed and therefor can't really depend on LGPL licensed
software :(
That includes the parent poms, so the jboss-parent can't be only LGPL licensed.
Option 1: Add the ASL license to make it dual licensed under LGPL and ASL:
{code}
<license>
<name>The Apache Software License, Version 2.0</name>
<url>http://www.apache.org/licenses/LICENSE-2.0.txt</url>
<distribution>repo</distribution>
</license>
{code}
Note: a pom that inherits from the jboss-parent pom and specifies a license, only has
it's own license (try yourself with "mvn help:effective-pom".
Option 2: Only use an ASL license, because LGPL can use ASL (and not the other way
around).
Option 3: Only use a BSD license, because LGPL and ASL can use that.
Note: you need to specify a license so <distribution>repo</distribution> can
be set.
Seperate issue: add <distribution>repo</distribution> to whichever licence it
uses.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:47 a.m.
New subject: [JBoss JIRA] Updated: (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 updated JBBUILD-690:
------------------------------
Fix Version/s: JBoss Parent POM - 7
(was: JBoss Parent POM - 6)
The JBoss parent pom should be dual licenced under LGPL and ASL (not
just LGPL)
-------------------------------------------------------------------------------
Key: JBBUILD-690
URL: https://issues.jboss.org/browse/JBBUILD-690
Project: JBoss Build System
Issue Type: Bug
Components: JBoss Parent POM
Affects Versions: JBoss Parent POM - 6
Reporter: Geoffrey De Smet
Assignee: Paul Gier
Fix For: JBoss Parent POM - 7
Drools and jBPM are ASL licensed and therefor can't really depend on LGPL licensed
software :(
That includes the parent poms, so the jboss-parent can't be only LGPL licensed.
Option 1: Add the ASL license to make it dual licensed under LGPL and ASL:
{code}
<license>
<name>The Apache Software License, Version 2.0</name>
<url>http://www.apache.org/licenses/LICENSE-2.0.txt</url>
<distribution>repo</distribution>
</license>
{code}
Note: a pom that inherits from the jboss-parent pom and specifies a license, only has
it's own license (try yourself with "mvn help:effective-pom".
Option 2: Only use an ASL license, because LGPL can use ASL (and not the other way
around).
Option 3: Only use a BSD license, because LGPL and ASL can use that.
Note: you need to specify a license so <distribution>repo</distribution> can
be set.
Seperate issue: add <distribution>repo</distribution> to whichever licence it
uses.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:24 p.m.
New subject: [JBoss JIRA] Commented: (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 commented on JBBUILD-690:
-----------------------------------
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.
The JBoss parent pom should be dual licenced under LGPL and ASL (not
just LGPL)
-------------------------------------------------------------------------------
Key: JBBUILD-690
URL: https://issues.jboss.org/browse/JBBUILD-690
Project: JBoss Build System
Issue Type: Bug
Components: JBoss Parent POM
Affects Versions: JBoss Parent POM - 6
Reporter: Geoffrey De Smet
Assignee: Paul Gier
Fix For: JBoss Parent POM - 7
Drools and jBPM are ASL licensed and therefor can't really depend on LGPL licensed
software :(
That includes the parent poms, so the jboss-parent can't be only LGPL licensed.
Option 1: Add the ASL license to make it dual licensed under LGPL and ASL:
{code}
<license>
<name>The Apache Software License, Version 2.0</name>
<url>http://www.apache.org/licenses/LICENSE-2.0.txt</url>
<distribution>repo</distribution>
</license>
{code}
Note: a pom that inherits from the jboss-parent pom and specifies a license, only has
it's own license (try yourself with "mvn help:effective-pom".
Option 2: Only use an ASL license, because LGPL can use ASL (and not the other way
around).
Option 3: Only use a BSD license, because LGPL and ASL can use that.
Note: you need to specify a license so <distribution>repo</distribution> can
be set.
Seperate issue: add <distribution>repo</distribution> to whichever licence it
uses.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:24 p.m.
New subject: [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.
The JBoss parent pom should be dual licenced under LGPL and ASL (not
just LGPL)
-------------------------------------------------------------------------------
Key: JBBUILD-690
URL: https://issues.jboss.org/browse/JBBUILD-690
Project: JBoss Build System
Issue Type: Bug
Components: JBoss Parent POM
Affects Versions: JBoss Parent POM - 6
Reporter: Geoffrey De Smet
Assignee: Paul Gier
Fix For: JBoss Parent POM - 7
Drools and jBPM are ASL licensed and therefor can't really depend on LGPL licensed
software :(
That includes the parent poms, so the jboss-parent can't be only LGPL licensed.
Option 1: Add the ASL license to make it dual licensed under LGPL and ASL:
{code}
<license>
<name>The Apache Software License, Version 2.0</name>
<url>http://www.apache.org/licenses/LICENSE-2.0.txt</url>
<distribution>repo</distribution>
</license>
{code}
Note: a pom that inherits from the jboss-parent pom and specifies a license, only has
it's own license (try yourself with "mvn help:effective-pom".
Option 2: Only use an ASL license, because LGPL can use ASL (and not the other way
around).
Option 3: Only use a BSD license, because LGPL and ASL can use that.
Note: you need to specify a license so <distribution>repo</distribution> can
be set.
Seperate issue: add <distribution>repo</distribution> to whichever licence it
uses.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:28 p.m.
New subject: [JBoss JIRA] Closed: (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 closed JBBUILD-690.
-----------------------------
Resolution: Done
Fixed in
[def528d|https://github.com/jboss/jboss-parent-pom/commit/def528d9b17796e3...]
The JBoss parent pom should be dual licenced under LGPL and ASL (not
just LGPL)
-------------------------------------------------------------------------------
Key: JBBUILD-690
URL: https://issues.jboss.org/browse/JBBUILD-690
Project: JBoss Build System
Issue Type: Bug
Components: JBoss Parent POM
Affects Versions: JBoss Parent POM - 6
Reporter: Geoffrey De Smet
Assignee: Paul Gier
Fix For: JBoss Parent POM - 7
Drools and jBPM are ASL licensed and therefor can't really depend on LGPL licensed
software :(
That includes the parent poms, so the jboss-parent can't be only LGPL licensed.
Option 1: Add the ASL license to make it dual licensed under LGPL and ASL:
{code}
<license>
<name>The Apache Software License, Version 2.0</name>
<url>http://www.apache.org/licenses/LICENSE-2.0.txt</url>
<distribution>repo</distribution>
</license>
{code}
Note: a pom that inherits from the jboss-parent pom and specifies a license, only has
it's own license (try yourself with "mvn help:effective-pom".
Option 2: Only use an ASL license, because LGPL can use ASL (and not the other way
around).
Option 3: Only use a BSD license, because LGPL and ASL can use that.
Note: you need to specify a license so <distribution>repo</distribution> can
be set.
Seperate issue: add <distribution>repo</distribution> to whichever licence it
uses.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5473
days inactive
5480
days old
4 comments
2 participants
participants (2)
-
Geoffrey De Smet (JIRA) -
Paul Gier (JIRA)