maps, arrays and json support with xsl3
Hi all, I'm thinking to slowly begin and implement XPath 3.1 maps and arrays support (ref, https://www.w3.org/TR/xpath-31/#id-maps-and-arrays) and associated XPath 3.1 functions (ref, https://www.w3.org/TR/xpath-functions-31/#maps-and-arrays), into XalanJ's XSLT 3.0 dev branch. If anyone wishes to collaborate on this work effort, that shall be great. Any thoughts are welcome as well. -- Regards, Mukul Gandhi - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Commented] (XALANJ-2650) The pom file for xalan 2.7.3 and serializer 2.7.3 misses license (regression since 2.7.2)
[ https://issues.apache.org/jira/browse/XALANJ-2650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17821076#comment-17821076 ] Joseph Kessselman commented on XALANJ-2650: --- Hmmm. The maven-based build for the master branch copies in LICENSE.txt and NOTICE.txt, but does not copy in META-INF/services. As a maven novice, I'm not sure what the correct fix is. > The pom file for xalan 2.7.3 and serializer 2.7.3 misses license (regression > since 2.7.2) > - > > Key: XALANJ-2650 > URL: https://issues.apache.org/jira/browse/XALANJ-2650 > Project: XalanJ2 > Issue Type: Improvement > Security Level: No security risk; visible to anyone(Ordinary problems in > Xalan projects. Anybody can view the issue.) > Components: Xalan >Reporter: Vladimir Sitnikov >Assignee: Gary D. Gregory >Priority: Blocker > > See [https://repo1.maven.org/maven2/xalan/xalan/2.7.3/xalan-2.7.3.pom] > The tag is missing, and 2.7.3 does not refer to a parent pom. > --- > Please: > 1) Specify the license via tag > 2) Specify the license in the jar file (Bundle-License attribute in > META-INF/MANIFEST.MF), see > [https://docs.osgi.org/specification/osgi.core/7.0.0/framework.module.html#framework.module-bundle-license] > 3) Include license text as META-INF/LICENSE in the jar file. See > https://issues.apache.org/jira/browse/LEGAL-642 which clarifies each jar > should include a LICENSE file. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Commented] (XALANJ-2731) the xalan 2.7.3 is missing license info
[
https://issues.apache.org/jira/browse/XALANJ-2731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17821074#comment-17821074
]
Joseph Kessselman commented on XALANJ-2731:
---
Hmmm. The maven-based build for the master branch copies in LICENSE.txt and
NOTICE.txt, but does not copy in META-INF/services. As a maven novice, I'm not
sure what the correct fix is.
> the xalan 2.7.3 is missing license info
> ---
>
> Key: XALANJ-2731
> URL: https://issues.apache.org/jira/browse/XALANJ-2731
> Project: XalanJ2
> Issue Type: Bug
> Security Level: No security risk; visible to anyone(Ordinary problems in
> Xalan projects. Anybody can view the issue.)
>Affects Versions: 2.7.3
>Reporter: Samael Bate
>Priority: Major
>
> I use the license-maven-plugin with failOnMissing set to true but this is
> causing me an issue due to the Xalan jars not having license info defined:
> {noformat}
> There are 2 dependencies with no license :
> - xalan--serializer--2.7.3
> - xalan--xalan--2.7.3{noformat}
>
> I'm working around this be adding
> {code:java}
> xalan {code}
> please fix the missing license info and release a bugfix version
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional commands, e-mail: dev-h...@xalan.apache.org
