Re: [VOTE] Release Apache Maven Daemon 1.0-m6

[Olivier Lamy]

+1

On Thu, 23 Mar 2023 at 20:21, Guillaume Nodet  wrote:
>
> I've staged a candidate release at
> https://dist.apache.org/repos/dist/dev/maven/mvnd/1.0-m6/
>
> This release provides distributions based on Maven 3.9.1 and 4.0.0-alpha-4
> releases.
> The release notes are available at :
>
> https://github.com/apache/maven-mvnd/releases/tag/untagged-659daa4af1d963db7430
>
> Please review and vote !
>
> Cheers
> Guillaume Nodet

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

Re: [VOTE] Release Maven SCM Publish Plugin version 3.2.1

[Sylwester Lachiewicz]

+1

niedz., 26 mar 2023, 19:51 użytkownik Michael Osipov 
napisał:

> Hi,
>
> We solved 8 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317920=12349526
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/projects/MSCMPUB/issues
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1904/
>
> https://repository.apache.org/content/repositories/maven-1904/org/apache/maven/plugins/maven-scm-publish-plugin/3.2.1/maven-scm-publish-plugin-3.2.1-source-release.zip
>
> Source release checksum(s):
> maven-scm-publish-plugin-3.2.1-source-release.zip
> sha512:
>
> 0ccb7d851b9774de6a82302f95a3da5a551eea695afe3160c6125d50f72b70abea57476f89522d400203be04a8dba14e3ade2029ed5524fe851a0f233b862f82
>
> Staging site:
> https://maven.apache.org/plugins-archives/maven-scm-publish-plugin-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
>
>

Re: [VOTE] Release Maven SCM Publish Plugin version 3.2.1

[Slawomir Jaranowski]

+1

niedz., 26 mar 2023 o 19:51 Michael Osipov  napisał(a):

> Hi,
>
> We solved 8 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317920=12349526
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/projects/MSCMPUB/issues
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1904/
>
> https://repository.apache.org/content/repositories/maven-1904/org/apache/maven/plugins/maven-scm-publish-plugin/3.2.1/maven-scm-publish-plugin-3.2.1-source-release.zip
>
> Source release checksum(s):
> maven-scm-publish-plugin-3.2.1-source-release.zip
> sha512:
>
> 0ccb7d851b9774de6a82302f95a3da5a551eea695afe3160c6125d50f72b70abea57476f89522d400203be04a8dba14e3ade2029ed5524fe851a0f233b862f82
>
> Staging site:
> https://maven.apache.org/plugins-archives/maven-scm-publish-plugin-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
>
>

-- 
Sławomir Jaranowski

Re: [VOTE] Release Maven Fluido Skin version 2.0.0-M4

[Michael Osipov]

Am 2023-03-26 um 21:08 schrieb Herve Boutemy:

+1

but I could not reproduce the build: META-INF/LICENSE and META-INF/NOTICE give
different result

notice also that it can't be build with Maven 3.9: Jira issue created (and
easy to fix: I keep it for a new contributor)
https://issues.apache.org/jira/browse/MSKINS-220


Search JIRA you must: 
https://issues.apache.org/jira/projects/MSKINS/issues/MSKINS-216?


:-D


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

Re: [VOTE] Release Maven Fluido Skin version 2.0.0-M4

[Herve Boutemy]

+1

but I could not reproduce the build: META-INF/LICENSE and META-INF/NOTICE give 
different result

notice also that it can't be build with Maven 3.9: Jira issue created (and 
easy to fix: I keep it for a new contributor)
https://issues.apache.org/jira/browse/MSKINS-220

Regards,

Hervé

On 2023/03/25 20:49:33 Michael Osipov wrote:
> Hi,
> 
> We solved 3 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317926=12353046
> 
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSKINS%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20%22Fluido%20Skin%22
> 
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1902/
> https://repository.apache.org/content/repositories/maven-1902/org/apache/maven/skins/maven-fluido-skin/2.0.0-M4/maven-fluido-skin-2.0.0-M4-source-release.zip
> 
> Source release checksum(s):
> maven-fluido-skin-2.0.0-M4-source-release.zip
> sha512: 
> 628391f3d8745f8e1213580b282af804fefaaab1c359af0ce80b18eb0cdb673b3a4bf8adab55f670328ad9fa09981a387f09ff4040dc2ddeff6b90fa3b5471db
> 
> Staging site:
> https://maven.apache.org/components/skins-archives/maven-fluido-skin-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 SCM Publish Plugin version 3.2.1

[Hervé Boutemy]

+1

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

Regards,

Hervé

