Am 2019-11-07 um 12:08 schrieb Enrico Olivelli:
Il giorno gio 7 nov 2019 alle ore 10:38 <[email protected]> ha scritto:
sure, if you know how to fix, yes, I can drop this release and start the
next one quickly
particularly if it helps us later to improve Maven handling of the case
This case of -shaded.jar published to Central [1] is really a completely
different scenario than Maven -bin.zip/tar,gz binary distribution [2] that
has the dependency added to the archive.
I currently did not really get how the shaded archive case should be
managed: do you have any strategy or fix available?
I have thought more about this case:
For the Binary Distribution of Maven we can simply add the LICENSE and
NOTICE in the zip files, I will handle it.
For the distribution on Maven central of shaded artifacts......really I
don't know.
Maybe we should ask to LEGAL as the problem is for every one that is using
the shade plugin and deploying to Maven Central.
I image we can't drop JSoup now, ot at least it won't be an easy task
Actually, we can. If you look for what JSoup is used, it does not really
make sense to do so. It assumes that the target server is Apache HTTPd
which must not be the case. Along with assumptions where
http://host/path and http://host/path/ are the same which must not
necessarily be true.
Jsoup is used to satisfy/implement
org.apache.maven.wagon.Wagon.getFileList(String) on HttpWagon and
LightweightHttpWagon, but that is wrong. HTTP has no means to list a
directory, moreover there is no notion of directories in HTTP, only
resources. Parsing some HTML file is plain wrong and makes assumptions
about an unknown environment. The only HTTP target which can satisfy
this is WebDAV where a directory can be logically mapped to a collection
which will happily respond with HTTP 207 Multistatus.
If you really cannot satisfy the license, it'd be a little risk removing
JSoup with 3.4.0.
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
