Mailing-List: contact legal-discuss-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: legal-discuss@apache.org
Date: Mon, 18 Jul 2016 07:33:20 +0000 (UTC)
From: "Andreas Beeker (JIRA)" <jira@apache.org>
To: legal-discuss@apache.org
Message-ID: <JIRA.12990135.1468709156000.56411.1468827200459@Atlassian.JIRA>
In-Reply-To: <JIRA.12990135.1468709156000@Atlassian.JIRA>
References: <JIRA.12990135.1468709156000@Atlassian.JIRA> <JIRA.12990135.1468709156738@arcas>
Subject: [jira] [Commented] (LEGAL-264) Fork and distribute JAXB
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 18 Jul 2016 07:33:23 -0000


    [ https://issues.apache.org/jira/browse/LEGAL-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15381835#comment-15381835 ] 

Andreas Beeker commented on LEGAL-264:
--------------------------------------

We intent to fork the JAXB RI itself, because android doesn't allow packages under javax.*

CDDL and EPL are both listed under catagory B, so both seem to be not suitable for a fork. I have also looked at Moxy, but before putting even more work into it (which is not simply linking against a different library ...), I'd like to know a way to get an andoid version legally in.

So if your recommendation is EPL, I will try to adapt Moxy.

If ASF can't fork/host the custom JAXB version, we could fork it externally, but would need to include the binaries of that fork.


[5] http://www.apache.org/legal/resolved.html#category-b

> Fork and distribute JAXB
> ------------------------
>
>                 Key: LEGAL-264
>                 URL: https://issues.apache.org/jira/browse/LEGAL-264
>             Project: Legal Discuss
>          Issue Type: Question
>            Reporter: Andreas Beeker
>
> We would like (to try) to adapt JAXB ([1],[2]) to replace xmlbeans and to support android - this would be a substantial part of Apache POI.
> JAXB is dual licensed under GPL v2 and CDDL 1.1 [3]
> The process of adapting JAXB would include repacking a current version and changing the source [1] - after this modification the new library probably won't be changed until a new JAXB version appears. 
> So would it be possible to distribute a JAXB fork and link to it from an ASF project? [4]
> If yes, what would be the process to do so? (e.g. a new incubator project or simply another POI module? how are new versions handled?)
> [1] http://www.docx4java.org/blog/2012/05/jaxb-can-be-made-to-run-on-android/
> [2] http://apache-poi.1045710.n5.nabble.com/xmlbeans-successor-tt5722870.html
> [3] https://issues.apache.org/jira/browse/LEGAL-121
> [4] http://stackoverflow.com/questions/2388786/i-cant-distribute-jaxb-closed-code


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org