You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by "Joe Kesselman (Jira)" <ji...@apache.org> on 2024/01/10 22:28:00 UTC
[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&focusedCommentId=17805311#comment-17805311 ]
Joe Kesselman commented on XALANJ-2650:
---------------------------------------
Maven build adds the missing files. But yes, we might want to back-patch the 2.7.3 ant build too.
> 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 <license> tag is missing, and 2.7.3 does not refer to a parent pom.
> ---
> Please:
> 1) Specify the license via <license> 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-unsubscribe@xalan.apache.org
For additional commands, e-mail: dev-help@xalan.apache.org