Skip to content
This repository was archived by the owner on May 28, 2018. It is now read-only.

Conversation

@Stephan202
Copy link
Contributor

The Maven POM allows one to specify multiple licenses. This is useful for dual (or triple) licensed projects such as Jersey. However, Jersey currently:

  • ...declares its licenses in a single <license> element, using the plus sign.
  • ...doesn't declare the version of the licenses used.

Both these things are inconvenient for users of the license-maven-plugin, as it doesn't allow one to "merge" the licenses with other uses of the CDDL 1.1 and/or GPLv2 with classpath exception.

The change proposed by this pull request distributes the license declaration over two <license> elements. (NB: If you accept this patch, note that the HK2 POMs should similarly be updated.)

@jerseyrobot
Copy link
Contributor

Can one of the admins verify this patch?

@shamoh
Copy link
Contributor

shamoh commented Apr 22, 2014

@Stephan202 Thanks for submitting the pull request. It make sense.

I would like to ask you to sign the Oracle Contributor Agreement before we can merge the request. See instructions at http://www.oracle.com/technetwork/community/oca-486395.html. Thanks a lot.

@Stephan202
Copy link
Contributor Author

@shamoh I downloaded, signed, scanned and emailed the OCA just now. Thanks for considering the pull request!

@Stephan202
Copy link
Contributor Author

I have received confirmation that the OCA has been approved, so I guess this is ready for merging :)

@mpotociar
Copy link
Collaborator

Hello Stephan,

I am very sorry, but after discussing this internally in the wide GlassFish developer forum, the decision is to keep the current license definition as is for the time being. As such, I'm closing the pull request without merging.

@mpotociar mpotociar closed this Jul 15, 2014
@Stephan202
Copy link
Contributor Author

@mpotociar, that's unfortunate but not the end of the world :)

If you don't mind me asking: which considerations led to this decision?

@mpotociar
Copy link
Collaborator

Sure:

  • Severity of the issue
  • The number of GlassFish related projects that would have to change for consistency reasons an associated effort required
  • Legal implications / effort necessary to obtain legal verification & approval for the change

Based on the criteria above, the decision has been made to keep the Jersey license definition unchanged and in sync with all other GlassFish-related open source projects, since the issue is not severe enough to justify the effort needed.

HTH.

@Stephan202
Copy link
Contributor Author

I'll delete the branch and forked repository, because at this time I have no further work to be merged. For future reference, the proposed change was the following:

diff --git a/pom.xml b/pom.xml
index 4c097b8..aa7fa54 100644
--- a/pom.xml
+++ b/pom.xml
@@ -160,8 +160,13 @@

     <licenses>
         <license>
-            <name>CDDL+GPL License</name>
-            <url>http://glassfish.java.net/public/CDDL+GPL_1_1.html</url>
+            <name>CDDL 1.1</name>
+            <url>https://jersey.java.net/license.html#cddl</url>
+            <distribution>repo</distribution>
+        </license>
+        <license>
+            <name>GPLv2 with classpath exception</name>
+            <url>https://jersey.java.net/license.html#gpl</url>
             <distribution>repo</distribution>
         </license>
     </licenses>

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants