This isn't actually what we do. The ASF release is NOT a Git tag, but the
source release ZIP file. Please retain the tag as-is.
> Gesendet: Freitag, 27. August 2021 um 10:02 Uhr
> Von: "Robert Scholte"
> An: "Maven Users List"
> Betreff: Re: New release of
ot;
Aan: users@maven.apache.org
Verzonden: 27-8-2021 09:40:47
Onderwerp: Re: New release of Maven Shade Plugin
Hi
Sorry for digging up this old mail thread.
I'm also interesseted in a new maven-shade-plugin.
I noticed the 3.3.0 git tag
(https://github.com/apache/maven-shade-plugin/releases/tag/mave
Hi
Sorry for digging up this old mail thread.
I'm also interesseted in a new maven-shade-plugin.
I noticed the 3.3.0 git tag
(https://github.com/apache/maven-shade-plugin/releases/tag/maven-shade-plugin-3.3.0),
but this version doesn't seems to be published on maven central
(https://mvnreposit
Alexander Kriegisch schrieb am 22.07.2021 09:34 (GMT +07:00):
> MSHADE-366: Romain and I are still talking and working on a possible
> basic implementation of self-shading. (I have started hacking around,
> but it is not easy.) But in order to get rid of the warning, you could
> merge https://gith
MSHADE-366: Romain and I are still talking and working on a possible
basic implementation of self-shading. (I have started hacking around,
but it is not easy.) But in order to get rid of the warning, you could
merge https://github.com/apache/maven-shade-plugin/pull/104 as-is. then
you do not have t
Can we cut a new release of m-shade-p?
Is there any pending bug fix or improvement that you want to include in the
release?
Cheers
Tibor
