Re: [VOTE] Release Apache Maven Reporting Impl version 4.0.0

[Herve Boutemy]

+1

Reproducible Build ok: reference build done with JDK 8 on Windows

Regards,

Hervé

On 2024/10/12 19:48:50 Michael Osipov wrote:
> Hi,
> 
> we solved 69 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12354042
> 
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20maven-reporting-impl
> 
> Staging repo:
> https://repository.apache.org/content/repositories/maven-2216/
> https://repository.apache.org/content/repositories/maven-2216/org/apache/maven/reporting/maven-reporting-impl/4.0.0/maven-reporting-impl-4.0.0-source-release.zip
> 
> Source release checksum(s):
> maven-reporting-impl-4.0.0-source-release.zip
> sha512: 
> c338cd213a3a152adec8aa0a36d557988e6678384aa0b18df9af7d2f3ae67ea318b79b833c5369e6c8c0239da73a95664b4127dc2498cd567eb9c688569fa933
> 
> Staging site:
> https://maven.apache.org/shared-archives/maven-reporting-impl-LATEST/
> 
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
> 
> Vote open for 72 hours.
> 
> [ ] +1
> [ ] +0
> [ ] -1
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
> 
> 

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Release Maven Resolver 2.0.2

[Herve Boutemy]

+1

Reproducible Build ok: reference build done with JDK 21 on *nix

Regards,

Hervé

On 2024/10/14 20:48:19 Tamás Cservenák wrote:
> Howdy,
> 
> This Resolver 2.0.2 release is a bugfix release with several
> improvements as well.
> 
> Maven 4.x is picking up Resolver 2.x, while Maven 3.x remains at
> Resolver 1.x lineage. The two major versions, as far as client code
> goes (Mojos or extensions, using Resolver API as documented), are
> binary compatible, see [1] and [2].
> 
> Resolver 2.0.2 is to be picked up by the upcoming Maven 4 release.
> 
> We solved 14 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&version=12354988
> 
> There are still some issues in JIRA:
> https://issues.apache.org/jira/projects/MRESOLVER/issues
> 
> Staging repository:
> https://repository.apache.org/content/repositories/maven-2217/
> 
> Source release SHA512:
> 384ae0cb4806d0ad4cc59dd56e1ced56ceb8439d1d633940b63bcf07ce71f7423faa1635223651806c13eec2cdf8858a27f2da70e858467a9cca5f11bcdfbcad
> 
> Staging site:
> https://maven.apache.org/resolver-archives/resolver-LATEST/
> 
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
> 
> [1] 
> https://maven.apache.org/resolver-archives/resolver-LATEST/api-compatibility.html
> [2] 
> https://maven.apache.org/resolver-archives/resolver-LATEST/upgrading-resolver.html
> 
> Vote open for 72 hours.
> 
> [ ] +1
> [ ] +0
> [ ] -1
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
> 
> 

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

[VOTE] Release Maven Resolver 2.0.2

[Tamás Cservenák]

Howdy,

This Resolver 2.0.2 release is a bugfix release with several
improvements as well.

Maven 4.x is picking up Resolver 2.x, while Maven 3.x remains at
Resolver 1.x lineage. The two major versions, as far as client code
goes (Mojos or extensions, using Resolver API as documented), are
binary compatible, see [1] and [2].

Resolver 2.0.2 is to be picked up by the upcoming Maven 4 release.

We solved 14 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&version=12354988

There are still some issues in JIRA:
https://issues.apache.org/jira/projects/MRESOLVER/issues

Staging repository:
https://repository.apache.org/content/repositories/maven-2217/

Source release SHA512:
384ae0cb4806d0ad4cc59dd56e1ced56ceb8439d1d633940b63bcf07ce71f7423faa1635223651806c13eec2cdf8858a27f2da70e858467a9cca5f11bcdfbcad

Staging site:
https://maven.apache.org/resolver-archives/resolver-LATEST/

Guide to testing staged releases:
https://maven.apache.org/guides/development/guide-testing-releases.html

