You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Tibor Digana <ti...@apache.org> on 2021/07/21 22:26:10 UTC
New release of Maven Shade Plugin
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
Re: Re: New release of Maven Shade Plugin
Posted by Michael Osipov <19...@gmx.net>.
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" <ap...@sourcegrounds.com>
> An: "Maven Users List" <us...@maven.apache.org>
> Betreff: Re: New release of Maven Shade Plugin
>
> See the vote[1]
> I'll remove the github tag to prevent more confusion
>
> thanks,
> Robert
>
> [1]
> https://lists.apache.org/thread.html/rb9f899586cf49fefffc291b028a14b5fa8e22797d79d2362bcdfb58c%40%3Cdev.maven.apache.org%3E
>
>
>
> ------ Origineel bericht ------
> Van: "Philipp Dallig" <ph...@gmail.com>
> 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/maven-shade-plugin-3.3.0), but this version doesn't seems to be published on maven central (https://mvnrepository.com/artifact/org.apache.maven.plugins/maven-shade-plugin).
> >
> >I hope that we can move the tag to the latest version of the master branch, because I'm interesseted in new commits, which are improving the source code shading (https://github.com/apache/maven-shade-plugin/commit/1dca37c71649fa4f4aa110de3b78cc98d0e47eda)
> >
> >At the moment the missing release blocks quite important change in the apache/zeppelin. I created a JIRA ticket to track the progross (https://issues.apache.org/jira/browse/MSHADE-404).
> >
> >Best Regards
> >Philipp
> >
> >
> >On 2021/07/22 07:01:52, "Alexander Kriegisch" <a....@kriegisch.name> wrote:
> > > 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://github.com/apache/maven-shade-plugin/pull/104 as-is. then>
> > > > you do not have to wait for me to finish the self-shading feature, which>
> > > > IMO is out of scope for MSHADE-366 anyway.>
> > >
> > > I created MSHADE-400 on top of it and PR>
> > > https://github.com/apache/maven-shade-plugin/pull/110, which can be>
> > > reviewed already. I do not want to slow down the release process, which>
> > > is why I expedited this today for everyone's convenience.>
> > >
> > > > MSHADE-396: https://github.com/apache/maven-shade-plugin/pull/105 is>
> > > > ready for merge.>
> > > > >
> > > > >
> > > > Tibor Digana schrieb am 22.07.2021 05:26 (GMT +07:00):>
> > > > >
> > > >> 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?>
> > >
> > > --------------------------------------------------------------------->
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org>
> > > For additional commands, e-mail: users-help@maven.apache.org>
> > >
> > >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >For additional commands, e-mail: users-help@maven.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: New release of Maven Shade Plugin
Posted by Robert Scholte <ap...@sourcegrounds.com>.
See the vote[1]
I'll remove the github tag to prevent more confusion
thanks,
Robert
[1]
https://lists.apache.org/thread.html/rb9f899586cf49fefffc291b028a14b5fa8e22797d79d2362bcdfb58c%40%3Cdev.maven.apache.org%3E
------ Origineel bericht ------
Van: "Philipp Dallig" <ph...@gmail.com>
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/maven-shade-plugin-3.3.0), but this version doesn't seems to be published on maven central (https://mvnrepository.com/artifact/org.apache.maven.plugins/maven-shade-plugin).
>
>I hope that we can move the tag to the latest version of the master branch, because I'm interesseted in new commits, which are improving the source code shading (https://github.com/apache/maven-shade-plugin/commit/1dca37c71649fa4f4aa110de3b78cc98d0e47eda)
>
>At the moment the missing release blocks quite important change in the apache/zeppelin. I created a JIRA ticket to track the progross (https://issues.apache.org/jira/browse/MSHADE-404).
>
>Best Regards
>Philipp
>
>
>On 2021/07/22 07:01:52, "Alexander Kriegisch" <a....@kriegisch.name> wrote:
> > 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://github.com/apache/maven-shade-plugin/pull/104 as-is. then>
> > > you do not have to wait for me to finish the self-shading feature, which>
> > > IMO is out of scope for MSHADE-366 anyway.>
> >
> > I created MSHADE-400 on top of it and PR>
> > https://github.com/apache/maven-shade-plugin/pull/110, which can be>
> > reviewed already. I do not want to slow down the release process, which>
> > is why I expedited this today for everyone's convenience.>
> >
> > > MSHADE-396: https://github.com/apache/maven-shade-plugin/pull/105 is>
> > > ready for merge.>
> > > >
> > > >
> > > Tibor Digana schrieb am 22.07.2021 05:26 (GMT +07:00):>
> > > >
> > >> 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?>
> >
> > --------------------------------------------------------------------->
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org>
> > For additional commands, e-mail: users-help@maven.apache.org>
> >
> >
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: New release of Maven Shade Plugin
Posted by Philipp Dallig <ph...@gmail.com>.
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://mvnrepository.com/artifact/org.apache.maven.plugins/maven-shade-plugin).
I hope that we can move the tag to the latest version of the master
branch, because I'm interesseted in new commits, which are improving the
source code shading
(https://github.com/apache/maven-shade-plugin/commit/1dca37c71649fa4f4aa110de3b78cc98d0e47eda)
At the moment the missing release blocks quite important change in the
apache/zeppelin. I created a JIRA ticket to track the progross
(https://issues.apache.org/jira/browse/MSHADE-404).
Best Regards
Philipp
On 2021/07/22 07:01:52, "Alexander Kriegisch" <a....@kriegisch.name> wrote:
> 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://github.com/apache/maven-shade-plugin/pull/104 as-is.
then>
> > you do not have to wait for me to finish the self-shading feature,
which>
> > IMO is out of scope for MSHADE-366 anyway.>
>
> I created MSHADE-400 on top of it and PR>
> https://github.com/apache/maven-shade-plugin/pull/110, which can be>
> reviewed already. I do not want to slow down the release process, which>
> is why I expedited this today for everyone's convenience.>
>
> > MSHADE-396: https://github.com/apache/maven-shade-plugin/pull/105 is>
> > ready for merge.>
> > >
> > >
> > Tibor Digana schrieb am 22.07.2021 05:26 (GMT +07:00):>
> > >
> >> 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?>
>
> --------------------------------------------------------------------->
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org>
> For additional commands, e-mail: users-help@maven.apache.org>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: New release of Maven Shade Plugin
Posted by Alexander Kriegisch <al...@kriegisch.name>.
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://github.com/apache/maven-shade-plugin/pull/104 as-is. then
> you do not have to wait for me to finish the self-shading feature, which
> IMO is out of scope for MSHADE-366 anyway.
I created MSHADE-400 on top of it and PR
https://github.com/apache/maven-shade-plugin/pull/110, which can be
reviewed already. I do not want to slow down the release process, which
is why I expedited this today for everyone's convenience.
> MSHADE-396: https://github.com/apache/maven-shade-plugin/pull/105 is
> ready for merge.
>
>
> Tibor Digana schrieb am 22.07.2021 05:26 (GMT +07:00):
>
>> 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?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: New release of Maven Shade Plugin
Posted by Alexander Kriegisch <al...@kriegisch.name>.
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 to wait for me to finish the self-shading feature, which
IMO is out of scope for MSHADE-366 anyway.
MSHADE-396: https://github.com/apache/maven-shade-plugin/pull/105 is
ready for merge.
--
Alexander Kriegisch
https://scrum-master.de
Tibor Digana schrieb am 22.07.2021 05:26 (GMT +07:00):
> 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?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org