Le dimanche 26 mars 2023, 19:51:31 CEST Michael Osipov a écrit :
> Hi,
> 
> We solved 8 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317920
> rsion=12349526
> 
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/projects/MSCMPUB/issues
> 
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1904/
> https://repository.apache.org/content/repositories/maven-1904/org/apache/mav
> en/plugins/maven-scm-publish-plugin/3.2.1/maven-scm-publish-plugin-3.2.1-sou
> rce-release.zip
> 
> Source release checksum(s):
> maven-scm-publish-plugin-3.2.1-source-release.zip
> sha512:
> 0ccb7d851b9774de6a82302f95a3da5a551eea695afe3160c6125d50f72b70abea57476f8952
> 2d400203be04a8dba14e3ade2029ed5524fe851a0f233b862f82
> 
> Staging site:
> https://maven.apache.org/plugins-archives/maven-scm-publish-plugin-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

[VOTE] Release Maven SCM Publish Plugin version 3.2.1

[Michael Osipov]

Hi,

We solved 8 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317920=12349526

There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/projects/MSCMPUB/issues

Staging repo:
https://repository.apache.org/content/repositories/maven-1904/
https://repository.apache.org/content/repositories/maven-1904/org/apache/maven/plugins/maven-scm-publish-plugin/3.2.1/maven-scm-publish-plugin-3.2.1-source-release.zip

Source release checksum(s):
maven-scm-publish-plugin-3.2.1-source-release.zip
sha512: 
0ccb7d851b9774de6a82302f95a3da5a551eea695afe3160c6125d50f72b70abea57476f89522d400203be04a8dba14e3ade2029ed5524fe851a0f233b862f82


Staging site:
https://maven.apache.org/plugins-archives/maven-scm-publish-plugin-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

Re: [VOTE] Release Maven Fluido Skin version 2.0.0-M4

[Michael Osipov]

Am 2023-03-26 um 18:49 schrieb Slawomir Jaranowski:

+1

Anchors and links generated by the toc macro on the main page are not
working   but probably is not a problem with skin


Applied one-off patch.


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

Re: [DISCUSSION] Apache Maven plugins versioning

[Michael Osipov]

Am 2023-03-26 um 19:02 schrieb Romain Manni-Bucau:

@Benjamin what's the addtion of the "4" except looking weird after 1
version since you use semver? It forces 2 changes instead of one without
anything else explicit IMHO.


I fully second that!


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

Re: [DISCUSSION] Apache Maven plugins versioning

[Romain Manni-Bucau]

@Benjamin what's the addtion of the "4" except looking weird after 1
version since you use semver? It forces 2 changes instead of one without
anything else explicit IMHO.

Romain Manni-Bucau
@rmannibucau  |  Blog
 | Old Blog
 | Github  |
LinkedIn  | Book



Le dim. 26 mars 2023 à 18:16, Benjamin Marwell  a
écrit :

> +1 to your proposal
>
> org.apache.maven:maven4-xyz-plugin:
>
> I don't think it would cause too much trouble as Maven APIs will love for a
> few years. It will only occasionally break when a new major Maven release
> is published. I can live with that.
>
> Also, maven 3 plugins will be compatible for a while.
>
>
>
>
> On Thu, 23 Mar 2023, 20:58 Slawomir Jaranowski, 
> wrote:
>
> > Hi,
> >
> > I know that historically plugin versions like 2.x was dedicated to Maven
> > 2.x and versions 3.x is for Maven 3.x.
> >
> > We don't have any written documentation about it (or I can't find it), it
> > looks like a traditional agreement.
> >
> > Nowadays Semantic Versioning is very popular and it is understood by
> people
> > and by automatic tools.
> > In many cases we use versions which look like Semantic Versioning
> (x.y.z) -
> > but internally we try to classify it in different ways.
> >
> > When we connect the plugins version with the Maven version as the major
> > version,
> > we have difficulty introducing breaking changes for plugins for the same
> > Maven version.
> > Also we can introduce many misunderstandings which version contains new
> > features and which only bug fixes.
> >
> > Authors of plugins outside Maven core in many cases don't use 3.x as for
> > Maven 3 and so on.
> >
> > One of the propositions can be - use Semantic Versioning as is described
> > and put a Maven version in the artifact name of the plugin.
> >
> > So we can have:
> >
> > maven4-XXX-plugin - for core plugins
> > XXX-maven4-plugin - for external plugins
> >
> > Additionally Maven 4 will have a new Api which is incompatible with Maven
> > 3, when we have the target Maven version in artifact it will be easier to
> > transition plugins from 3 to 4 and so on.
> >
> > Simply in many cases business logic which plugin provides can be
> extracted
> > to a common module and next two modules will provide plugins for specific
> > Maven.
> > It can help maintain one plugin for many Maven versions.
> >
> >
> > --
> > Sławomir Jaranowski
> >
>

Re: [VOTE] Release Maven Fluido Skin version 2.0.0-M4

[Slawomir Jaranowski]

