[ANN] Maven Deploy Plugin 3.0.0 Released

2022-07-19 Thread Tamás Cservenák
Howdy, The Apache Maven team is pleased to announce the release of Maven Deploy Plugin 3.0.0. Plugin is Java7 level and compatible with Maven 3.2.5+ Site: https://maven.apache.org/plugins/maven-deploy-plugin/ Release Notes - Maven Deploy Plugin - Version 3.0.0 ** Bug * [MDEPLOY-193] -

[ANN] Maven Install Plugin 3.0.0 Released

2022-07-19 Thread Tamás Cservenák
Howdy, The Apache Maven team is pleased to announce the release of Maven Install Plugin 3.0.0. Plugin is Java7 level and compatible with Maven 3.2.5+ Site: https://maven.apache.org/plugins/maven-install-plugin/ === NOTE: Release 3.0.0 has a regression related to install-file Mojo that slipped

[ANN[ Maven Indexer 6,2,2 Released

2022-07-19 Thread Tamás Cservenák
Howdy, The Apache Maven team is pleased to announce the release of Maven Indexer 6.2.2. Site: https://maven.apache.org/maven-indexer/ Release Notes - Maven Indexer - Version 6.2.2 ** Bug * [MINDEXER-164] - IndexOutOfBoundsException during indexing of repositories files Have fun - The

Re: Maven-Assembly-Plugin v3.4.1 not correctly processing assembly descriptors?

2022-07-19 Thread Tamás Cservenák
Howdy, yes, maven-common-artifact-filters vote/release is ongoing, next will be m-asembly-p 3.4.2 filters is out tomorrow (3 day vote), and then m-asembly-p release (another 3 day vote). HTH T On Tue, Jul 19, 2022 at 12:56 PM Jean Pierre URKENS wrote: > Looks like the issue is already

RE: Maven-Assembly-Plugin v3.4.1 not correctly processing assembly descriptors?

2022-07-19 Thread Jean Pierre URKENS
Unfortunately, I already tried it but v3.3.1 of the maven-common-artifact-filters is for the moment in no maven repository available, so dependency resolution fails. I don't know where to download the artifact otherwise (github page doesn't include references to builds). Kind Regards, J.P.

Re: Maven-Assembly-Plugin v3.4.1 not correctly processing assembly descriptors?

2022-07-19 Thread Karl Heinz Marbaise
Hi, You can verify that if you simply add the maven-common-artifact-filters version in the dependencies part of the plugin configuration where you defined the dvtm.base Assembly Kind regards Karl Heinz Marbaise On 19.07.22 12:55, Jean Pierre URKENS wrote: Looks like the issue is already

RE: Maven-Assembly-Plugin v3.4.1 not correctly processing assembly descriptors?

2022-07-19 Thread Jean Pierre URKENS
Looks like the issue is already reported: https://issues.apache.org/jira/projects/MASSEMBLY/issues/MASSEMBLY-969?filter=allopenissues and solved by https://github.com/apache/maven-common-artifact-filters/pull/29. Maven-Assembly-Plugin v3.4.1 uses maven-common-artifact-filters v3.3.0 -> fails

Re: Maven-Assembly-Plugin v3.4.1 not correctly processing assembly descriptors?

2022-07-19 Thread Karl Heinz Marbaise
Hi, can you make an example project on github or alike... Kind regards Karl Heinz Marbaise On 19.07.22 12:07, Jean Pierre URKENS wrote: I am trying to re-zip some deliverables into one packaging using the maven-assembly-plugin. My plugin configuration looks like:

Re: m-javadoc-plugin with JPMS

2022-07-19 Thread Olivier Lamy
On Tue, 19 Jul 2022 at 16:42, Maxim Solodovnik wrote: > On Tue, 19 Jul 2022 at 13:16, Daniel Widdis wrote: > > > > > The only problem of having both is redundancy :) > > > > Technically speaking, you always have an automatic module name even if > you don't explicitly name it. It will use your

Maven-Assembly-Plugin v3.4.1 not correctly processing assembly descriptors?

2022-07-19 Thread Jean Pierre URKENS
I am trying to re-zip some deliverables into one packaging using the maven-assembly-plugin. My plugin configuration looks like: org.apache.maven.plugins *maven-assembly-plugin* 3.4.1

Re: m-javadoc-plugin with JPMS

2022-07-19 Thread Maxim Solodovnik
On Tue, 19 Jul 2022 at 13:16, Daniel Widdis wrote: > > > The only problem of having both is redundancy :) > > Technically speaking, you always have an automatic module name even if you > don't explicitly name it. It will use your jar filename to deduce one. > Unless you use a reserved word

Re: m-javadoc-plugin with JPMS

2022-07-19 Thread Daniel Widdis
> The only problem of having both is redundancy :) Technically speaking, you always have an automatic module name even if you don't explicitly name it. It will use your jar filename to deduce one. Unless you use a reserved word in your jar, and then the world breaks. __ On 7/18/22, 11:07

Re: m-javadoc-plugin with JPMS

2022-07-19 Thread Maxim Solodovnik
Thanks for the answer Daniel :) On Tue, 19 Jul 2022 at 13:03, Daniel Widdis wrote: > > I think you're asking on the right list. And it's not a "basic" question but > it isn't an obvious answer either. > > I'm not sure your question has enough detail for anyone to deduce the answer. > Linking

Re: m-javadoc-plugin with JPMS

2022-07-19 Thread Daniel Widdis
I think you're asking on the right list. And it's not a "basic" question but it isn't an obvious answer either. I'm not sure your question has enough detail for anyone to deduce the answer. Linking to your project may help you get more attention on it. FWIW, I have both an automatic module