[1] 
https://maven.apache.org/resolver-archives/resolver-LATEST/api-compatibility.html
[2] 
https://maven.apache.org/resolver-archives/resolver-LATEST/upgrading-resolver.html

Vote open for 72 hours.

[ ] +1
[ ] +0
[ ] -1

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

[VOTE] Release Apache Maven Artifact Plugin version 3.5.2

[Hervé Boutemy]

Hi,

We solved 12 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12324322&version=12354471&styleName=Text

Staging repo:
https://repository.apache.org/content/repositories/maven-2218
https://repository.apache.org/content/repositories/maven-2218/org/apache/maven/plugins/maven-artifact-plugin/3.5.2/maven-artifact-plugin-3.5.2-source-release.zip

Source release checksum(s):
maven-artifact-plugin-3.5.2-source-release.zip: 
926559590be3263517a647c6d28409262fc35a0cc5324137131f39ce7a904706e0905bc4b37808ee8929f688c406c1bec233ff1331efac04728048501e7b49f5%

Staging site:
https://maven.apache.org/plugins-archives/maven-artifact-plugin-LATEST/

Guide to testing staged releases:
https://maven.apache.org/guides/development/guide-testing-releases.html

Vote open for at least 72 hours.

[ ] +1
[ ] +0
[ ] -1



-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Maven 3.9.7 generates dodgy snapshot maven-metadata.xml

[Dale Ogilvie]

Thanks for that. Our artifactory release predates 7.68 so this could well
be the culprit.

On Tue, Oct 15, 2024 at 7:16 AM Richard Eckart de Castilho 
wrote:

> Hi
>
> > On 14. Oct 2024, at 01:31, Dale Ogilvie 
> wrote:
> >
> > The trick is, the generated maven-metadata.xml is fine when we use maven
> > 3.8.5. This is a very mature build pipeline, and we have just started
> > noticing this, after a switch to 3.9.x
> >
> > I'm taking a look at this off of our build infrastructure.
>
> If you see this problem when deploying to Artifactory, it might be due to
> a bug in Artifactory.
>
> RTDEV-35001
>
>
> https://jfrog.com/help/r/jfrog-release-information/artifactory-7.68.11-self-hosted
>
> Cheers,
>
> -- Richard
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

-- 
Dale Ogilvie
Senior Software Engineer,
Technical and Process Coach,
Business Systems
11 Birmingham Drive, Christchurch, New Zealand
+64-22-6005437 Mobile
dale_ogil...@trimble.com

Re: [doxia] [DISCUSS] adding footnote processing to markdown

[Michael Osipov]

The only remaining task is to update deps and do the actual releases. See: 
https://cwiki.apache.org/confluence/display/MAVEN/Towards+Doxia+2.0.0+Stack#TowardsDoxia2.0.0Stack-ComponentReleaseOrder
Expect the trail to be complete end of October.

On 2024/10/13 12:45:38 Claude Warren wrote:
> May i assist in the testing / dev.  Or are you far enough along that
> bringing in a new head will take to much time away with bringing me op to
> speed?
> 
> On Sun 13 Oct 2024, 12:55 Michael Osipov,  wrote:
> 
> > On 2024/10/13 11:07:45 Claude Warren wrote:
> > > Now that Doxia 2.0 is out is there something that has to be done to
> > enable
> > > footnotes or are they enabled by default?
> >
> > Wait until next Maven Site Plugin version is released unless you want to
> > fiddle with deps.
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >
> 

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Maven 3.9.7 generates dodgy snapshot maven-metadata.xml

[Richard Eckart de Castilho]

Hi

> On 14. Oct 2024, at 01:31, Dale Ogilvie  wrote:
> 
> The trick is, the generated maven-metadata.xml is fine when we use maven
> 3.8.5. This is a very mature build pipeline, and we have just started
> noticing this, after a switch to 3.9.x
> 
> I'm taking a look at this off of our build infrastructure.

If you see this problem when deploying to Artifactory, it might be due to a bug 
in Artifactory.

RTDEV-35001

https://jfrog.com/help/r/jfrog-release-information/artifactory-7.68.11-self-hosted

Cheers,

-- Richard


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org