[
https://issues.apache.org/jira/browse/XALANJ-2790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17898598#comment-17898598
]
Mukul Gandhi commented on XALANJ-2790:
--------------------------------------
[~singingbush] Xalan-J's XSL 3 development code is available on branch
xalan-j_xslt3.0, and that is not backward compatible with XSLT 1.0 spec. The
master branch has XSLT 1.0 implementation.
> create branch for migrating XSL 3 ant build to maven
> ----------------------------------------------------
>
> Key: XALANJ-2790
> URL: https://issues.apache.org/jira/browse/XALANJ-2790
> Project: XalanJ2
> Issue Type: New Feature
> Security Level: No security risk; visible to anyone(Ordinary problems in
> Xalan projects. Anybody can view the issue.)
> Components: Build, Xalan
> Affects Versions: The Latest Development Code
> Reporter: Mukul Gandhi
> Priority: Major
>
> There's a consensus within Xalan-J team to port from Ant build to Maven. This
> has already been done for Xalan-J XSLT 1.0 master branch. The same needs to
> be done on branch xalan-j_xslt3.0 as well.
> I think, a good way to do this is to create a new branch from the branch
> xalan-j_xslt3.0, and then doing Maven migration on that new XSL 3 code
> branch. Parallelly, any new XSL 3 changes to code may be done on branch
> xalan-j_xslt3.0 with an existing Ant build, allowing quicker resolutions to
> Xalan-J's XSL 3 implementation issues till the time the new XSL 3 Maven
> branch gets stable.
> I'm creating this jira issue, to track creating a new Xalan-J XSL 3 Maven
> branch.
--
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
