[jira] [Work logged] (AMQ-9005) remove xalan dependency due to it being end of life
[ https://issues.apache.org/jira/browse/AMQ-9005?focusedWorklogId=800192=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-800192 ] ASF GitHub Bot logged work on AMQ-9005: --- Author: ASF GitHub Bot Created on: 12/Aug/22 06:10 Start Date: 12/Aug/22 06:10 Worklog Time Spent: 10m Work Description: lucastetreault commented on PR #871: URL: https://github.com/apache/activemq/pull/871#issuecomment-1212762736 Thanks JB! Issue Time Tracking --- Worklog Id: (was: 800192) Time Spent: 2h 20m (was: 2h 10m) > 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 >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.18.0, 5.17.2 > > Time Spent: 2h 20m > 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)
[jira] [Work logged] (AMQ-9005) remove xalan dependency due to it being end of life
[ https://issues.apache.org/jira/browse/AMQ-9005?focusedWorklogId=800189=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-800189 ] ASF GitHub Bot logged work on AMQ-9005: --- Author: ASF GitHub Bot Created on: 12/Aug/22 06:06 Start Date: 12/Aug/22 06:06 Worklog Time Spent: 10m Work Description: jbonofre closed pull request #873: [AMQ-9005] Remove resin-web.xml conf example URL: https://github.com/apache/activemq/pull/873 Issue Time Tracking --- Worklog Id: (was: 800189) Time Spent: 2h (was: 1h 50m) > 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 >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.18.0, 5.17.2 > > Time Spent: 2h > 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)
[jira] [Work logged] (AMQ-9005) remove xalan dependency due to it being end of life
[ https://issues.apache.org/jira/browse/AMQ-9005?focusedWorklogId=800191=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-800191 ] ASF GitHub Bot logged work on AMQ-9005: --- Author: ASF GitHub Bot Created on: 12/Aug/22 06:06 Start Date: 12/Aug/22 06:06 Worklog Time Spent: 10m Work Description: jbonofre merged PR #871: URL: https://github.com/apache/activemq/pull/871 Issue Time Tracking --- Worklog Id: (was: 800191) Time Spent: 2h 10m (was: 2h) > 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 >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.18.0, 5.17.2 > > Time Spent: 2h 10m > 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)
[jira] [Work logged] (AMQ-9005) remove xalan dependency due to it being end of life
[ https://issues.apache.org/jira/browse/AMQ-9005?focusedWorklogId=798303=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)
[jira] [Work logged] (AMQ-9005) remove xalan dependency due to it being end of life
[ https://issues.apache.org/jira/browse/AMQ-9005?focusedWorklogId=798300=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-798300 ] ASF GitHub Bot logged work on AMQ-9005: --- Author: ASF GitHub Bot Created on: 05/Aug/22 07:30 Start Date: 05/Aug/22 07:30 Worklog Time Spent: 10m Work Description: lucastetreault commented on PR #871: URL: https://github.com/apache/activemq/pull/871#issuecomment-1206137075 @jbonofre is there a way I can re-initiate the tests? Everything passed for me: ``` [INFO] [INFO] Reactor Summary for ActiveMQ 5.18.0-SNAPSHOT: [INFO] [INFO] ActiveMQ ... SUCCESS [ 0.481 s] [INFO] ActiveMQ :: Openwire Generator . SUCCESS [ 0.334 s] [INFO] ActiveMQ :: Client . SUCCESS [01:04 min] [INFO] ActiveMQ :: Openwire Legacy Support SUCCESS [ 0.103 s] [INFO] ActiveMQ :: JAAS ... SUCCESS [ 13.006 s] [INFO] ActiveMQ :: Broker . SUCCESS [ 49.482 s] [INFO] ActiveMQ :: KahaDB Store ... SUCCESS [02:45 min] [INFO] ActiveMQ :: STOMP Protocol . SUCCESS [10:06 min] [INFO] ActiveMQ :: MQTT Protocol .. SUCCESS [17:06 min] [INFO] ActiveMQ :: JDBC Store . SUCCESS [ 4.500 s] [INFO] ActiveMQ :: Generic JMS Pool ... SUCCESS [ 36.790 s] [INFO] ActiveMQ :: Pool ... SUCCESS [ 3.421 s] [INFO] ActiveMQ :: RA . SUCCESS [01:31 min] [INFO] ActiveMQ :: Spring . SUCCESS [ 54.835 s] [INFO] ActiveMQ :: Console SUCCESS [ 4.809 s] [INFO] ActiveMQ :: Partition Management ... SUCCESS [ 16.057 s] [INFO] ActiveMQ :: Runtime Configuration .. SUCCESS [07:57 min] [INFO] ActiveMQ :: Tooling SUCCESS [ 0.009 s] [INFO] ActiveMQ :: JUnit Rule . SUCCESS [ 1.965 s] [INFO] ActiveMQ :: Unit Tests . SUCCESS [ 02:06 h] [INFO] ActiveMQ :: HTTP Protocol Support .. SUCCESS [09:07 min] [INFO] ActiveMQ :: AMQP ... SUCCESS [05:05 min] [INFO] ActiveMQ :: All JAR bundle . SUCCESS [ 0.213 s] [INFO] ActiveMQ :: Log4j Appender . SUCCESS [ 0.138 s] [INFO] ActiveMQ :: Apache Karaf ... SUCCESS [ 0.901 s] [INFO] ActiveMQ :: ConnectionFactory .. SUCCESS [ 0.058 s] [INFO] ActiveMQ :: RAR SUCCESS [ 1.941 s] [INFO] ActiveMQ :: Run Jar SUCCESS [ 0.093 s] [INFO] ActiveMQ :: Shiro .. SUCCESS [ 2.049 s] [INFO] ActiveMQ :: Memory Usage Test Plugin ... SUCCESS [ 1.381 s] [INFO] ActiveMQ :: Performance Test Plugin SUCCESS [ 5.114 s] [INFO] ActiveMQ :: StartUp/Stop Plugin SUCCESS [ 3.505 s] [INFO] ActiveMQ :: Web SUCCESS [ 13.664 s] [INFO] ActiveMQ :: OSGi bundle SUCCESS [ 0.812 s] [INFO] ActiveMQ :: Blueprint .. SUCCESS [ 0.042 s] [INFO] ActiveMQ :: Web Demo ... SUCCESS [ 24.623 s] [INFO] ActiveMQ :: Web Console SUCCESS [ 4.367 s] [INFO] ActiveMQ :: Karaf Integration Tests SUCCESS [ 1.081 s] [INFO] ActiveMQ :: Assembly ... SUCCESS [ 24.476 s] [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 03:05 h [INFO] Finished at: 2022-08-03T09:44:54Z [INFO] ``` Issue Time Tracking --- Worklog Id: (was: 798300) Time Spent: 1h 40m (was: 1.5h) > 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 40m > Remaining Estimate: 0h > > Xalan is no longer
[jira] [Work logged] (AMQ-9005) remove xalan dependency due to it being end of life
[ https://issues.apache.org/jira/browse/AMQ-9005?focusedWorklogId=796962=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-796962 ] ASF GitHub Bot logged work on AMQ-9005: --- Author: ASF GitHub Bot Created on: 01/Aug/22 17:05 Start Date: 01/Aug/22 17:05 Worklog Time Spent: 10m Work Description: lucastetreault opened a new pull request, #871: URL: https://github.com/apache/activemq/pull/871 As per discussion here: https://github.com/apache/activemq/pull/870 Issue Time Tracking --- Worklog Id: (was: 796962) Time Spent: 1.5h (was: 1h 20m) > 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: 1.5h > 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)
[jira] [Work logged] (AMQ-9005) remove xalan dependency due to it being end of life
[ https://issues.apache.org/jira/browse/AMQ-9005?focusedWorklogId=796961=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-796961 ] ASF GitHub Bot logged work on AMQ-9005: --- Author: ASF GitHub Bot Created on: 01/Aug/22 17:04 Start Date: 01/Aug/22 17:04 Worklog Time Spent: 10m Work Description: lucastetreault commented on PR #870: URL: https://github.com/apache/activemq/pull/870#issuecomment-1201473992 I'll open another PR but I'll need input on how to test the resin-web.xml change :) Issue Time Tracking --- Worklog Id: (was: 796961) Time Spent: 1h 20m (was: 1h 10m) > 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 20m > 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)
[jira] [Work logged] (AMQ-9005) remove xalan dependency due to it being end of life
[ https://issues.apache.org/jira/browse/AMQ-9005?focusedWorklogId=796959=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-796959 ] ASF GitHub Bot logged work on AMQ-9005: --- Author: ASF GitHub Bot Created on: 01/Aug/22 17:01 Start Date: 01/Aug/22 17:01 Worklog Time Spent: 10m Work Description: lucastetreault commented on PR #870: URL: https://github.com/apache/activemq/pull/870#issuecomment-1201470213 > Other xalan references need to be cleaned up and XPath unit tests validated > > ./activemq-client/src/main/java/org/apache/activemq/filter/XPathExpression.java ./activemq-broker/src/main/java/org/apache/activemq/filter/XalanXPathEvaluator.java So I'm not entirely sure what to do with these... activemq-broker/src/main/java/org/apache/activemq/filter/XalanXPathEvaluator is actually identical to activemq-broker/src/main/java/org/apache/activemq/filter/JAXPXPathEvaluator and neither of them use Xalan. I guess we can delete XalanXPathEvaluator and change the reference to it in XPathExpression to use JAXPXPathEvaluator. The SelectorParserTest is the only test I can find using XPathExpression and it passes with these changes. > > xalan reference missed: > > https://github.com/apache/activemq/blob/main/assembly/src/release/examples/conf/resin-web.xml > > I'm guessing but that TransformerFactory setting can probably just be removed. That would likely mean that the JDK built-in transformer is used (unless another JAXP compliant transformer was on the classpath, eg Saxon). I don't know anything about resin. How can I test this? Issue Time Tracking --- Worklog Id: (was: 796959) Time Spent: 1h 10m (was: 1h) > 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 10m > 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)
[jira] [Work logged] (AMQ-9005) remove xalan dependency due to it being end of life
[ https://issues.apache.org/jira/browse/AMQ-9005?focusedWorklogId=796919=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-796919 ] ASF GitHub Bot logged work on AMQ-9005: --- Author: ASF GitHub Bot Created on: 01/Aug/22 14:32 Start Date: 01/Aug/22 14:32 Worklog Time Spent: 10m Work Description: jbonofre commented on PR #870: URL: https://github.com/apache/activemq/pull/870#issuecomment-1201285745 Good catch. I will do a new pass. Thanks ! Issue Time Tracking --- Worklog Id: (was: 796919) Time Spent: 1h (was: 50m) > 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 > 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)
[jira] [Work logged] (AMQ-9005) remove xalan dependency due to it being end of life
[ https://issues.apache.org/jira/browse/AMQ-9005?focusedWorklogId=796917=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-796917 ] ASF GitHub Bot logged work on AMQ-9005: --- Author: ASF GitHub Bot Created on: 01/Aug/22 14:28 Start Date: 01/Aug/22 14:28 Worklog Time Spent: 10m Work Description: mattrpav commented on PR #870: URL: https://github.com/apache/activemq/pull/870#issuecomment-1201281358 Other xalan references need to be cleaned up and XPath unit tests validated ./activemq-client/src/main/java/org/apache/activemq/filter/XPathExpression.java ./activemq-broker/src/main/java/org/apache/activemq/filter/XalanXPathEvaluator.java Issue Time Tracking --- Worklog Id: (was: 796917) Time Spent: 50m (was: 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 >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.18.0, 5.17.2 > > Time Spent: 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)
[jira] [Work logged] (AMQ-9005) remove xalan dependency due to it being end of life
[ https://issues.apache.org/jira/browse/AMQ-9005?focusedWorklogId=796913=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-796913 ] ASF GitHub Bot logged work on AMQ-9005: --- Author: ASF GitHub Bot Created on: 01/Aug/22 14:27 Start Date: 01/Aug/22 14:27 Worklog Time Spent: 10m Work Description: pjfanning commented on PR #870: URL: https://github.com/apache/activemq/pull/870#issuecomment-1201279751 > xalan reference missed: > > https://github.com/apache/activemq/blob/main/assembly/src/release/examples/conf/resin-web.xml I'm guessing but that TransformerFactory setting can probably just be removed. That would likely mean that the JDK built-in transformer is used (unless another JAXP compliant transformer was on the classpath, eg Saxon). Issue Time Tracking --- Worklog Id: (was: 796913) Time Spent: 40m (was: 0.5h) > 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 >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.18.0, 5.17.2 > > Time Spent: 40m > 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)
[jira] [Work logged] (AMQ-9005) remove xalan dependency due to it being end of life
[ https://issues.apache.org/jira/browse/AMQ-9005?focusedWorklogId=796910=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-796910 ] ASF GitHub Bot logged work on AMQ-9005: --- Author: ASF GitHub Bot Created on: 01/Aug/22 14:22 Start Date: 01/Aug/22 14:22 Worklog Time Spent: 10m Work Description: mattrpav commented on PR #870: URL: https://github.com/apache/activemq/pull/870#issuecomment-1201274483 xalan reference missed: https://github.com/apache/activemq/blob/main/assembly/src/release/examples/conf/resin-web.xml Issue Time Tracking --- Worklog Id: (was: 796910) Time Spent: 0.5h (was: 20m) > 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 >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.18.0, 5.17.2 > > Time Spent: 0.5h > 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)
[jira] [Work logged] (AMQ-9005) remove xalan dependency due to it being end of life
[ https://issues.apache.org/jira/browse/AMQ-9005?focusedWorklogId=796761=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-796761 ] ASF GitHub Bot logged work on AMQ-9005: --- Author: ASF GitHub Bot Created on: 01/Aug/22 04:39 Start Date: 01/Aug/22 04:39 Worklog Time Spent: 10m Work Description: jbonofre merged PR #870: URL: https://github.com/apache/activemq/pull/870 Issue Time Tracking --- Worklog Id: (was: 796761) Time Spent: 20m (was: 10m) > 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 >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.18.0, 5.17.2 > > Time Spent: 20m > 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)
[jira] [Work logged] (AMQ-9005) remove xalan dependency due to it being end of life
[ https://issues.apache.org/jira/browse/AMQ-9005?focusedWorklogId=796714=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-796714 ] ASF GitHub Bot logged work on AMQ-9005: --- Author: ASF GitHub Bot Created on: 31/Jul/22 18:17 Start Date: 31/Jul/22 18:17 Worklog Time Spent: 10m Work Description: lucastetreault opened a new pull request, #870: URL: https://github.com/apache/activemq/pull/870 https://issues.apache.org/jira/browse/AMQ-9005 There's no use of Xalan in code and all tests are passing without the dependency. Seems safe to remove but I assume we'll need a note about it in the release notes. Issue Time Tracking --- Worklog Id: (was: 796714) Remaining Estimate: 0h Time Spent: 10m > 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 >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.18.0, 5.17.2 > > Time Spent: 10m > 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)
