[
https://issues.apache.org/jira/browse/AMQ-9005?focusedWorklogId=798303&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-798303
]
ASF GitHub Bot logged work on AMQ-9005:
---------------------------------------
Author: ASF GitHub Bot
Created on: 05/Aug/22 07:34
Start Date: 05/Aug/22 07:34
Worklog Time Spent: 10m
Work Description: jbonofre commented on PR #871:
URL: https://github.com/apache/activemq/pull/871#issuecomment-1206140169
Yes. It's pretty easy: create a new commit with git commit --allow-empty and
then rebase and squash. Then you can force push, it will trigger a new Jenkins
execution.
Issue Time Tracking
-------------------
Worklog Id: (was: 798303)
Time Spent: 1h 50m (was: 1h 40m)
> remove xalan dependency due to it being end of life
> ---------------------------------------------------
>
> Key: AMQ-9005
> URL: https://issues.apache.org/jira/browse/AMQ-9005
> Project: ActiveMQ
> Issue Type: Improvement
> Reporter: PJ Fanning
> Priority: Major
> Fix For: 5.18.0, 5.17.2
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> Xalan is no longer supported.
> https://lists.apache.org/thread/s8kjny5270ssfcp46v0fl39lk98987w7
> It is better to use JAXP TransformerFactory than using xalan directly. If you
> add xalan dependency just to ensure that you have a JAXP compliant
> transformer on the classpath, this is unnecessary - the Java runtime has a
> built-in implementation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
