Hi all,

The first item to check is we can legally re-license the files to the
Apache license. I randomly looked at one file and it starts with "Copyright
(c) 2008 Standards for Technology in Automotive Retail and others."
followed by the Eclipse license.

The next tricky part is which branch to pick as the target, I would assume
it to be what we released 2.7.2 from.

Perhaps a good exercise would be to release 2.7.3 first. There are some
pending tickets w patches IIRC.

Gary



Gary

On Fri, Jan 22, 2021, 05:05 Mukul Gandhi <[email protected]> wrote:

> Hi all,
>     I've been thinking recently along following ideas.
>
> With the final goal to implement an XSLT 3.0 processor developed with java
> at Xalan, I wish to help start and implement XPath 3.1 at Xalan. For this,
> I wish to create a branch named xpath3_1 within Apache gitbox Xalan repos
> (if I'm unable, to do this myself I'll seek help on this list).
>
> I suggest that, we use the Eclipse webtools XPath 2.0 processor (
> https://git.eclipse.org/c/sourceediting/webtools.sourceediting.xpath.git/,
> branch R3_2_maintenance), as the codebase starting point, for our XPath 3.1
> processor (for this, I intend to import at this beginning, the XPath 2.0
> implementation codebase from eclipse webtools to apache gitbox Xalan within
> the "to be" created XalanJ branch xpath3_1). Sometime in near future, we
> should also probably reuse the Eclipse webtools XPath 2.0 tests code, as a
> base for our XPath 3.1 implementation test cases.
>
> If anyone has any objections or different thoughts, than above, please let
> us know.
>
>
>
> --
> Regards,
> Mukul Gandhi
>
>

Reply via email to