+1

Anchors and links generated by the toc macro on the main page are not
working   but probably is not a problem with skin

sob., 25 mar 2023 o 21:49 Michael Osipov  napisał(a):

> Hi,
>
> We solved 3 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317926=12353046
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSKINS%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20%22Fluido%20Skin%22
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1902/
>
> https://repository.apache.org/content/repositories/maven-1902/org/apache/maven/skins/maven-fluido-skin/2.0.0-M4/maven-fluido-skin-2.0.0-M4-source-release.zip
>
> Source release checksum(s):
> maven-fluido-skin-2.0.0-M4-source-release.zip
> sha512:
>
> 628391f3d8745f8e1213580b282af804fefaaab1c359af0ce80b18eb0cdb673b3a4bf8adab55f670328ad9fa09981a387f09ff4040dc2ddeff6b90fa3b5471db
>
> Staging site:
>
> https://maven.apache.org/components/skins-archives/maven-fluido-skin-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
>
>

-- 
Sławomir Jaranowski

Re: [DISCUSSION] Apache Maven plugins versioning

[Benjamin Marwell]

+1 to your proposal

org.apache.maven:maven4-xyz-plugin:

I don't think it would cause too much trouble as Maven APIs will love for a
few years. It will only occasionally break when a new major Maven release
is published. I can live with that.

Also, maven 3 plugins will be compatible for a while.




On Thu, 23 Mar 2023, 20:58 Slawomir Jaranowski, 
wrote:

> Hi,
>
> I know that historically plugin versions like 2.x was dedicated to Maven
> 2.x and versions 3.x is for Maven 3.x.
>
> We don't have any written documentation about it (or I can't find it), it
> looks like a traditional agreement.
>
> Nowadays Semantic Versioning is very popular and it is understood by people
> and by automatic tools.
> In many cases we use versions which look like Semantic Versioning (x.y.z) -
> but internally we try to classify it in different ways.
>
> When we connect the plugins version with the Maven version as the major
> version,
> we have difficulty introducing breaking changes for plugins for the same
> Maven version.
> Also we can introduce many misunderstandings which version contains new
> features and which only bug fixes.
>
> Authors of plugins outside Maven core in many cases don't use 3.x as for
> Maven 3 and so on.
>
> One of the propositions can be - use Semantic Versioning as is described
> and put a Maven version in the artifact name of the plugin.
>
> So we can have:
>
> maven4-XXX-plugin - for core plugins
> XXX-maven4-plugin - for external plugins
>
> Additionally Maven 4 will have a new Api which is incompatible with Maven
> 3, when we have the target Maven version in artifact it will be easier to
> transition plugins from 3 to 4 and so on.
>
> Simply in many cases business logic which plugin provides can be extracted
> to a common module and next two modules will provide plugins for specific
> Maven.
> It can help maintain one plugin for many Maven versions.
>
>
> --
> Sławomir Jaranowski
>

Re: [DISCUSSION] Apache Maven plugins versioning

[Michael Osipov]

Am 2023-03-23 um 20:57 schrieb Slawomir Jaranowski:

Hi,

I know that historically plugin versions like 2.x was dedicated to Maven
2.x and versions 3.x is for Maven 3.x.

We don't have any written documentation about it (or I can't find it), it
looks like a traditional agreement.


I wouldn't tie it anymore. It just needs proper documentation. I will 
soon bump *all* reporting plugins to new major versions because the 
Doxia 2.0.0 stack is coming. Same Maven version, but Doxia 1.x will be 
left behind. This CANNOT happen in a minor version.


SemVer has its issues, it does not support post-release qualifiers, I 
consider it, by looking at the EBNF too complex.


We have also this: 
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-dist-tool/job/master/site/dist-tool-prerequisites.html


M

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

Re: [VOTE] Release Maven Fluido Skin version 2.0.0-M4

[Michael Osipov]

Am 2023-03-25 um 21:49 schrieb Michael Osipov:

Hi,

We solved 3 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317926=12353046

There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSKINS%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20%22Fluido%20Skin%22

Staging repo:
https://repository.apache.org/content/repositories/maven-1902/
https://repository.apache.org/content/repositories/maven-1902/org/apache/maven/skins/maven-fluido-skin/2.0.0-M4/maven-fluido-skin-2.0.0-M4-source-release.zip

Source release checksum(s):
maven-fluido-skin-2.0.0-M4-source-release.zip
sha512: 
628391f3d8745f8e1213580b282af804fefaaab1c359af0ce80b18eb0cdb673b3a4bf8adab55f670328ad9fa09981a387f09ff4040dc2ddeff6b90fa3b5471db


Staging site:
https://maven.apache.org/components/skins-archives/maven-fluido-skin-LATEST/

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

Vote open for 72 hours.


+1


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