remove dependency scala-xml_2.11

[dependabot]

Bumps scala-xml_2.11 from 1.0.5 to 1.3.0.

Release notes

Sourced from scala-xml_2.11's releases.

Scala Standard XML Library v1.3.0

• Fixes regression on Scala 2.13, issue #392, concerning the collections implementation for NodeSeq
• Publish for Scala.js 1.0
• Update Scala.js to 0.6.32
• Update Scala to 2.12.10 and 2.13.1
• Various unused public classes and methods are deprecated
  • Deprecate definitions under scala.xml.persistent
    • CachedFileStorage
    • Index
    • SetStorage
  • Deprecate scala.xml.dtd.impl.PointedHedgeExp
  • Deprecate scala.xml.dtd.Scanner
  • Deprecate scala.xml.dtd.ContentModelParser
  • Deprecate scala.xml.dtd.ElementValidator
  • Deprecate scala.xml.factory.Binder
  • Deprecate scala.xml.parsing.ValidatingMarkupHandler

The items deprecated above are already deleted in the 2.0.0-M1 milestone release, which see https://github.com/scala/scala-xml/blob/v2.0.0-M1/CHANGELOG.md

Scala Standard XML Library v1.2.0

This is a small bug-fix release, but is released as 1.2.0 since it includes all the Scala 2.13 changes in preparation for the impending Scala 2.13.0 final. There is also a small breaking change to scala.xml.transform.RewriteRule, but it should be inconsequential.

Release notes

• Various changes for 2.13.0 support #276, #256, #217
• Fix match result for attribute search of empty string #249
• Fix missing toString in dtd.Decl #270
• Remove name field in transform.RewriteRule #129
• Update Scala.js from 0.6.26 #274
• Update Scala.js from 1.0.0-M6 #260
• Update Scala.js to 0.6.27 and 1.0.0-M7 #283
• Fix license in POM file to Apache License 2.0 #275

Binary compatibility

This release is not backwards compatible with the last release of scala-xml, 1.1.1, because of the small change that removes the name field from transform.RewriteRule, see #129. It appears to have been an unused vestigial class member in a rarely used class, so it's likely of low risk.

Scala Standard XML Library v1.1.1

This is a patch release of Scala XML that is binary and source compatible with the previous release, 1.1.0.

Release notes

• Fix #73, Utility.trim should handle whitespace between adjacent Text() nodes
• Fix #160, support nested escaped CDATA sections
• Fix #192, deprecate XMLEventReader, and suggest javax.xml.stream.events.XMLEvent
• Fix #32 and #209, out-of-memory error with ConstructingParser
• Fix #231, avoid splitting up empty elements with PrettyPrinter(minimizeEmpty = true)
• Fix #251, make invalid argument exception the same type for NodeSeq.\\()
• Fix #259, null pointer exception for DOCTYPE in XhtmlParser

... (truncated)

Changelog

Sourced from scala-xml_2.11's changelog.

Scala XML Changes

2.0.1 (2021-07-21)

Binary compatible with Scala XML 2.0.0.

Published for Scala 2.12 and 2.13, Scala 3, Scala.js 1.6, and Scala Native 0.4.

Added

• No new functionality.

Fixed

• Fixed runtime error for MarkupParser on Scala 3 by changing the access modifier of internal class, WithLookAhead (#542)

2.0.0 (2021-05-13)

Not binary compatible with Scala XML 1.3.0.

Published for Scala 2.12, 2.13, and 3.0, Scala.js 1.5, and Scala Native 0.4.

Artifacts are no longer published for Scala 2.11 and Scala.js 0.6.

A number of deprecated elements have been removed from the library; see the "Removed" section below. The library's JAR byte size is about 15% smaller.

Added

• Add scala.xml.transform.NestingTransformer, to apply a single rule recursively, to give the original behavior of RuleTransformer, see below.
• The apiURL is now published in ivy metadata so that hyperlinks exist in downstream projects that reference Scala XML in their Scaladocs.
• Declare version policy of with early-semver in Mima with sbt-version-policy plugin

Changed

• Changes to the default parser settings for the JDK SAXParser, see Safe parser defaults page on the wiki.
• The parser used by the load methods from scala.xml.XML and from scala.xml.factory.XMLLoader is now a ThreadLocal instance of SAXParser to reuse the parser instance and avoid repeatedly

... (truncated)

Commits

• c60de43 Update to Scala.js 1.0.1
• 172ce22 Merge pull request #418 from lrytz/publish-backport
• 5966334 backport new publishing scripts based on sbt-ci-release
• 003f60c Merge pull request #411 from ashawley/1.3-update
• a311d74 Various updates for 1.3.0
• 306fe58 Merge pull request #396 from ashawley/issue-392
• df7d18e Add further tests of NodeSeq
• e723935 Add test of issue 392
• bcb83f3 Fix 2.13 collections methods for NodeSeq
• a410659 Merge pull request #395 from ashawley/empty-circle
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

A newer version of org.scala-lang.modules:scala-xml_2.11 exists, but since this PR has been edited by someone other than Dependabot I haven't updated it. You'll get a PR for the updated version as normal once this PR is merged.