[
https://issues.apache.org/jira/browse/XALANJ-2823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18042994#comment-18042994
]
Samael Bate edited comment on XALANJ-2823 at 12/5/25 7:45 AM:
--------------------------------------------------------------
Thanks, I have no desire/need to setup Eclipse as I don't use it. I just
assumed that's your IDE as xpath31_types has no ant/maven/gradle build but does
have .classpath and .project files in the root.
I just want to confirm how the missing classes are being added. It seems that I
was right about needing to build xalan-java-3.0.1-SNAPSHOT.jar and adding it to
classpath for xpath31_types.
This does potentially cause an issue when it's eventually time to build release
jars though. With both projects depending on each other, which one will be
released first?
I don't know if there is a license issue with EPL code being in the xalan repo
but it would certainly make things easier and with the later being a maven
project, it's dependencies will need to be available in maven central when it's
time to publish jars. So xpath31_types being another repo without maven
releases is likely to become more of a problem.
{_}edit{_}: I've setup a maven project now for xpath31_types that's working
fairly well for my local development and makes it easier to test the processor
types. Once I've got some more tests in place I'll create a PR for it
was (Author: singingbush):
Thanks, I have no desire/need to setup Eclipse as I don't use it. I just
assumed that's your IDE as xpath31_types has no ant/maven/gradle build but does
have .classpath and .project files in the root.
I just want to confirm how the missing classes are being added. It seems that I
was right about needing to build xalan-java-3.0.1-SNAPSHOT.jar and adding it to
classpath for xpath31_types.
This does potentially cause an issue when it's eventually time to build release
jars though. With both projects depending on each other, which one will be
released first?
I don't know if there is a license issue with EPL code being in the xalan repo
but it would certainly make things easier and with the later being a maven
project, it's dependencies will need to be available in maven central when it's
time to publish jars. So xpath31_types being another repo without maven
releases is likely to become more of a problem.
> implementation of xpath 3.1 partial function applications
> ---------------------------------------------------------
>
> Key: XALANJ-2823
> URL: https://issues.apache.org/jira/browse/XALANJ-2823
> Project: XalanJ2
> Issue Type: Task
> Security Level: No security risk; visible to anyone(Ordinary problems in
> Xalan projects. Anybody can view the issue.)
> Reporter: Mukul Gandhi
> Assignee: Mukul Gandhi
> Priority: Major
>
> I'm creating this jira issue to track, implementation of XPath 3.1 partial
> function applications within Xalan-J's XSLT 3.0 dev repos branch.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
