I notice the release process happened on the repository. Thank you! If you
need a volunteer to verify the release candidate or any help, please let me
know :)

Best,
tison.


tison <wander4...@gmail.com> 于2022年9月10日周六 17:16写道:

> Hi,
>
> Bump this thread as a kind reminder ;)
>
> Best,
> tison.
>
>
> Romain Manni-Bucau <rmannibu...@gmail.com> 于2022年9月6日周二 21:51写道:
>
>> Le mar. 6 sept. 2022 à 15:45, Delany <delany.middle...@gmail.com> a
>> écrit :
>>
>> > Just to add, IntelliJ's tooltip links to
>> > https://maven.apache.org/ref/2.2.1/maven-model/maven.html
>> > Where is it getting v2.2.1 from?
>> >
>>
>>
>>
>> https://github.com/JetBrains/intellij-community/blob/522209df34f7266923df5133f9b50b226054412a/plugins/maven/src/main/java/org/jetbrains/idea/maven/dom/MavenModelDocumentationProvider.java#L41
>>
>>
>> > The plugin depends on v3.1.1 (
>> >
>> >
>> https://github.com/apache/maven-shade-plugin/blob/maven-shade-plugin-3.3.0/pom.xml
>> > )
>> > Delany
>> >
>> > On Tue, 6 Sept 2022 at 15:35, Romain Manni-Bucau <rmannibu...@gmail.com
>> >
>> > wrote:
>> >
>> > > Hi,
>> > >
>> > > It is a generic maven issue, on intellij side it is mainly a matter of
>> > > checking the expceted model and enhance the completion > 2 levels (not
>> > > supported as of today - actually 1 level or 2 for containers like
>> lists).
>> > > On maven side I guess supporting xsd for the plugin configuration can
>> > help
>> > > there (could be generated by the maven-plugin-plugin tooling).
>> > >
>> > > Romain Manni-Bucau
>> > > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
>> > > <https://rmannibucau.metawerx.net/> | Old Blog
>> > > <http://rmannibucau.wordpress.com> | Github <
>> > > https://github.com/rmannibucau> |
>> > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
>> > > <
>> > >
>> >
>> https://www.packtpub.com/application-development/java-ee-8-high-performance
>> > > >
>> > >
>> > >
>> > > Le mar. 6 sept. 2022 à 15:31, Delany <delany.middle...@gmail.com> a
>> > écrit
>> > > :
>> > >
>> > > > While we're talking about shade, I noticed if I spell a tag wrong
>> > neither
>> > > > `mvn validate` nor IntelliJ take issue with my tag <inlucde>
>> > > >
>> > > >         <artifactId>maven-shade-plugin</artifactId>
>> > > >         <executions>
>> > > >           <execution>
>> > > >             <id>default</id>
>> > > >             <phase>pre-integration-test</phase>
>> > > >             <configuration>
>> > > >               <artifactSet>
>> > > >                 <includes>
>> > > >                   <inlucde>software.amazon.awssdk:ecr</inlucde>
>> > > >
>> > > > And it builds!
>> > > > How can this situation be improved?
>> > > >
>> > > > Kind regards,
>> > > > Delany
>> > > >
>> > > > On Tue, 6 Sept 2022 at 13:25, tison <wander4...@gmail.com> wrote:
>> > > >
>> > > > > Thank you!
>> > > > >
>> > > > > Best,
>> > > > > tison.
>> > > > >
>> > > > >
>> > > > > Karl Heinz Marbaise <khmarba...@gmx.de> 于2022年9月6日周二 17:44写道:
>> > > > >
>> > > > > > Hi,
>> > > > > >
>> > > > > > I will try to do a release on the weekend...
>> > > > > >
>> > > > > > Kind regards
>> > > > > > Karl Heinz Marbaise
>> > > > > > On 06.09.22 10:55, tison wrote:
>> > > > > > > Hi,
>> > > > > > >
>> > > > > > > The latest release of m-shade-p happened in March 2022 and now
>> > > about
>> > > > > > half a
>> > > > > > > year passed. We have some dependencies bump and one bug fix
>> > > > > > MSHADE-425[1].
>> > > > > > >
>> > > > > > > As the author of the patch to MSHADED-425, I made it to
>> resolve
>> > one
>> > > > or
>> > > > > > > several downstream troubles as described in the ticket. Now
>> I'm
>> > > > looking
>> > > > > > > forward to a new release and I'll upgrade the downstream
>> > > dependencies
>> > > > > for
>> > > > > > > this fix.
>> > > > > > >
>> > > > > > > As suggested by the reviewers, I come here to see if there's a
>> > > > > volunteer
>> > > > > > > release manager. I'm happy to verify the release candidate :)
>> > > > > > >
>> > > > > > > Best,
>> > > > > > > tison.
>> > > > > > >
>> > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>>
>

Reply via email to