Hi Matt, It would probably take some time to switch to the latest release of Milton library as the versions are not 100% compatible. Apart from that, BaseX WebDAV has some custom extensions for locking resources, which would need to be reimplemented.
I remember there was another thread on licensing issues with Milton [1]. Best, Christian [1] https://www.mail-archive.com/basex-talk@mailman.uni-konstanz.de/msg10267.html On Fri, Jan 21, 2022 at 11:24 PM Matthew Dziuban <mrdziu...@gmail.com> wrote: > > Hi all, > > While auditing the library dependencies of an application, I found that > org.basex:basex-api [1] depends on a very old version of > com.ettrema:milton-api -- v1.8.1.4 released in 2014 [2]. The package seems to > have been migrated to the io.milton namespace and have a recently (December > 2021) released v3.1.0.301 [3]. This stood out to me because my application is > using the latest version of Apache commons-io, v2.11.0, while the old version > of milton-api depends on Apache commons-io v1.4, released in 2008. > > Would it be feasible to migrate BaseX to a newer version of the milton-api > library? Thanks in advance! > > Matt > > [1] https://mvnrepository.com/artifact/org.basex/basex-api/9.6.4 > [2] https://mvnrepository.com/artifact/com.ettrema/milton-api/1.8.1.4 > [3] https://mvnrepository.com/artifact/io.milton/milton-api/3.1.0.301
