Re: maven-plugin-testing-harness
wt., 27 wrz 2022 o 16:31 Christoph Läubrich napisał(a): > I recently came across a problem with the > maven-plugin-testing-harness[1] and wanted to report a bug, but without > success. > > > https://maven.apache.org/plugin-testing/maven-plugin-testing-harness/issue-tracking.html > -> dead link > https://issues.apache.org/jira/projects/MPLUGINTESTING > > https://maven.apache.org/plugin-testing/maven-plugin-testing-harness/source-repository.html > -> dead link > > https://github.com/apache/maven-plugin-testing/ > So is maven-plugin-testing-harness dead? Are there any modern approaches > to use? > You are right, the project needs some refresh ... It is widely used so is not dead > [1] > > https://mvnrepository.com/artifact/org.apache.maven.plugin-testing/maven-plugin-testing-harness/3.3.0 > > - > 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 Apache Maven 4.0.0-alpha-2
Thanks. Site is also available under https://maven.apache.org/ref/4-LATEST/ - there are some missing links like https://maven.apache.org/ref/4-LATEST/maven-model/maven.html - some are outdated like https://maven.apache.org/ref/4-LATEST/maven-settings/settings.html For me it can be fixed in next releases ... niedz., 16 paź 2022 o 15:27 Guillaume Nodet napisał(a): > I've also deployed the distributions at > > > https://dist.apache.org/repos/dist/dev/maven/maven-4/4.0.0-alpha-2/binaries/ > > https://dist.apache.org/repos/dist/dev/maven/maven-4/4.0.0-alpha-2/sources/ > > and the web site at: > > > http://svn.apache.org/repos/asf/maven/website/components/ref/4-LATEST/index.html > > Guillaume > > Le sam. 15 oct. 2022 à 12:32, Slawomir Jaranowski > a écrit : > > > Hi, > > > > Link for biaries is: > > > > > https://repository.apache.org/content/repositories/maven-1811/org/apache/maven/apache-maven/4.0.0-alpha-2/ > > > > By the way binaries should be available at distribution area also ... > > https://dist.apache.org/repos/dist/dev/maven/ > > > > Did you publish a staging Maven site somewhere? > > > > > > sob., 15 paź 2022 o 02:19 Guillaume Nodet > napisał(a): > > > > > I've staged a release candidate at > > > https://repository.apache.org/content/repositories/maven-1811 > > > > > > The binaries are available at: > > > > > > > > > > > > https://repository.apache.org/service/local/repositories/maven-1811/content/org/apache/maven/apache-maven/4.0.0-alpha-2/ > > > > > > The tag is available at: > > > https://github.com/apache/maven/tree/maven-4.0.0-alpha-2 > > > > > > Please review and vote ! > > > > > > Cheers, > > > Guillaume Nodet > > > > > > > > > -- > > Sławomir Jaranowski > > > > > -- > > Guillaume Nodet > -- Sławomir Jaranowski
Re: [DISCUSS] Release Maven 4.0.0-alpha-1 this week
> > Fully agreed, that's what I initially tried to do. But the repository does > not allow removing a tag. So this would have to be changed. > I see deleted tags ... maybe Maven core repository has another configurations https://lists.apache.org/list?comm...@maven.apache.org:lte=1y:annotated%20tag%20deleted I think it is to check - and we should update procedure of release for such case -- Sławomir Jaranowski
Re: [VOTE] Release Maven Doxia version 2.0.0-M4
+1 niedz., 16 paź 2022 o 21:30 Michael Osipov napisał(a): > Hi, > > We solved 17 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317230=12352066 > > There are still a couple of issues left in JIRA: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20DOXIA%20AND%20resolution%20%3D%20Unresolved > > Staging repo: > https://repository.apache.org/content/repositories/maven-1812/ > > https://repository.apache.org/content/repositories/maven-1812/org/apache/maven/doxia/doxia/2.0.0-M4/doxia-2.0.0-M4-source-release.zip > > Source release checksum(s): > doxia-2.0.0-M4-source-release.zip > sha512: > > 49138846067639a96b99c6c27778ddfbab6fbde503b128d00d66df1a50c993d90f9939fba96115440e932c06add09c8aa87d36b47f895faee79e3a51f3eaa512 > > Staging site: > https://maven.apache.org/doxia/doxia-archives/doxia-LATEST/ > > Guide to testing staged releases: > http://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
[VOTE] Release Apache Maven EAR Plugin version 3.3.0
Hi, We solved 18 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317422=12349537 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MEAR%20AND%20resolution%20%3D%20Unresolved Staging repo: https://repository.apache.org/content/repositories/maven-1813/ https://repository.apache.org/content/repositories/maven-1813/org/apache/maven/plugins/maven-ear-plugin/3.3.0/maven-ear-plugin-3.3.0-source-release.zip Source release checksum(s): maven-ear-plugin-3.3.0-source-release.zip - SHA-512 : 41ef2aaf6aa14936c3913a71bff4dc5ae01ac40e0b9ccd7ac8e383973a4c3b3185e2d6a1fa415b5f46130b8b5a49110e9e5f280f6269eba316581fa850a10702 Staging site: https://maven.apache.org/plugins-archives/maven-ear-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 -- Sławomir Jaranowski
Install / Deploy plugins at the end
Hi, I'm looking for how to resolve issues connected with the feature installAtEnd / deployAtEnd of install and deploy plugins. We have a similar feature in clean plugin where it is implemented by wrapping session.getRequest().getExecutionListener() [1] Because ExecutionListener on request is not chained by default it will be difficult implement the next wrappers in two plugins. In current implementation we assume that install or deploy plugins are executed in all modules, but it can not be true e.g. one module can use different packaging which doesn't have those plugins in their lifecycle so detecting the last executing module does not work. We can also have skipped or not used install / deploy plugins in the last executed module. I'm thinking of using AbstractMavenLifecycleParticipant to detect the end of a Maven session and to finish the job in afterSessionEnd callback. But in this way I see another issue - AbstractMavenLifecycleParticipant.afterSessionEnd method is called after session.request.ExecutionListene which prints a summary of whole build, so we have additional tasks not computed in the build summary - Can it be accepted? I don't have a sure which callback method will be called first from install or from deploy plugin. So we can have a situation where deployment will be executed first. Can it be accepted? Of course when we will use the AbstractMavenLifecycleParticipant plugin must be configured as an extension - but it is not an issue I think. Any other suggestions ... Some of related issues: https://issues.apache.org/jira/browse/MINSTALL-102 https://issues.apache.org/jira/browse/MDEPLOY-226 [1] https://github.com/apache/maven-clean-plugin/blob/master/src/main/java/org/apache/maven/plugins/clean/Cleaner.java#L514-L527 -- Sławomir Jaranowski
Re: Install / Deploy plugins at the end
I'm. In plugins each processed module are marked with one of flags: SKIPPED, INSTALLED, TO_BE_INSTALLED or SKIPPED, DEPLOYED, TO_BE_DEPLOYED And finally we check if all modules have a flag set to detect end of session in method allProjectsMarked But if one module not used install / deploy plugins at all - nothing will be installed / deployed. To reproduce - in multimodule project - bind install / deploy plugin to none phase in one of modules. śr., 19 paź 2022 o 22:59 Tamás Cservenák napisał(a): > Slawek, > > Are you sure those issues still stand for 3.0.x of plugins? > > T > > > On Wed, Oct 19, 2022, 22:07 Slawomir Jaranowski > wrote: > > > Hi, > > > > I'm looking for how to resolve issues connected with the feature > > installAtEnd / deployAtEnd of install and deploy plugins. > > > > We have a similar feature in clean plugin where it is implemented by > > wrapping session.getRequest().getExecutionListener() [1] > > Because ExecutionListener on request is not chained by default it will be > > difficult implement the next wrappers in two plugins. > > > > In current implementation we assume that install or deploy plugins are > > executed in all modules, > > but it can not be true e.g. one module can use different packaging > > which doesn't have those plugins in their lifecycle > > so detecting the last executing module does not work. > > > > We can also have skipped or not used install / deploy plugins in the last > > executed module. > > > > I'm thinking of using AbstractMavenLifecycleParticipant to detect the end > > of a Maven session and to finish the job in afterSessionEnd callback. > > > > But in this way I see another issue - > > AbstractMavenLifecycleParticipant.afterSessionEnd method is called after > > session.request.ExecutionListene which prints a summary of whole build, > > so we have additional tasks not computed in the build summary - Can it be > > accepted? > > > > I don't have a sure which callback method will be called first from > install > > or from deploy plugin. > > So we can have a situation where deployment will be executed first. > > Can it be accepted? > > > > Of course when we will use the AbstractMavenLifecycleParticipant plugin > > must be configured as an extension - but it is not an issue I think. > > > > Any other suggestions ... > > > > Some of related issues: > > https://issues.apache.org/jira/browse/MINSTALL-102 > > https://issues.apache.org/jira/browse/MDEPLOY-226 > > > > [1] > > > > > https://github.com/apache/maven-clean-plugin/blob/master/src/main/java/org/apache/maven/plugins/clean/Cleaner.java#L514-L527 > > > > -- > > Sławomir Jaranowski > > > -- Sławomir Jaranowski
Re: [VOTE] Release Apache Maven 4.0.0-alpha-2
+1 tested with some of my projects sob., 15 paź 2022 o 02:19 Guillaume Nodet napisał(a): > I've staged a release candidate at > https://repository.apache.org/content/repositories/maven-1811 > > The binaries are available at: > > > https://repository.apache.org/service/local/repositories/maven-1811/content/org/apache/maven/apache-maven/4.0.0-alpha-2/ > > The tag is available at: > https://github.com/apache/maven/tree/maven-4.0.0-alpha-2 > > Please review and vote ! > > Cheers, > Guillaume Nodet > -- Sławomir Jaranowski
[ANN] Apache Maven EAR Plugin 3.3.0 Released
The Apache Maven team is pleased to announce the release of the Apache Maven EAR Plugin, version 3.3.0 This plugin generates Java EE Enterprise Archive (EAR) file. https://maven.apache.org/plugins/maven-ear-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-ear-plugin 3.3.0 You can download the appropriate sources etc. from the download page: https://maven.apache.org/plugins/maven-ear-plugin/download.html Release Notes - Maven EAR Plugin - Version 3.3.0 ** Bug * [MEAR-297] - failure when building javadoc: maven-plugin-tools-javadoc:jar:3.6.0 is missing * [MEAR-301] - wrong repackaging when defaultLibBundleDir start with dot ** New Feature * [MEAR-302] - jakarta EE 9 EAR compatibility * [MEAR-309] - Support JakartaEE 10 ** Improvement * [MEAR-298] - Improving EAR packaging performance with ZipFileSystem * [MEAR-319] - Remove generated MANIFEST from outdated resources * [MEAR-321] - Remove not implemented parameter - useBaseVersion ** Task * [MEAR-304] - Update dependencies used in IT tests * [MEAR-311] - Require Java 8 * [MEAR-318] - Require Maven 3.2.5 ** Dependency upgrade * [MEAR-310] - Upgrade Parent to 37 * [MEAR-312] - Upgrade Maven Verifier to 2.0.0-M1 * [MEAR-313] - Bump maven-filtering from 3.2.0 to 3.3.0 * [MEAR-314] - Bump plexus-archiver from 4.2.4 to 4.5.0 * [MEAR-315] - Bump maven-archiver from 3.5.1 to 3.6.0 * [MEAR-316] - Bump plexus-io from 3.2.0 to 3.4.0 * [MEAR-317] - Bump maven-shared-utils from 3.3.3 to 3.3.4 * [MEAR-320] - Bump plexus-utils from 3.3.0 to 3.4.2 Enjoy, -The Apache Maven team
[RESULT] [VOTE] Release Apache Maven EAR Plugin version 3.3.0
Hi, The vote has passed with the following result: +1: Michael Osipov, Tamás Cservenák, Olivier Lamy, Sylwester Lachiewicz, Hervé Boutemy PMC quorum: reached I will promote the source release zip file to Apache distribution area and the artifacts to the central repo. -- Sławomir Jaranowski
Re: [VOTE] Release Maven Plugin Tools 3.7.0
Next issues from me: https://issues.apache.org/jira/browse/MPLUGIN-430 https://issues.apache.org/jira/browse/MPLUGIN-431 Guillaume - do you agree to drop the current release and try again after fixing reported issues? I can take care of it. pon., 24 paź 2022 o 15:01 Konrad Windszus napisał(a): > Hi, > I created > https://issues.apache.org/jira/browse/MPLUGIN-429 and > https://issues.apache.org/jira/browse/MPLUGIN-428 for the superfluous > warnings related to missing Javadoc URLs. > > Sorry that this slipped through. > > Konrad > > > too many examples for this plugin broken links [1] > > I don't see it on > > On 2022/10/24 11:44:27 Slawomir Jaranowski wrote: > > Hi, > > > > Build ok. > > > > Documentation for new plugin-report:report has some issues > > - too many examples for this plugin broken links [1] > > - plugin-report:report is since 3.7 not 2.0 [2] > > > > New plugin-report:report with old deprecated parameters - creating new > we > > should not introduce deprecated items [2] > > > > Tested with m-install-p I have many warnings like: > > > > [WARNING] Could not get javadoc URL for type int of parameter lineLength > > from goal help: Resolving primitives is not supported. Binary name must > > contain at least one dot: int > > [WARNING] Could not get javadoc URL for type boolean of parameter > > installAtEnd from goal install: Resolving primitives is not supported. > > Binary name must contain at least one dot: boolean > > [WARNING] Could not get javadoc URL for type > > org.apache.maven.plugin.descriptor.PluginDescriptor of parameter > > pluginDescriptor from goal install: Found no javadoc site for > > org.apache.maven.plugin.descriptor.PluginDescriptor > > > > I didn't check it well enough before release ... now I'm not sure if we > > should publish this release > > > > [1] - > > > https://maven.apache.org/plugin-tools-archives/plugin-tools-LATEST/maven-plugin-report-plugin/index.html > > [2] - > > > https://maven.apache.org/plugin-tools-archives/plugin-tools-LATEST/maven-plugin-report-plugin/report-mojo.html > > > > > > > > czw., 20 paź 2022 o 10:48 Guillaume Nodet > napisał(a): > > > > > Hi, > > > > > > We solved 18 issues: > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317820=12344367 > > > > > > There are still a couple of issues left in JIRA: > > > > > > > https://issues.apache.org/jira/browse/?jql=project%20%3D%20MPLUGIN%20and%20resolution%20%3D%20Unresolved > > > > > > Staging repo: > > > https://repository.apache.org/content/repositories/maven-1814/ > > > > > > > https://repository.apache.org/content/repositories/maven-1814/org/apache/maven/plugin-tools/maven-plugin-tools/3.7.0/maven-plugin-tools-3.7.0-source-release.zip > > > > > > Source release checksum(s): > > > maven-plugin-tools-3.7.0-source-release.zip - SHA-512 : > > > > > > > de2aea68dc6645465184c3d1da40d5d0de1ee9c87743aade3668a4ce24ed9270445925e39b18a157f34e1698080ecc72066f670c47ce93f795b80fdede5475b1 > > > > > > Staging site: > > > https://maven.apache.org/plugin-tools-archives/plugin-tools-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 > > > > > > -- > > > > > > Guillaume Nodet > > > > > > > > > -- > > Sławomir Jaranowski > > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- Sławomir Jaranowski
Re: [VOTE] Maven Apache Shade Plugin 3.4.1
+1 Build by Maven 3 ok. Just as a curiosity - build project by Maven 4, some IT tests failed, I did not investigate it. [ERROR] * mshade-123/pom.xml [ERROR] * finalNameBuild-attached/pom.xml [ERROR] * MSHADE-340_shadedTestJarArtifactAttached/pom.xml [ERROR] * finalNameShade-attached/pom.xml [ERROR] * attached-artifact-type/pom.xml [ERROR] * finalNameShade/pom.xml [ERROR] * finalNameBuild/pom.xml [ERROR] * attach-after-lifecycle-fork/pom.xml pt., 21 paź 2022 o 23:00 Guillaume Nodet napisał(a): > Hi, > > We solved 7 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317921=12352285 > > There are still a couple of issues left in JIRA: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHADE%20AND%20resolution%20%3D%20Unresolved > > Staging repo: > https://repository.apache.org/content/repositories/maven-1815/ > > https://repository.apache.org/content/repositories/maven-1815/org/apache/maven/plugins/maven-shade-plugin/3.4.1/maven-shade-plugin-3.4.1-source-release.zip > > Source release checksum(s): > maven-shade-plugin-3.4.1-source-release.zip - SHA-512 : > > 677bbb062b442b4b1843bdfdd637398aea6c7e99c9eae3db476b9a90323e38f042384c8639ac12f50ad142e664ddd1e09ed1fe44f3dd5a5843023668660e5b8a > > Staging site: > https://maven.apache.org/plugins-archives/maven-shade-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 > > -- > > Guillaume Nodet > -- Sławomir Jaranowski
Re: [VOTE] Release Maven Plugin Tools 3.7.0
Hi, Build ok. Documentation for new plugin-report:report has some issues - too many examples for this plugin broken links [1] - plugin-report:report is since 3.7 not 2.0 [2] New plugin-report:report with old deprecated parameters - creating new we should not introduce deprecated items [2] Tested with m-install-p I have many warnings like: [WARNING] Could not get javadoc URL for type int of parameter lineLength from goal help: Resolving primitives is not supported. Binary name must contain at least one dot: int [WARNING] Could not get javadoc URL for type boolean of parameter installAtEnd from goal install: Resolving primitives is not supported. Binary name must contain at least one dot: boolean [WARNING] Could not get javadoc URL for type org.apache.maven.plugin.descriptor.PluginDescriptor of parameter pluginDescriptor from goal install: Found no javadoc site for org.apache.maven.plugin.descriptor.PluginDescriptor I didn't check it well enough before release ... now I'm not sure if we should publish this release [1] - https://maven.apache.org/plugin-tools-archives/plugin-tools-LATEST/maven-plugin-report-plugin/index.html [2] - https://maven.apache.org/plugin-tools-archives/plugin-tools-LATEST/maven-plugin-report-plugin/report-mojo.html czw., 20 paź 2022 o 10:48 Guillaume Nodet napisał(a): > Hi, > > We solved 18 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317820=12344367 > > There are still a couple of issues left in JIRA: > > https://issues.apache.org/jira/browse/?jql=project%20%3D%20MPLUGIN%20and%20resolution%20%3D%20Unresolved > > Staging repo: > https://repository.apache.org/content/repositories/maven-1814/ > > https://repository.apache.org/content/repositories/maven-1814/org/apache/maven/plugin-tools/maven-plugin-tools/3.7.0/maven-plugin-tools-3.7.0-source-release.zip > > Source release checksum(s): > maven-plugin-tools-3.7.0-source-release.zip - SHA-512 : > > de2aea68dc6645465184c3d1da40d5d0de1ee9c87743aade3668a4ce24ed9270445925e39b18a157f34e1698080ecc72066f670c47ce93f795b80fdede5475b1 > > Staging site: > https://maven.apache.org/plugin-tools-archives/plugin-tools-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 > > -- > > Guillaume Nodet > -- Sławomir Jaranowski
[VOTE] Release Maven Plugin Tools 3.7.0
Hi, We solved 42 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317820=12344367 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MPLUGIN%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key Staging repo: https://repository.apache.org/content/repositories/maven-1819/ https://repository.apache.org/content/repositories/maven-1819/org/apache/maven/plugin-tools/maven-plugin-tools/3.7.0/maven-plugin-tools-3.7.0-source-release.zip Source release checksum(s): maven-plugin-tools-3.7.0-source-release.zip - SHA-512 : 7a208c35d273ebaca83fcd1dace1c255b3e805bb5765de675792c1ed6ccd5b5dd1beb6782003e9162e925fa8ca8354b54dde15f252f50c497bfe4274c97974e3 Staging site: https://maven.apache.org/plugin-tools-archives/plugin-tools-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 -- Sławomir Jaranowski
Re: [VOTE] Release Maven Plugin Tools 3.7.0
niedz., 30 paź 2022 o 11:16 Michael Osipov napisał(a): > Am 2022-10-30 um 11:02 schrieb Slawomir Jaranowski: > > Hi, > > > > We solved 42 issues: > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317820=12344367 > > > > There are still a couple of issues left in JIRA: > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MPLUGIN%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key > > > > Staging repo: > > https://repository.apache.org/content/repositories/maven-1819/ > > > https://repository.apache.org/content/repositories/maven-1819/org/apache/maven/plugin-tools/maven-plugin-tools/3.7.0/maven-plugin-tools-3.7.0-source-release.zip > > > > Source release checksum(s): > > maven-plugin-tools-3.7.0-source-release.zip - SHA-512 : > > > 7a208c35d273ebaca83fcd1dace1c255b3e805bb5765de675792c1ed6ccd5b5dd1beb6782003e9162e925fa8ca8354b54dde15f252f50c497bfe4274c97974e3 > > > > > > Staging site: > > https://maven.apache.org/plugin-tools-archives/plugin-tools-LATEST/ > > > > Guide to testing staged releases: > > https://maven.apache.org/guides/development/guide-testing-releases.html > > > > Vote open for at least 72 hours. > > This is weird. It should have been 3.7.1. We burn versions when the vote > has been canceled. > > 3.7.0 - was never released as the last vote was canceled. So I restarted a new vote ... >From release procedure [1]: > If the vote is unsuccessful, the process will need to be restarted. Be sure to: > - drop your staging repository as described in Dropping a Repo. > - remove the release from the corresponding github release https://github.com/apache/maven-project/releases [1] https://maven.apache.org/developers/release/maven-project-release-procedure.html#check-the-vote-results But anyway, +1. > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- Sławomir Jaranowski
Clarify procedure for restarting releases
Hi, Current procedure of releases is unclear in case of restart releases. [1] I see two cases: - technical problem during release ... something goes wrong after SMC tag was created - canceled vote Technically we have many solutions: 1. - drop old tag and restart with the same version - no need other actions 2. - restart process with next version - don't touch wrong tag in repo - or drop old tag - rename release label in jira - or create next release and add only fixed issues for restart [1] https://maven.apache.org/developers/release/maven-project-release-procedure.html#check-the-vote-results -- Sławomir Jaranowski
Re: Clarify procedure for restarting releases
Hi, We are talking about a situation which happens very rarely - canceling a vote. Adding the next manual step like post process tagging only for one reason is not justified. I think that when we have multiple release labels for issues and one will be released and second not, can be misunderstood for final users. Not every user follows the dev list and voting result. In such a case simply delete tag and create next with next release run with the same label is easy and possible. By deleting / moving tag to another commit we don't change git history - all commits are present in history we only change a label for the next commit. pon., 31 paź 2022 o 07:41 Romain Manni-Bucau napisał(a): > Le lun. 31 oct. 2022 à 07:34, Hervé Boutemy a > écrit : > > > if pushing the tag is an additional manual step after the vote, > experience > > shows that it will be forgotten > > > > Well it worked well for multiple projects so I'm sure it can work for > maven. > Dist is another deal and we can also invest automating it IMHO since using > nexus there is no value handling it manually at all next to the standard > maven (build) release procedure. > > > > > > and even if we check its existence in dist-tool and publish what is > > missing, > > people will have to look at the report: > > > > > https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-dist-tool/job/ > > master/site/dist-tool-check-errors.html > > < > https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-dist-tool/job/master/site/dist-tool-check-errors.html > > > > > > as you can see, the existing manual steps are already not fully followed, > > I > > don't want to be the one who fixes missed steps > > > > Le dimanche 30 octobre 2022, 21:40:00 CET Olivier Lamy a écrit : > > > +1 > > > > > > Exactly if the problem is the tag, we simply don’t push the tag. > > > m-release-p has options for that (don’t push and local clone). > > > The tag is not needed as we are supposed to vote sources tarball. > > > This even make the release process faster as you avoid some extra > network > > > operations such another clone.. > > > If really asking by someone the tag can be pushed in a fork > > > > > > On Mon, 31 Oct 2022 at 6:32 am, Guillaume Nodet > > wrote: > > > > I don't see the point of burning releases. Imho, this has a negative > > > > impact on users for no benefits. > > > > If the problem is just about not rewriting the git history, we could > > > > simply > > > > tag manually once the vote has succeeded (or find a way to delay > > pushing > > > > the tag even if the tag has been created in your local repo when the > > > > release is built). > > > > > > > > Le dim. 30 oct. 2022 à 20:43, Michael Osipov a > > > > > > > > écrit : > > > > > Am 2022-10-30 um 20:32 schrieb Elliotte Rusty Harold: > > > > > > On Sun, Oct 30, 2022 at 6:53 PM Michael Osipov < > > micha...@apache.org> > > > > > > > > > > wrote: > > > > > >> Am 2022-10-30 um 19:39 schrieb Elliotte Rusty Harold: > > > > > >>> IMO A failed release should not burn an external facing version > > > > > >>> number. If it does, then the release process is flawed and > needs > > to > > > > > > > > be > > > > > > > > > >>> fixed. > > > > > >> > > > > > >> Why? This I don't understand. From ASF PoV only the source > release > > > > > >> ZIP > > > > > >> file is relevant. Everything else isn't public. The Git tag does > > not > > > > > >> matter actually. > > > > > > > > > > > > If it's not an externally facing version number as used in the > > pom.xml > > > > > > dependency/version element, then it doesn't really matter. I > > thought > > > > > > we were talking about restarting a release requiring a new > version > > > > > > number because the git tag is tied to the version number and the > > git > > > > > > tag can't be deleted or repointed. However if that's not the > case, > > > > > > then I agree it doesn't really matter. > > > > > > > > > > While I have never actively deleted tags, I consider this as > > rewriting > > > > > history what two different source trees appear under the same tag. > > This > > > > > does not sound write. We don't rewrite history and maintain a > linear > > > > > branch strategy whatever is released from master. > > > > > > > > > > > > > > > > - > > > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > > > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > > > > -- > > > > > > > > Guillaume Nodet > > > > > > > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > -- Sławomir Jaranowski
Artifact Resolver configuration
Hi, Artifact Resolver has many useful configuration options [1] Most of these properties must be provided by user or system properties. Some are extracted from settings.xml Providing such many settings by command line for every execution is very uncomfortable. We can put those in MAVEN_OPTS by shell profile or by .mavenrc But in this case all values are put in the command line by mvn script, command line length can be limited ... and we have next place to mange Maven configuration What do you think about allow configure Resolver by settings.xml - it looks the most natural way, because settings.xml contains location of local repository which is affected by Resolver - it will be easier manage whole configuration in one place Some of the Resolver configurations can have complex type like for: aether.connector.http.headers is Map Can we provide such configuration by user/system properties? Propositions: 1. Pass profiles/profile/properties to Resolver configuration - all as is - only beginning with aether.* - what with complex type? 2. Introduce new elements in settings.xml - profiles/profile/resolverConfig - with global properties - profiles/profile/repositories/repository/resolverConfig - for properties supports repo id 3. Use existing servers/server/configuration for properties supports repo id Any other ideas, hints? [1] https://maven.apache.org/resolver/configuration.html -- Sławomir Jaranowski
Re: Artifact Resolver configuration
Hi, Agree to not expose all LOW LEVEL configurations. So we can think - what is LOW and HIGH level - "most common" - how to map LOW to HIGH I see that maven.resolver.transport and maven.resolver.locking can be as HIGH level And the question is still open - how users can manage HIGH level options? maybe we can allow in profiles/profile/properties maven.resolver.*? maven.resolver.transport - native can benefit with - "included checksums" [1] I think that options like aether.enhancedLocalRepository.split* can be attractive for users [1] https://maven.apache.org/resolver/included-checksum-strategies.html czw., 27 paź 2022 o 20:00 Tamás Cservenák napisał(a): > Howdy, > > I already thought about this, and probably shared some thoughts (that may > have slipped, or did not share on ML?). > > In short: personally, I consider these "resolver configurations" LOW LEVEL > settings that ARE exposed to those users who are adventurous, but in > general, Maven should provide sane(er) HIGH LEVEL config support for them. > > My usual example: > resolver locking: https://github.com/apache/maven/pull/762 > resolver transport: https://github.com/apache/maven/pull/711 > and so on, and so on > > In short, while you CAN use zillion of -D's to set locking or achieve > anything you want, maven may/should offer out of the box "high level" > (easier to comprehend, "usual" setup, yada yada) config, that is much > easier for users to apply. > > === > > TL;DR: resolver configuration is "low level" for adventurous developers, > and is exposed for them. OTOH Maven should offer "most common" (or > anticipated) higher level and easier to use config options for some (IMHO > not all) resolver config. > > > HTH > T > > On Thu, Oct 27, 2022 at 7:35 PM Slawomir Jaranowski < > s.jaranow...@gmail.com> > wrote: > > > Hi, > > > > Artifact Resolver has many useful configuration options [1] > > > > Most of these properties must be provided by user or system properties. > > Some are extracted from settings.xml > > > > Providing such many settings by command line for every execution is very > > uncomfortable. > > > > We can put those in MAVEN_OPTS by shell profile or by .mavenrc > > But in this case all values are put in the command line by mvn script, > > command line length can be limited ... > > and we have next place to mange Maven configuration > > > > What do you think about allow configure Resolver by settings.xml > > - it looks the most natural way, because settings.xml contains location > of > > local repository which is affected by Resolver > > - it will be easier manage whole configuration in one place > > > > Some of the Resolver configurations can have complex type like for: > > aether.connector.http.headers is Map > > Can we provide such configuration by user/system properties? > > > > Propositions: > > > > 1. Pass profiles/profile/properties to Resolver configuration > > - all as is > > - only beginning with aether.* > > - what with complex type? > > > > 2. Introduce new elements in settings.xml > > > > - profiles/profile/resolverConfig - with global properties > > - profiles/profile/repositories/repository/resolverConfig - for > properties > > supports repo id > > > > 3. Use existing servers/server/configuration for properties supports repo > > id > > > > > > Any other ideas, hints? > > > > > > [1] https://maven.apache.org/resolver/configuration.html > > > > -- > > Sławomir Jaranowski > > > -- Sławomir Jaranowski
Re: [VOTE] Release Maven SCM version 2.0.0-M3
+1 wt., 25 paź 2022 o 21:58 Michael Osipov napisał(a): > Hi, > > We solved 2 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317828=12352129 > > There are still a couple of issues left in JIRA: > https://issues.apache.org/jira/projects/SCM/issues > > Staging repo: > https://repository.apache.org/content/repositories/maven-1816/ > > https://repository.apache.org/content/repositories/maven-1816/org/apache/maven/scm/maven-scm/2.0.0-M3/maven-scm-2.0.0-M3-source-release.zip > > Source release checksum(s): > maven-scm-2.0.0-M3-source-release.zip > sha512: > > f471a1d6709ab92925bfa78a25ff5f7839c1b7c3baf738777024a2958def41bfb1ab1d30c72464163d1181283d205f60aa14b6eacf298cd6d145fde224a45eba > > Staging site: > https://maven.apache.org/scm-archives/scm-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: Install / Deploy plugins at the end
czw., 20 paź 2022 o 09:04 Tamás Cservenák napisał(a): > Howdy, > > I cannot reproduce any of the issues you linked, moreover all the other > issues are IMHO non reproducible with m-install-p 3.0.1 and m-deploy-p > 3.0.0. > > You are right - issues should be closed - I will review it. > There is ONE issue that still stands, and it is the one you mention: when > m-install-p/m-deploy-p is not part of a module build at all, but IMHO is > simple fix. > > No need for any magic, fix is almost trivial... > > Any more details? > T > > On Wed, Oct 19, 2022 at 11:22 PM Slawomir Jaranowski < > s.jaranow...@gmail.com> > wrote: > > > I'm. > > > > In plugins each processed module are marked with one of flags: SKIPPED, > > INSTALLED, TO_BE_INSTALLED or SKIPPED, DEPLOYED, TO_BE_DEPLOYED > > > > And finally we check if all modules have a flag set to detect end of > > session in method allProjectsMarked > > But if one module not used install / deploy plugins at all - nothing > will > > be installed / deployed. > > > > To reproduce - in multimodule project - bind install / deploy plugin to > > none phase in one of modules. > > > > > > > > śr., 19 paź 2022 o 22:59 Tamás Cservenák > napisał(a): > > > > > Slawek, > > > > > > Are you sure those issues still stand for 3.0.x of plugins? > > > > > > T > > > > > > > > > On Wed, Oct 19, 2022, 22:07 Slawomir Jaranowski < > s.jaranow...@gmail.com> > > > wrote: > > > > > > > Hi, > > > > > > > > I'm looking for how to resolve issues connected with the feature > > > > installAtEnd / deployAtEnd of install and deploy plugins. > > > > > > > > We have a similar feature in clean plugin where it is implemented by > > > > wrapping session.getRequest().getExecutionListener() [1] > > > > Because ExecutionListener on request is not chained by default it > will > > be > > > > difficult implement the next wrappers in two plugins. > > > > > > > > In current implementation we assume that install or deploy plugins > are > > > > executed in all modules, > > > > but it can not be true e.g. one module can use different packaging > > > > which doesn't have those plugins in their lifecycle > > > > so detecting the last executing module does not work. > > > > > > > > We can also have skipped or not used install / deploy plugins in the > > last > > > > executed module. > > > > > > > > I'm thinking of using AbstractMavenLifecycleParticipant to detect the > > end > > > > of a Maven session and to finish the job in afterSessionEnd > callback. > > > > > > > > But in this way I see another issue - > > > > AbstractMavenLifecycleParticipant.afterSessionEnd method is called > > after > > > > session.request.ExecutionListene which prints a summary of whole > build, > > > > so we have additional tasks not computed in the build summary - Can > it > > be > > > > accepted? > > > > > > > > I don't have a sure which callback method will be called first from > > > install > > > > or from deploy plugin. > > > > So we can have a situation where deployment will be executed first. > > > > Can it be accepted? > > > > > > > > Of course when we will use the AbstractMavenLifecycleParticipant > plugin > > > > must be configured as an extension - but it is not an issue I think. > > > > > > > > Any other suggestions ... > > > > > > > > Some of related issues: > > > > https://issues.apache.org/jira/browse/MINSTALL-102 > > > > https://issues.apache.org/jira/browse/MDEPLOY-226 > > > > > > > > [1] > > > > > > > > > > > > > > https://github.com/apache/maven-clean-plugin/blob/master/src/main/java/org/apache/maven/plugins/clean/Cleaner.java#L514-L527 > > > > > > > > -- > > > > Sławomir Jaranowski > > > > > > > > > > > > > -- > > Sławomir Jaranowski > > > -- Sławomir Jaranowski
Upcoming Maven Verifier release - 2.0.0-M1
Hi, I'm preparing for the next release of Maven Verifier. We have cleaned pieces of code, many methods are now deprecated. [1] There are still a couple of issues for 2.0.0 version [2] I want to release the M1 version to allow easier switching for version 2.0.0 which will have removed old methods. Most of the tasks are needed for switching Maven Core integration tests to JDK 8 and JUnit 5. [3] Thanks to Guillaume I'm going to release it on Wednesday (21.09) or Thursday (22.09), any remarks are welcome. [1] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12352314 [2] https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20maven-verifier-2.0.0 [3] https://github.com/apache/maven-integration-testing/pull/176 -- Sławomir Jaranowski
Re: [VOTE] Release Apache Maven Shade Plugin version 3.4.0
+1 niedz., 11 wrz 2022 o 12:38 Karl Heinz Marbaise napisał(a): > Hi, > > We solved 6 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317921=12351491 > > There are still a couple of issues left in JIRA: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHADE%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC%2C%20updated%20DESC > > > Staging repo: > > https://repository.apache.org/content/repositories/maven-1806/org/apache/maven/plugins/maven-shade-plugin/3.4.0/maven-shade-plugin-3.4.0-source-release.zip > > Source release checksum(s): > maven-shade-plugin-3.4.0-source-release.zip sha512: > > 3470a1316f65b1efff7309a9890f1c4d70ce549919004e682565a62cb204b3925ba325b62818f6fc3390e5aae55fb15b631392965bfc97fc3bf2fafe6e0bc797 > > Staging site: > https://maven.apache.org/plugins-archives/maven-shade-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 > > Kind regards > Karl Heinz Marbaise > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- Sławomir Jaranowski
[VOTE] Release Apache Maven JAR Plugin version 3.3.0
Hi, We solved 6 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317526=12351126 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MJAR%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC Staging repo: https://repository.apache.org/content/repositories/maven-1807/ https://repository.apache.org/content/repositories/maven-1807/org/apache/maven/plugins/maven-jar-plugin/3.3.0/maven-jar-plugin-3.3.0-source-release.zip Source release checksum(s): maven-jar-plugin-3.3.0-source-release.zip - SHA-512 : 867aa9ac437b9d2fc9fed67373bdf66ab1992469563c896e1006ca032a0af3b9b055834b9b0d3b28de83ddc1bede8e42a654d5649e5dd2d5ac53b4bc55eeed31 Staging site: https://maven.apache.org/plugins-archives/maven-jar-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 -- Sławomir Jaranowski
[VOTE] Maven Shared Maven Common Artifact Filters 3.3.2
Hi, We solved 2 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12352116 There are still one 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-common-artifact-filters Staging repo: https://repository.apache.org/content/repositories/maven-1808/ https://repository.apache.org/content/repositories/maven-1808/org/apache/maven/shared/maven-common-artifact-filters/3.3.2/maven-common-artifact-filters-3.3.2-source-release.zip Source release checksum(s): maven-common-artifact-filters-3.3.2-source-release.zip - SHA-512 : 8fda12113b179a88bd42f554b7515b0b508af7e6968f5d371eb26a726d54e52143d75c465470c531dd40ae16bbc3f2602c748d2a36be60ae83a87fcdcfd9ed86 Staging site: https://maven.apache.org/shared-archives/maven-common-artifact-filters-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 -- Sławomir Jaranowski
[RESULT] [VOTE] Release Apache Maven Verifier version 2.0.0-M1
Hi, The vote has passed with the following result: +1 : Herve Boutemy, Michael Osipov, Tamás Cservenák PMC quorum: reached I will promote the source release zip file to Apache distribution area and the artifacts to the central repo. -- Sławomir Jaranowski
[ANN] Apache Maven Verifier 2.0.0-M1 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Verifier, version 2.0.0-M1 This library provides a test harness for Maven integration tests. https://maven.apache.org/shared/maven-verifier/ You should specify the dependency in your project: org.apache.maven.shared maven-verifier 2.0.0-M1 You can download the appropriate sources etc. from the download page: https://maven.apache.org/shared/maven-verifier/download.html Release Notes - Maven Shared Components - Version maven-verifier-2.0.0-M1 ** Improvement * [MSHARED-690] - Change package from org.apache.maven.it to org.apache.maven.shared.verifier * [MSHARED-1124] - Add new version of methods filterFile and newDefaultFilterMap * [MSHARED-1125] - Require Maven args to be provided one by one * [MSHARED-1127] - Remove main method from Verifier * [MSHARED-1128] - Deprecate all executeGoal(s) methods * [MSHARED-1129] - Replace CLI options with CLI args * [MSHARED-1134] - Remove / deprecate internal debug mode in Verifier * [MSHARED-1135] - Deprecate Verifier#setMavenDebug(boolean) for removal * [MSHARED-1137] - Revise Verifier#getDefaultMavenHome()/#getExecutable() * [MSHARED-1142] - Remove e.getMessage() duplication when e is passed as object ** Dependency upgrade * [MSHARED-1075] - Upgrade Parent to 36 * [MSHARED-1089] - Update maven-verifier to JDK 8 / Junit 5 * [MSHARED-1126] - Bump maven-shared-components from 36 to 37 * [MSHARED-1148] - Bump junit-jupiter from 5.9.0 to 5.9.1 Enjoy, -The Apache Maven team
Re: What is the recommended approach to get org.apache.maven.repository.RepositorySystem in 3.8.6?
Hi, Maybe it is time to deprecate org.apache.maven.repository.RepositorySystem We should document replacement for each method. pon., 26 wrz 2022 o 15:04 Tamás Cservenák napisał(a): > Howdy, > > As I see your use case "in the particular case we \"simply\" resolve an > artifact with its dependencies" is basically very much same as m-compiler-p > does to get annotation processors. > Hence, I did this just to see: > https://github.com/apache/maven-compiler-plugin/pull/151 > > Hope it helps > T > > On Mon, Sep 26, 2022 at 1:05 PM Christoph Läubrich > wrote: > > > THanks for the hints, in general I'm currently cleanup/refactor Tycho > > but still there are places where maven-compat seems required (and the > > tests is such a part sadly). > > > > Tycho requires maven-3.8.6 as a minimum and hopefully will move on to > > maven 3.9.x once it is released (and we got rid of the compat stuff). > > > > I think I'll try as you suggested and get rid of > > org.apache.maven.repository.RepositorySystem in favor of > > org.eclipse.aether.RepositorySystemSession, just need to check how this > > new stuff all works, in the particular case we "simply" resolve an > > artifact with its dependencies using > > > > @Requirement > > private RepositorySystem repositorySystem; > > > > org.apache.maven.repository.RepositorySystem.createArtifact(...) > > > > and > > > > > > > org.apache.maven.repository.RepositorySystem.resolve(ArtifactResolutionRequest) > > > > calls ... > > > > > > Am 26.09.22 um 12:47 schrieb Tamás Cservenák: > > > Howdy, > > > > > > you did not specify what is what you exactly look for but in > general: > > > definitely avoid maven-compat (maven2 support). > > > > > > Your best bet is to: > > > - NOT support older Maven then 3.1, then you save yourself from > > > aether/resolver package change (so no need for things like > > > https://github.com/apache/maven-artifact-transfer and alike) > > > - go directly for resolver API > > (org.eclipse.aether.RepositorySystemSession > > > and related ones) -- this is the recommended way today (as Maven itself > > > "lifted" minimal Maven version to 3.1+ as well, Maven 3.0 is dead and > to > > be > > > completely forgotten). > > > - maven 4 will introduce new API ( > > https://github.com/apache/maven/pull/703) > > > but only in 4+ versions (and will provide a "window" for > > plugins/extensions > > > to move from resolver-direct to API use), so several Maven 4.x versions > > > will support both: "direct" resolver access but also provide API as > well. > > > At one point, maven "core" (never meant as "API") access will be shut > > off. > > > > > > also, take a peek at this (and related) pages > > > > > > https://cwiki.apache.org/confluence/display/MAVEN/Maven+Ecosystem+Cleanup > > > > > > So, if you are in position to ignore Maven 3.0, then you are free to > use > > > resolver API directly w/o issue. True, in future, migration to Maven 4 > > API > > > will be inevitable, but until core access is not shut down (no exact > > > timeline for it), you are fine. Again, your mileage may vary, as the > > > interface you refer to is really huge... > > > > > > > > > HTH > > > T > > > > > > On Mon, Sep 26, 2022 at 12:07 PM Christoph Läubrich < > m...@laeubi-soft.de > > > > > > wrote: > > > > > >> I'm currently writing a test for a component that requires > > >> > > >> org.apache.maven.repository.RepositorySystem > > >> > > >> the problem is that it seems the only implementation of this is > > >> LegacyRepositorySystem that is part of maven-compat (and thus I'd like > > >> to avoid adding that as a dependency) > > >> > > >> So I see two options: > > >> > > >> 1) There is a new alterantive that implements > > >> org.apache.maven.repository.RepositorySystem but I just don't know > > about? > > >> > > >> 2) I could try to refactor my code to not using > > >> org.apache.maven.repository.RepositorySystem, but what should be the > > >> alternative? > > >> > > >> org.apache.maven.repository.RepositorySystem is not deprecated and I > > >> can't see any note that something else should be used instead... > > >> > > >> any hints? > > >> > > >> - > > >> 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 > > > > > -- Sławomir Jaranowski
[VOTE] Release Apache Maven Verifier version 2.0.0-M1
Hi, We solved 14 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12352314 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-verifier%20ORDER%20BY%20key%20DESC Staging repo: https://repository.apache.org/content/repositories/maven-1809/ https://repository.apache.org/content/repositories/maven-1809/org/apache/maven/shared/maven-verifier/2.0.0-M1/maven-verifier-2.0.0-M1-source-release.zip Source release checksum(s): maven-verifier-2.0.0-M1-source-release.zip - SHA-512 : 79f5bd400f67bff2832dae5b61297be6bcee0db6e3668ac7245f5493664db7b8e047f7442a1a053a2a4c931790e32cafd6556f3990e2e6c8aafbc6a72ccf3889 Staging site: https://maven.apache.org/shared-archives/maven-verifier-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 -- Sławomir Jaranowski
[RESULT] [VOTE] Release Apache Maven JAR Plugin version 3.3.0
Hi, The vote has passed with the following result: +1 : Jorge Solórzano, Sylwester Lachiewicz, Herve Boutemy, Tamás Cservenák, Michael Osipov, Karl Heinz Marbaise, Olivier Lamy PMC quorum: reached I will promote the source release zip file to Apache distribution area and the artifacts to the central repo. -- Sławomir Jaranowski
[RESULT] [VOTE] Maven Shared Maven Common Artifact Filters 3.3.2
Hi, The vote has passed with the following result: +1 : Sylwester Lachiewicz, Tamás Cservenák, Herve Boutemy, Michael Osipov, Karl Heinz Marbaise, Olivier Lamy PMC quorum: reached I will promote the source release zip file to Apache distribution area and the artifacts to the central repo. -- Sławomir Jaranowski
[ANN] Maven JAR Plugin 3.3.0 released
The Apache Maven team is pleased to announce the release of the Maven JAR Plugin version 3.3.0. https://maven.apache.org/plugins/maven-jar-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-jar-plugin 3.3.0 Release Notes - Maven JAR Plugin - Version 3.3.0 ** Bug * [MJAR-275] - outputTimestamp not applied to module-info; breaks reproducible builds ** Task * [MJAR-278] - Update plugin (requires Maven 3.2.5+) * [MJAR-280] - Java 8 as minimum ** Dependency upgrade * [MJAR-288] - Upgrade Parent to 36 * [MJAR-290] - Update Plexus Utils to 3.4.2 * [MJAR-291] - Upgrade Parent to 37 Enjoy, -The Apache Maven team
[ANN] Maven Shared Maven Common Artifact Filters 3.3.2 Released
The Apache Maven team is pleased to announce the release of Maven Shared Maven Common Artifact Filters 3.3.2 component. Site: https://maven.apache.org/shared/maven-common-artifact-filters/ Release Notes - Maven Shared Components - Version maven-common-artifact-filters-3.3.2 ** Bug * [MSHARED-1130] - PatternIncludesArtifactFilters raising NPE for patterns w/ wildcards and artifactoid w/ null on any coordinate ** Dependency upgrade * [MSHARED-1131] - Upgrade Parent to 37 and cleanup Have fun - The Apache Maven Team
Re: ASF Source Assembly now contains .gitignore and .gitattributes
Hi, Also apache-rat-plugin use .gitignore for skipping verification pt., 16 wrz 2022 o 11:14 Michael Osipov napisał(a): > Am 2022-09-16 um 11:03 schrieb Vladimir Sitnikov: > >> “.gitignore” and “.gitattributes” files > > > > .gitignore and .gitattributes can easily be helpful during the build, so > it > > does sound strange to exclude them. > > > > For instance, Apache Calcite uses .gitattribute to configure that > specific > > files should have an "executable" bit in the resulting tar.gz archive: > > > https://github.com/apache/calcite/blob/e41555f568510df04d3883516b2195393a93426d/.gitattributes#L20-L21 > > If one deletes the .gitattributes file, the resulting tar.gz will be > broken. > > > > It does sound strange to me to exclude .gitattributes and .gitignore on > the > > basis of "SCM specific metadata". > > This is something I need to crunch on. Thanks for raising... > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > -- Sławomir Jaranowski
Re: [RAT] release 0.15?
Hi, RAT plugin is maintained by Apache Creadur team https://projects.apache.org/committee.html?creadur wt., 13 wrz 2022 o 19:05 Gary Gregory napisał(a): > Hi Maven, > > Any chance of finishing up RAT 0.15 soon? > > Gary > -- Sławomir Jaranowski
Re: [DISCUSS] Automatically format and sort imports
Hi, Generally I'm ok for such automatic tasks - we should test if the provided configuration for the IDE is completed and when we execute reformat code in the IDE we will have the same result. śr., 12 paź 2022 o 18:51 Tamás Cservenák napisał(a): > +1 for this. Tested on resolver, that has many old/untouched and hence, > badly formatted sources. > > T > > On Wed, Oct 12, 2022, 18:23 Guillaume Nodet wrote: > > > I'd like to propose merging the following PRs: > > * https://github.com/apache/maven-shared-resources/pull/1 > > * https://github.com/apache/maven-site/pull/329 > > * https://github.com/apache/maven/pull/824 > > * https://github.com/apache/maven-resolver/pull/147 > > ... and more to come > > > > The idea is to use plugins to automatically reformat the source code and > > sort imports to obey the maven coding style. > > The first PR adds the necessary resources to maven-shared-resources : a > new > > header file, as there's a requirement to put the header at the very > > beginning for the import sorter plugin to work correctly (else it > considers > > the license comment to be part of comment headers and screws the > > formatting), and the eclipse xml formatter plugin. > > The second PR updates the web site to point to that file which would be > in > > git instead of on the maven web site, and also updates the instruction > for > > IDEA since it has been supporting the eclipse xml config for years now). > > The third and fourth PRs are updates on maven and maven-resolver to apply > > those two plugins. > > > > Those plugins have been used on mvnd and maven-build-cache-extension > > already, although they are not using a single shared resource that would > be > > added by the first PR. Hence mvnd is still using its previous coding > > style. > > > > Another point is that those plugins are fast and only do not process > files > > if they have been already processed and untouched since the last build. > So > > from a daily development pov, this is transparent and does not incur any > > additional processing time during the build (or not much really). > > > > Cheers, > > Guillaume > > > -- Sławomir Jaranowski
Re: [DISCUSS] Change maven code style
+1 for moving braces to the end line, it is difficult especially with
lambda expression
śr., 12 paź 2022 o 18:52 Tamás Cservenák napisał(a):
> +1 for this formatting change.
>
> T
>
> On Wed, Oct 12, 2022, 18:23 Guillaume Nodet wrote:
>
> > Related to the discussion about automatically formatting and sorting
> > imports, I think it would be nice, given the big reformat commits if
> those
> > PRs are to be merged, to eventually discuss some changes to those code
> > style. In particular, I found out that the code is very sparse and my
> > screen is more wide than height, which means I can usually only see 30-40
> > lines of code, where sometime half of them do not really carry any
> semantic
> > (open braces, or things like close brace + else + open brace on 3 lines).
> > This makes me scroll a lot even on quite small methods to be able to read
> > the full code, and that's a pain imho.
> > So I'd like to propose the following changes that would make maven code
> > more readable imho (and also closer to the usual java coding style) :
> > * move open braces to the end of the previous line on all places
> > * allow the else keyword to be directly following a closing brace to
> > allow "} else {" to be on the same line
> > * eventually relax a bit the checkstyle line length as described in
> > https://github.com/gnodet/maven-shared-resources/pull/2. This has not
> > much
> > effect, as the formatter will automatically format the lines and wrap
> them
> > at 120. However, in certain cases, the formatter can find in difficult to
> > wrap the line (for example with a variable declaration and cast with a
> > fully qualified name) and there is either a need to manually force the
> wrap
> > (using an end of line comment for example) or disabling the check with a
> > @SuppressWarning( "checkstyle:LineLength" ) annotation. This change only
> > removes the checks so that in those rare cases, the formatter can be left
> > without any need to force things.
> >
> > If this is to be accepted, I'd amend the PRs from the other thread to
> > follow those changes.
> >
> > Cheers,
> > Guillaume
> >
>
--
Sławomir Jaranowski
Re: [DISCUSS] Automatically format and sort imports
czw., 13 paź 2022 o 17:41 Guillaume Nodet napisał(a): > So the plugin I'm using actually has a validate goal which won't do any > formatting, but simply fail the build if the code is not correctly > formatted. > So it should be easy add that goal in PRs. Any PR will simply quickly fail > if the code is not correctly formatted. Is that what you have in mind ? > > +1 for simply checking during build, formatting should be done by developer, nevermind if using plugin or by IDE It can work like checkstyle. -- Sławomir Jaranowski
Re: [DISCUSS] Release Maven 4.0.0-alpha-1 this week
For failed release I would prefer - revert commits if needed - we will have history - remove tag try again :-) If we bump versions only caused by technical problems during release we need to change / create labels in jira, move labeled issues and so on And we can have questions why some versions are missing. sob., 15 paź 2022 o 13:31 Benjamin Marwell napisał(a): > Unpopular opinion: > Deactivate automatic push. If release:perform went well, push main and the > tags. > > Besides, push --delete works for tags, too (if PMC agrees). > I doubt there are already forks from the tag active anywhere. > But yes, bumping the version is what we used to do in this case. > > - Ben > > > Am Sa., 15. Okt. 2022 um 00:31 Uhr schrieb Guillaume Nodet < > gno...@apache.org>: > > > > The release:prepare has succeeded but the release:perform failed. > > Hence, the tag has been created on github and can't be deleted. > > > > Le sam. 15 oct. 2022 à 00:26, Gary Gregory a > > écrit : > > > > > Why are you bumping the version if it failed? > > > > > > Gary > > > > > > On Fri, Oct 14, 2022, 18:13 Guillaume Nodet wrote: > > > > > > > Just FYI, I've attempted to release 4.0.0-alpha-1, but it failed. > I'll > > > try > > > > to cut another version once the problems are resolved. So > 4.0.0-alpha-1 > > > is > > > > a burnt version and next attempt will be 4.0.0-alpha-2. Stay tuned ! > > > > > > > > Le lun. 10 oct. 2022 à 22:32, Guillaume Nodet a > > > écrit > > > > : > > > > > > > > > The master branch contains a lot of things and has not been > released > > > for > > > > a > > > > > long time. With the new addition of the v4 api, I think it would be > > > good > > > > to > > > > > get something out of the door to gather some feedback from users > and > > > also > > > > > allow migrating some components and plugins to the new API. > > > > > > > > > > So unless there's an objection, I'd like to start a release process > > > later > > > > > this week after [1] and [2] are merged. > > > > > > > > > > Thoughts ? > > > > > > > > > > Cheers, > > > > > Guillaume Nodet > > > > > > > > > > [1] https://github.com/apache/maven/pull/806 > > > > > [2] https://github.com/apache/maven/pull/819 > > > > > > > > > > > > > > > > > > -- > > > > > > > > Guillaume Nodet > > > > > > > > > > > > > -- > > > > Guillaume Nodet > > - > 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 Apache Maven 4.0.0-alpha-2
Hi, Link for biaries is: https://repository.apache.org/content/repositories/maven-1811/org/apache/maven/apache-maven/4.0.0-alpha-2/ By the way binaries should be available at distribution area also ... https://dist.apache.org/repos/dist/dev/maven/ Did you publish a staging Maven site somewhere? sob., 15 paź 2022 o 02:19 Guillaume Nodet napisał(a): > I've staged a release candidate at > https://repository.apache.org/content/repositories/maven-1811 > > The binaries are available at: > > > https://repository.apache.org/service/local/repositories/maven-1811/content/org/apache/maven/apache-maven/4.0.0-alpha-2/ > > The tag is available at: > https://github.com/apache/maven/tree/maven-4.0.0-alpha-2 > > Please review and vote ! > > Cheers, > Guillaume Nodet > -- Sławomir Jaranowski
Re: [VOTE] Release Apache Maven 4.0.0-alpha-2
Why alpha-2, we didn't release alpha-1. Even if some technical problems occur during release we should reuse the final tag. In jira we have a label for alpha-1. sob., 15 paź 2022 o 02:19 Guillaume Nodet napisał(a): > I've staged a release candidate at > https://repository.apache.org/content/repositories/maven-1811 > > The binaries are available at: > > > https://repository.apache.org/service/local/repositories/maven-1811/content/org/apache/maven/apache-maven/4.0.0-alpha-2/ > > The tag is available at: > https://github.com/apache/maven/tree/maven-4.0.0-alpha-2 > > Please review and vote ! > > Cheers, > Guillaume Nodet > -- Sławomir Jaranowski
Re: [Surefire] Toolchains seem to be ignored if forkCount > 1
Hi Niels,
This issue can be similar to your:
https://issues.apache.org/jira/browse/SUREFIRE-2073
pt., 2 wrz 2022 o 17:41 Niels Basjes napisał(a):
> Hi,
>
> I was working on a project and ran into a problem.
> I have reduced the reproduction to the smallest I could:
>
> https://github.com/nielsbasjes/MavenSurefireForkCount
>
> Summary:
> - I use Ubuntu 20.04
> - I have Java 11 as the default (i.e. in path and JAVA_HOME).
> - I also have Java 8 and Java 17 installed which I use via toolchains.
> - I have both the compiler and surefire plugins configured via
> pluginManagement ("large" project trying to avoid duplicating the
> configurations).
> - A specific module in my project can only run on Java 17 because of a
> dependency.
>
> When I build and test the project it works fine.
> When I try to run the surefire plugin with a forkCount > 1 it fails over
> binary class versions: It tries to run the Java 17 class file using the
> Java 11 runtime which obviously won't work.
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M7:test (default-test)
> on project toolchainer: Execution default-test of goal
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M7:test failed:
> java.lang.UnsupportedClassVersionError: nl/basjes/bugreport/TestApp has
> been compiled by a more recent version of the Java Runtime (class file
> version 61.0), this version of the Java Runtime only recognizes class file
> versions up to 55.0 -> [Help 1]
>
> What am I doing wrong?
> Or should I submit this as a bugreport?
>
> --
> Best regards / Met vriendelijke groeten,
>
> Niels Basjes
>
--
Sławomir Jaranowski
Re: [VOTE] Release Apache Maven PMD Plugin version 3.19.0
+1 czw., 1 wrz 2022 o 12:07 Andreas Dangel napisał(a): > Hi, > > We solved 2 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12352255=Text=12317621 > > There are still a couple of issues left in JIRA: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MPMD%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC > > Staging repo: > https://repository.apache.org/content/repositories/maven-1804/ > > https://repository.apache.org/content/repositories/maven-1804/org/apache/maven/plugins/maven-pmd-plugin/3.19.0/maven-pmd-plugin-3.19.0-source-release.zip > > Source release checksum(s): > maven-pmd-plugin-3.19.0-source-release.zip sha512: > > 050d2b8b2fe717b7415c13afbc2300e662a3c0dc5d37b9068c062109614760ca0e48631a8c013628f357e8bd3644f97c9c7238e64485e54b4ec840f95cdb1221 > > Staging site: > https://maven.apache.org/plugins-archives/maven-pmd-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 > > > Regards, > Andreas > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- Sławomir Jaranowski
Improvement in a maven-reporting-api design
Hi,
Currently Maven report plugin implements MavenReport by
extending AbstractMavenReport
Interface MavenReport is in maven-reporting-api
Class AbstractMavenReport is in maven-reporting-impl
maven-reporting-impl - has many transitive dependencies.
We have also AbstractMavenReportRenderer which hide some of method from
Doxia Sink,
Proposition:
Move AbstractMavenReport to maven-reporting-api
Add similar method from AbstractMavenReportRenderer to AbstractMavenReport
We can have something like:
class AbstractMavenReport ...
{
@Component
private DoxiaSupport doxiaSupport;
public void paragraph( String paragraph )
{
doxiaSupport.paragraph( paragraph );
}
}
Interface DoxiaSupport will be also in maven-reporting-api.
m-site-p by m-exec will add needed implementation of DoxiaSupport on plugin
classpath.
Advantage:
- plugin report will only need maven-reporting-api without any
transitive dependencies.
Disadvantage:
- plugin report can be only executed by m-site-p
WDYT?
--
Sławomir Jaranowski
Re: [VOTE] Release Maven Help Plugin version 3.3.0
+1 niedz., 14 sie 2022 o 14:35 Michael Osipov napisał(a): > Hi, > > We solved 11 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317522=12345417 > > There are still a couple of issues left in JIRA: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MPH%20AND%20resolution%20%3D%20Unresolved > > Staging repo: > https://repository.apache.org/content/repositories/maven-1797/ > > https://repository.apache.org/content/repositories/maven-1797/org/apache/maven/plugins/maven-help-plugin/3.3.0/maven-help-plugin-3.3.0-source-release.zip > > Source release checksum(s): > maven-help-plugin-3.3.0-source-release.zip > sha512: > > a33f460119cc11324a7e706199e323fbd5bd06835b448f5d2839fc8632cc71a64c454a7e1c56146f31a9e06e4fe4f895481c1271fbcc74454df14f7ba5109774 > > Staging site: > https://maven.apache.org/plugins-archives/maven-help-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 JXR version 3.3.0
+1 wt., 16 sie 2022 o 12:36 Michael Osipov napisał(a): > Hi, > > We solved 6 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317527=12351480 > > There are still a couple of issues left in JIRA: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20JXR%20AND%20resolution%20%3D%20Unresolved > > Staging repo: > https://repository.apache.org/content/repositories/maven-1798/ > > https://repository.apache.org/content/repositories/maven-1798/org/apache/maven/jxr/jxr/3.3.0/jxr-3.3.0-source-release.zip > > Source release checksum(s): > jxr-3.3.0-source-release.zip > sha512: > > 3455fcd6dec1a56d20737f7aa0253ff6c18a0b0e6ccdd7da05c70e46211c980224875108d8460ca6d75f46ccae6431559f03e481eb044a82d0b457c8eab16df7 > > Staging site: > https://maven.apache.org/jxr-archives/jxr-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 PDF Plugin version 1.6.1
+1 wt., 16 sie 2022 o 22:25 Michael Osipov napisał(a): > Hi, > > We solved 1 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317620=12352204 > > There are still a couple of issues left in JIRA: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MPDF%20AND%20resolution%20%3D%20Unresolved > > Staging repo: > https://repository.apache.org/content/repositories/maven-1799/ > > https://repository.apache.org/content/repositories/maven-1799/org/apache/maven/plugins/maven-pdf-plugin/1.6.1/maven-pdf-plugin-1.6.1-source-release.zip > > Source release checksum(s): > maven-pdf-plugin-1.6.1-source-release.zip > sha512: > > 1c4b431812201cd6057de0a1807bb0d8d24b92a564bcd3d79c5f494581c6a922382ea89c189581cbdf6d300d7b595f96a09217cb67d9e68422d320a7789e6759 > > Staging site: > https://maven.apache.org/plugins-archives/maven-pdf-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 PDF Plugin version 1.6.1
Please update site staging. wt., 16 sie 2022 o 22:25 Michael Osipov napisał(a): > Hi, > > We solved 1 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317620=12352204 > > There are still a couple of issues left in JIRA: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MPDF%20AND%20resolution%20%3D%20Unresolved > > Staging repo: > https://repository.apache.org/content/repositories/maven-1799/ > > https://repository.apache.org/content/repositories/maven-1799/org/apache/maven/plugins/maven-pdf-plugin/1.6.1/maven-pdf-plugin-1.6.1-source-release.zip > > Source release checksum(s): > maven-pdf-plugin-1.6.1-source-release.zip > sha512: > > 1c4b431812201cd6057de0a1807bb0d8d24b92a564bcd3d79c5f494581c6a922382ea89c189581cbdf6d300d7b595f96a09217cb67d9e68422d320a7789e6759 > > Staging site: > https://maven.apache.org/plugins-archives/maven-pdf-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 Release version 3.0.0-M7
+1 sob., 29 paź 2022 o 19:37 Michael Osipov napisał(a): > Hi, > > We solved 7 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824=12351828 > > There are still a couple of issues left in JIRA: > https://issues.apache.org/jira/projects/MRELEASE/issues > > Staging repo: > https://repository.apache.org/content/repositories/maven-1818/ > > https://repository.apache.org/content/repositories/maven-1818/org/apache/maven/release/maven-release/3.0.0-M7/maven-release-3.0.0-M7-source-release.zip > > Source release checksum(s): > maven-release-3.0.0-M7-source-release.zip > > e0b1ede39605ea0f5c4d2b05be1fd189e4875b49d285edb1e3f52a0fcce57e46c2b04619a8817275f12d8cf20009e91f349f2c29ff9a4da2aa839813c929acc5 > > Staging site: > https://maven.apache.org/maven-release-archives/maven-release-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: Clarify procedure for restarting releases
Thanks for feedback. Reading all of them, I must agree with Michael's proposition - yes it has been used for many years. Some of ideas from discussion: - create tag manually after voting ... not acceptable for me, hope also for others - we need it only for failed voting ... but we will add more manual works for all releases - dropping / moving tag in repository can have impact on fetched local repositories - and can generate more questions Users in most cases don't look at repository level. Versions aren't incremental numbers so it is not important that some of them will be missing - burned. I will prepare PR with a proposition for procedure update. wt., 1 lis 2022 o 18:25 Romain Manni-Bucau napisał(a): > Leads to the question: what is the most common source for end users. > Without debate it is not git so burning versions should be on central only > IMHO. For git we have clean solutions to not burn anything so it sounds > worth using them IMHO. > > Le mar. 1 nov. 2022 à 13:56, Heiko Studt a écrit : > > > Hello, > > > > Am 31.10.22 um 08:45 schrieb Slawomir Jaranowski: > > > > > We are talking about a situation which happens very rarely - canceling > a > > > vote. > > > > > In such a case simply delete tag and create next with next release run > > with > > > the same label is easy and possible. > > > > If your GIT repository has fetched some tag from the remote, it will NOT > > update this tag later on automatically nowadays. Some clients fetch the > > tags every 15 minutes, so you will probably have got the wrong tag > already. > > After that you will have the wrong version tags in some local repository > > after the tag was modified on remote. > > > > From the "git help fetch" > > | Since Git version 2.20, fetching to update refs/tags/* works the same > > | way as when pushing. I.e. any updates will be rejected without + in > > | the refspec (or --force). > > (2.20 was released on 2018-12-09) > > > > What is the workflow, if one tries to reproduce some issue on a special > > version? Do you really download the ZIP afresh for each such occasions > > or do you create a branch in your local repository from that specific > > version tag and start from there? > > > > I understand the reason *against* burning is the question: > >"why there is a GIT tag but not a release". > > The reason *for* burning is the question: > >"why the GIT tag is different to the release." > > > > For me, the former is way easier to spot and explain, the latter is > > error-prone on the user's side if the user is not aware that the tags > > are to be ignored or explicitely fetched before switching versions. > > > > Additionally, the latter may happen for other version artifact as well. > > > > > > MFG > > -- > > Heiko Studt > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > -- Sławomir Jaranowski
Re: [VOTE] Maven Build Cache Extension 1.0.0
Build locally from source-releases.zip - tests failed ... the same situation on Jenkins Is it acceptable? czw., 27 paź 2022 o 13:11 Guillaume Nodet napisał(a): > Hi, > > I've staged a release of Maven Build Cache Extension 1.0.0. > This is the first release of this component. > > Solved issues: > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12324820=12351243 > > JIRA issues left: > > > https://issues.apache.org/jira/browse/MBUILDCACHE?jql=project%20%3D%20MBUILDCACHE%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC > > Staging repo: > https://repository.apache.org/content/repositories/maven-1817 > > > https://repository.apache.org/content/repositories/maven-1817/org/apache/maven/extensions/maven-build-cache-extension/1.0.0/maven-build-cache-extension-1.0.0-source-release.zip > > Source release checksum: > maven-build-cache-extension-1.0.0-source-release.zip - SHA-512: > > 2379d68b15a47d47bcb836e2f0e543adce49c430b8bfe63de98c603e9a75c48450e56e9aab439a7437bf22b83e79bbf51d3ab7da97b53257f8e86cdc887105c7 > > Staging site: > > > https://maven.apache.org/extensions-archives/maven-build-cache-extension-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 > -- > > Guillaume Nodet > -- Sławomir Jaranowski
Re: [VOTE] Release Maven Fluido Skin version 2.0.0-M1
Something is not ok ... please look at generated report - look strange ... missing tables https://maven.apache.org/components/skins-archives/maven-fluido-skin-LATEST/dependency-convergence.html https://maven.apache.org/components/skins-archives/maven-fluido-skin-LATEST/surefire-report.html https://maven.apache.org/components/skins-archives/maven-fluido-skin-LATEST/checkstyle.html https://maven.apache.org/components/skins-archives/maven-fluido-skin-LATEST/invoker-report.html śr., 4 sty 2023 o 20:10 Michael Osipov napisał(a): > Hi, > > We solved 6 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317926=12331576 > > 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-1840/ > > https://repository.apache.org/content/repositories/maven-1840/org/apache/maven/skins/maven-fluido-skin/2.0.0-M1/maven-fluido-skin-2.0.0-M1-source-release.zip > > Source release checksum(s): > maven-fluido-skin-2.0.0-M1-source-release.zip > sha512: > > f956cd4ff0497cfd39c7d65dd3b91c1cc479291da867f8830d7754960809c2ff2265ad152effefe56216089344da1ad692b390c9a9254cf7c24678e96c3d6979 > > 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: [VOTE] Release Maven Dependency Plugin version 3.5.0
+1 - parent 39 should be used - master branch failed after release - fixed - not sure if we need the next minor version - there are no new features - but it is only a label :-) sob., 7 sty 2023 o 00:17 Michael Osipov napisał(a): > Hi, > > We solved 3 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317227=12352602 > > There are still a couple of issues left in JIRA: > https://issues.apache.org/jira/projects/MDEP/issues > > Staging repo: > https://repository.apache.org/content/repositories/maven-1845/ > > https://repository.apache.org/content/repositories/maven-1845/org/apache/maven/plugins/maven-dependency-plugin/3.5.0/maven-dependency-plugin-3.5.0-source-release.zip > > Source release checksum(s): > maven-dependency-plugin-3.5.0-source-release.zip > sha512: > > 1375b1d93318a05530bc3d0817776c3b6da78ed84177622ac39bb9bb4372ce3a46538bfb1121e708c4fd6196e741c977a7a7ca9be8bae6bfe3ee63df0787a4bd > > Staging site: > https://maven.apache.org/plugins-archives/maven-dependency-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 Project Info Reports Plugin version 3.4.2
+1 pt., 6 sty 2023 o 22:25 Michael Osipov napisał(a): > Hi, > > we solved 3 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317821=12352728 > > There are still a couple of issues left in JIRA: > https://issues.apache.org/jira/projects/MPIR/issues > > Staging repo: > https://repository.apache.org/content/repositories/maven-1842/ > > https://repository.apache.org/content/repositories/maven-1842/org/apache/maven/plugins/maven-project-info-reports-plugin/3.4.2/maven-project-info-reports-plugin-3.4.2-source-release.zip > > Source release checksum(s): > maven-project-info-reports-plugin-3.4.2-source-release.zip > sha512: > > f49363822ed543fb6ba873502cd8d1cfbda96e38216c57c6d39ec32748802f08349eca38a19080db3a34873c38bca9f5a56c8457f5c2952071a5dac1521aa161 > > Staging site: > > https://maven.apache.org/plugins-archives/maven-project-info-reports-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 Dependency Plugin version 3.5.0
niedz., 8 sty 2023 o 23:32 Michael Osipov napisał(a): > Am 2023-01-08 um 23:28 schrieb Slawomir Jaranowski: > > +1 > > > > - parent 39 should be used > > - master branch failed after release - fixed > > - not sure if we need the next minor version - there are no new features > - > > but it is only a label :-) > > I did the minor on purpose because the parent upgrade touched every > single source file. > > make sense > > - > 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-M1
+1 śr., 4 sty 2023 o 20:10 Michael Osipov napisał(a): > Hi, > > We solved 6 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317926=12331576 > > 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-1840/ > > https://repository.apache.org/content/repositories/maven-1840/org/apache/maven/skins/maven-fluido-skin/2.0.0-M1/maven-fluido-skin-2.0.0-M1-source-release.zip > > Source release checksum(s): > maven-fluido-skin-2.0.0-M1-source-release.zip > sha512: > > f956cd4ff0497cfd39c7d65dd3b91c1cc479291da867f8830d7754960809c2ff2265ad152effefe56216089344da1ad692b390c9a9254cf7c24678e96c3d6979 > > 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: [VOTE] Release Maven Surefire version 3.0.0-M8
+1 sob., 7 sty 2023 o 14:08 Michael Osipov napisał(a): > Hi, > > We solved 18 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927=12351809 > > There are still a couple of issues left in JIRA: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20SUREFIRE%20AND%20resolution%20%3D%20Unresolved > > Staging repo: > https://repository.apache.org/content/repositories/maven-1846/ > > https://repository.apache.org/content/repositories/maven-1846/org/apache/maven/surefire/surefire/3.0.0-M8/surefire-3.0.0-M8-source-release.zip > > Source release checksum(s): > surefire-3.0.0-M8-source-release.zip > sha512: > > d2a533fc8c89f92c40b20c104beb8da69a45683821cb5432e99e2d12b469067659b117e140ddf66e8ba71f12b1af7aa07207d279289957a52940162ce27599ba > > Staging site: > https://maven.apache.org/surefire-archives/surefire-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 Apache Maven version 3.8.7
+1 I use from yesterday - I don't discovered any issues pon., 26 gru 2022 o 17:36 Michael Osipov napisał(a): > Am 2022-12-24 um 21:20 schrieb Michael Osipov: > > Hi, > > > > We solved 19 issues: > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12352690 > > > > There are still hundreds of issues left in JIRA: > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20resolution%20%3D%20Unresolved > > > > Staging repo: > > https://repository.apache.org/content/repositories/maven-1839/ > > > > Dev dist directory: > > https://dist.apache.org/repos/dist/dev/maven/maven-3/3.8.7/ > > > > Source release checksums: > > apache-maven-3.8.7-src.zip sha512: > > > 7c5bbdfbd85711d11f93254208978b47e4dcf010f94a1b9f549c3040507d751dff10d99c5f3af5fa92fd44b4261fc950d69eac345736f62007416e1350319891 > > apache-maven-3.8.7-src.tar.gz sha512: > > > 99dc6a44811d945d2d9a9e88b32abde5a82e4a8fa202ff217a5e3106d7fc532f347cff01331f6c2c0d86b2cf67fc0d0ee609d0c7d39b352a9422b990e49a81eb > > > > Binary release checksums: > > apache-maven-3.8.7-bin.zip sha512: > > > c687fcdc3890bcf0f9f9dbc42ceded21dc80f0dcc5541c28912a99224694793f6e437998e46b5939bd314178865263c62a069c6c6f15d1d0541eea75748c46fd > > apache-maven-3.8.7-bin.tar.gz sha512: > > > 21c2be0a180a326353e8f6d12289f74bc7cd53080305f05358936f3a1b6dd4d91203f4cc799e81761cf5c53c5bbe9dcc13bdb27ec8f57ecf21b2f9ceec3c8d27 > > > > Draft for release notes: > > https://github.com/apache/maven-site/pull/356 > > > > Guide to testing staged releases: > > http://maven.apache.org/guides/development/guide-testing-releases.html > > > > Vote open until 2022-12-30T20:00Z > > +1 > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- Sławomir Jaranowski
[VOTE] Release Apache ASF parent 29, Maven parent 39
Hi, We solved 5 issues in ASF parent: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250=12352620 We solved 7 issues in Maven parent: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250=12352619 Commits: https://github.com/apache/maven-apache-parent/compare/apache-28...apache-29 https://github.com/apache/maven-parent/compare/maven-parent-38...maven-parent-39 Staging repos: https://repository.apache.org/content/repositories/orgapacheapache-1030/ https://repository.apache.org/content/repositories/orgapacheapache-1030/org/apache/apache/29/apache-29-source-release.zip https://repository.apache.org/content/repositories/maven-1834/ https://repository.apache.org/content/repositories/orgapacheapache-1031/ https://repository.apache.org/content/repositories/maven-1834/org/apache/maven/maven-parent/39/maven-parent-39-source-release.zip Source release checksum(s): apache-29-source-release.zip - SHA-512 : c1abe5433052918e5a7dde8e0338f809e0fb7a82fbb7db4d0509e2ceae7cb7e1acf88957c2a6447bc8064952df441d9235030b97764ec384b8508d1a2489 maven-parent-39-source-release.zip - SHA-512 : 1d3f23829a0733fedc29a10f014562f11fd0bdac54d29602da434fc0f012f9d3998e70c14cb5cbc54351b64349492a7e0405c02afb740111804d9dd18a629582 Staging sites: https://maven.apache.org/pom-archives/asf-LATEST/ https://maven.apache.org/pom-archives/maven-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 -- Sławomir Jaranowski
Re: New contributor alert
wt., 6 gru 2022 o 10:46 Jagruti Tiwari napisał(a): > Hi everyone, > > I have contributed to open source regularly since Feb 2022. I contributed > to Jenkins this Hacktoberfest. Right now, I am interested > in documentation and contributing to projects in Java. > > I was looking for GitHub repositories to contribute to and came across > Maven on up-for-grabs. > > I find this issue interesting: > https://issues.apache.org/jira/browse/MSHARED-1041| > > But I cannot comment because I cannot create a JIRA account by myself. > > Hi, For request new jira account please sent to priv...@maven.apache.org - prefered login name - display name - email address > Could someone help me here? > > Thanks, > Jagruti > -- Sławomir Jaranowski
Re: [VOTE] Maven Script Interpreter 1.4 and Maven Invoker Plugin 3.4.0
+ 1 Plugin stage page: https://maven.apache.org/plugins-archives/maven-invoker-plugin-LATEST/ czw., 15 gru 2022 o 04:30 Olivier Lamy napisał(a): > Hi, > I'd like to release Maven Script Interpreter 1.4 and Maven Invoker Plugin > 3.4.0 > The main goal is to support jdk19. > > Maven Script Interpreter 1.4 release notes > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12352358=Text=12317922=Create > > Staged repo: > https://repository.apache.org/content/repositories/maven-1836/ > sources: > https://repository.apache.org/content/repositories/maven-1836/org/apache/maven/shared/maven-script-interpreter/1.4/maven-script-interpreter-1.4-source-release.zip > > sources sha512 > https://repository.apache.org/content/repositories/maven-1836/org/apache/maven/shared/maven-script-interpreter/1.4/maven-script-interpreter-1.4-source-release.zip.sha512 > > staged site: > https://maven.apache.org/shared-archives/maven-script-interpreter-LATEST/ > > Maven Invoker Plugin 3.4.0 Release notes > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317525=12330828 > > staged repo: > https://repository.apache.org/content/repositories/maven-1837/ > sources > https://repository.apache.org/content/repositories/maven-1837/org/apache/maven/plugins/maven-invoker-plugin/3.4.0/maven-invoker-plugin-3.4.0-source-release.zip > sources sha512 > https://repository.apache.org/content/repositories/maven-1837/org/apache/maven/plugins/maven-invoker-plugin/3.4.0/maven-invoker-plugin-3.4.0-source-release.zip.sha512 > > vote open for 72H (countdown https://s.apache.org/m64qv ) > +1 > 0 > -1 > > cheers > Olivier > > - > 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 Wagon version 3.5.3
+1 - old parent - the most of mailing lists addresses was not working niedz., 18 gru 2022 o 22:57 Michael Osipov napisał(a): > Hi, > > We solved 1 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318122=12352696 > > There are still a couple of issues left in JIRA: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20WAGON%20AND%20resolution%20%3D%20Unresolved > > Staging repo: > https://repository.apache.org/content/repositories/maven-1838/ > > https://repository.apache.org/content/repositories/maven-1838/org/apache/maven/wagon/wagon/3.5.3/wagon-3.5.3-source-release.zip > > Source release checksum(s): > wagon-3.5.3-source-release.zip > sha512: > > 8db385a4676af25e78a35d9bea3c1c0892de29336206b02fcf5130e85736c01c2445b39276eb01c2b99ddce384b3649515c63a5f363ed168424b8c6d089f6170 > > Staging site: > https://maven.apache.org/wagon-archives/wagon-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 Apache Maven 4.0.0-alpha-3
Delany Is your issue the same, as: https://github.com/mojohaus/flatten-maven-plugin/issues/330 By the way, the issue should be reported on Maven jira. wt., 13 gru 2022 o 12:07 Guillaume Nodet napisał(a): > Could you raise a JIRA issue and attach the full stack trace please ? > > Le mar. 13 déc. 2022 à 11:12, Delany a écrit > : > > > Im still getting > > Execution flatten of goal > > org.codehaus.mojo:flatten-maven-plugin:1.3.0:flatten failed: Unable to > load > > the mojo 'flatten' (or one of its required components) from the plugin > > 'org.codehaus.mojo:flatten-maven-plugin:1.3.0': > > java.util.NoSuchElementException > > > > Do I still need the plugin though? > > > > Delany > > > > On Mon, 12 Dec 2022 at 15:19, Guillaume Nodet wrote: > > > > > I've staged a release candidate at: > > > https://repository.apache.org/content/repositories/maven-1835 > > > > > > Source distributions: > > > > > > > > > https://dist.apache.org/repos/dist/dev/maven/maven-4/4.0.0-alpha-3/source/ > > > > > > Binaries are available at: > > > > > > > > > > > > https://dist.apache.org/repos/dist/dev/maven/maven-4/4.0.0-alpha-3/binaries/ > > > > > > > > > > > > https://repository.apache.org/content/repositories/maven-1835/org/apache/maven/apache-maven/4.0.0-alpha-3/ > > > > > > Release notes: > > > > > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12352443 > > > https://github.com/apache/maven/milestone/1?closed=1 > > > > > > Github release: > > > https://github.com/apache/maven/releases/tag/maven-4.0.0-alpha-3 > > > > > > Please review and vote ! > > > > > > -- > > > > > > Guillaume Nodet > > > > > > > > -- > > Guillaume Nodet > -- Sławomir Jaranowski
[RESULT] [VOTE] Release Apache ASF parent 29, Maven parent 39
Hi, The vote has passed with the following result: +1: Olivier Lamy, Hervé Boutemy, Sylwester Lachiewicz, Guillaume Nodet, Romain Manni-Bucau PMC quorum: reached I will promote the source release zip file to Apache distribution area and the artifacts to the central repo. -- Sławomir Jaranowski
[ANN] Apache Software Foundation Parent POM Version 29 Released
The Apache Maven team is pleased to announce the release of the Apache Software Foundation Parent POM Version, version 29 https://maven.apache.org/pom/asf/ You should specify the version in your project as parent like the following: org.apache apache 29 You can download the appropriate sources etc. from the download page: http://maven.apache.org/pom/asf/download.html Release Notes - Maven POMs - Version ASF-29 ** Improvement * [MPOM-378] - Using an SPDX identifier as the license name is recommended by Maven ** Dependency upgrade * [MPOM-380] - Bump maven-ear-plugin from 3.2.0 to 3.3.0 * [MPOM-381] - Bump maven-release-plugin from 3.0.0-M6 to 3.0.0-M7 * [MPOM-382] - Bump maven-install-plugin from 3.0.1 to 3.1.0 * [MPOM-383] - Bump maven-dependency-plugin from 3.3.0 to 3.4.0 Enjoy, -The Apache Maven team
[ANN] Apache Maven Parent POMs 39 Released
The Apache Maven team is pleased to announce the release of the Maven Parent POMs Version 39. Maven Parent POMs include Maven Parent POM itself, but also Maven Plugins Parent POM, Maven Shared Components Parent POM, Maven Skins Parent POM and Maven Doxia Tools Parent POM. https://maven.apache.org/pom/maven/ You should specify the version in your project as parent like the following: org.apache.maven maven-parent 39 You can download the appropriate sources etc. from the download page: https://maven.apache.org/pom/maven/download.html Release Notes - Maven POMs - Version MAVEN-39 ** Bug * [MPOM-371] - Fix checkstyle configuration * [MPOM-376] - Spotless importOrder should be taken into consideration ** Improvement * [MPOM-370] - Document "format" profile * [MPOM-373] - Execute spotless before rat * [MPOM-377] - Add space before close empty elements in poms * [MPOM-384] - Allow to override streamLogsOnFailures parameter for m-invoker-p Enjoy, -The Apache Maven team
Re: [VOTE] Release Apache Maven 4.0.0-alpha-3
+1 To do: - release notes - new reference documentation https://maven.apache.org/docs/history.html pon., 12 gru 2022 o 14:20 Guillaume Nodet napisał(a): > I've staged a release candidate at: > https://repository.apache.org/content/repositories/maven-1835 > > Source distributions: > > https://dist.apache.org/repos/dist/dev/maven/maven-4/4.0.0-alpha-3/source/ > > Binaries are available at: > > > https://dist.apache.org/repos/dist/dev/maven/maven-4/4.0.0-alpha-3/binaries/ > > > https://repository.apache.org/content/repositories/maven-1835/org/apache/maven/apache-maven/4.0.0-alpha-3/ > > Release notes: > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12352443 > https://github.com/apache/maven/milestone/1?closed=1 > > Github release: > https://github.com/apache/maven/releases/tag/maven-4.0.0-alpha-3 > > Please review and vote ! > > -- > > Guillaume Nodet > -- Sławomir Jaranowski
Re: [VOTE] Release Apache Maven 4.0.0-alpha-3
Even more, I'm for adding 4.x to the download site together with mvnd ;-) śr., 14 gru 2022 o 01:08 Slawomir Jaranowski napisał(a): > +1 > > To do: > - release notes > - new reference documentation > > https://maven.apache.org/docs/history.html > > > pon., 12 gru 2022 o 14:20 Guillaume Nodet napisał(a): > >> I've staged a release candidate at: >> https://repository.apache.org/content/repositories/maven-1835 >> >> Source distributions: >> >> https://dist.apache.org/repos/dist/dev/maven/maven-4/4.0.0-alpha-3/source/ >> >> Binaries are available at: >> >> >> https://dist.apache.org/repos/dist/dev/maven/maven-4/4.0.0-alpha-3/binaries/ >> >> >> https://repository.apache.org/content/repositories/maven-1835/org/apache/maven/apache-maven/4.0.0-alpha-3/ >> >> Release notes: >> >> >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12352443 >> https://github.com/apache/maven/milestone/1?closed=1 >> >> Github release: >> https://github.com/apache/maven/releases/tag/maven-4.0.0-alpha-3 >> >> Please review and vote ! >> >> -- >> >> Guillaume Nodet >> > > > -- > Sławomir Jaranowski > -- Sławomir Jaranowski
Re: Surefire Plugin Pull Requests
Hi, Root cause for it is failing test: org.apache.maven.surefire.its.ConsoleOutputIT.properNewlinesAndEncodingWithDifferentEncoding Error which you see is from the GH job which tries to attach logs in case of failed build but on linux os is executed a test which checks a special path and such path is left in workspace after executing but is not valid for GH ... We should try to restore the original path after test_surefire-1617 to make the GH job work. czw., 15 gru 2022 o 14:15 Elliotte Rusty Harold napisał(a): > I looked at some of those recently but the Github CI seems borked, > possibly at head. Someone with repo privileges may have to look into > that before anything can be merged. E.g. > > Run actions/upload-artifact@v3 > With the provided path, there will be 8281 files uploaded > Starting artifact upload > For more detailed logs during the artifact upload process, enable > step-debugging: > > https://docs.github.com/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging#enabling-step-debug-logging > Artifact name is valid! > Error: Artifact path is not valid: /this is: a > test_surefire-1617/log.txt. Contains the following character: Colon : > Invalid characters include: Double quote ", Colon :, Less than <, > Greater than >, Vertical bar |, Asterisk *, Question mark ?, Carriage > return \r, Line feed \n > > On Thu, Dec 15, 2022 at 2:54 AM Pabst, Andreas > wrote: > > > > Hi all, > > > > there are quite a few pull requests in the Surefire project that are > worth for a committer to have a look at and possibly merge. > > > > https://github.com/apache/maven-surefire/pull/545 > > https://github.com/apache/maven-surefire/pull/549 > > https://github.com/apache/maven-surefire/pull/564 > > https://github.com/apache/maven-surefire/pull/568 > > > > I'd like to specifically request a review for the last one ( > https://github.com/apache/maven-surefire/pull/568) because it's my work, > but the others seem equally or even more important. > > > > If this is not the right channel to ask for a pull request review I > apologize. Please let me know what the right venue is in that case. > > > > Best Regards, > > Andreas > > > > -- > Elliotte Rusty Harold > elh...@ibiblio.org > > - > 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 Site Plugin version 4.0.0-M4
+1 pt., 2 gru 2022 o 21:38 Michael Osipov napisał(a): > Hi, > > We solved 12 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317923=12352544 > > There are still a couple of issues left in JIRA: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSITE%20AND%20resolution%20%3D%20Unresolved > > Staging repo: > https://repository.apache.org/content/repositories/maven-1833/ > > https://repository.apache.org/content/repositories/maven-1833/org/apache/maven/plugins/maven-site-plugin/4.0.0-M4/maven-site-plugin-4.0.0-M4-source-release.zip > > Source release checksum(s): > maven-site-plugin-4.0.0-M4-source-release.zip > sha512: > > cc1cb2eeb030b7961cdad7a60b037444979ea37b93c1d427a5876367ffdb64576d3456a5c421b0c79711e4907bcf1b2feccc53cff38e955e5abcef70c69226be > > Staging site: > https://maven.apache.org/plugins-archives/maven-site-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
Mock Repository Manager - improvements
Hi, Project Mock Repository Manager [1] still uses Maven 2.x Api for managing artifacts, meta-data and local repositories. I would like to switch to Api 3.x. There is also one more feature - browsing repositories by browser, you can start mrm by goal mrm:run and point your browser to provide address. In my opinion mrm in most cases is used during integration tests, and browsing managed repositories by browser is not used. For browsing are only available artifacts and path which was resolved early so not all available, These options need a lot of code to support it. I would like to remove such features and corresponding code, it will be easier for the next refactor and improvements. What do you think? [1] https://www.mojohaus.org/mrm/mrm-maven-plugin/index.html -- Sławomir Jaranowski
Re: [DISCUSS] Quo Vadis Maven Site
Hi, some my thoughts - site looks can be changed be skins - so can be more modern - long time on build site is caused by multiple executing the same Maven phase for many reports [1] - some reports, like tests result, static code analize is not usable for static documentation - such reports should be generated by CI nowadays [1] https://issues.apache.org/jira/browse/MSHARED-1044 śr., 16 lis 2022 o 11:19 Tamás Cservenák napisał(a): > Howdy, > > This is really just a brainstorming thread I'd like to spin, regarding > Maven Site stuff. > > Again, the message is in wiki > https://cwiki.apache.org/confluence/display/MAVEN/Quo+Vadis+Maven+Site > > But I would like to make discussion happen here on dev ML. > > Thanks > T > -- Sławomir Jaranowski
Re: Surefire plain text reports
pt., 18 lis 2022 o 09:24 Romain Manni-Bucau napisał(a): > +1 to switch it off by default (but keep the feature since it can help > investigations on CI) > Text reports contain exactly the same information that is displayed during build on console, so you should have it in logs from CI. Additionally xml reports also have it. Do you really use it on your CI? > > 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 ven. 18 nov. 2022 à 09:23, Slawomir Jaranowski > a écrit : > > > Hi, > > > > By default Surefire generate plain text reports which is stored in > > target/surefire-reports/yourTestName.txt > > > > It can be disabled by using the "useFile" parameter. > > > > Question - Does somebody use such reports? > > I'm thinking about removing those at all and saving some CO2 :-) > > > > What do you think? > > > > -- > > Sławomir Jaranowski > > > -- Sławomir Jaranowski
Surefire plain text reports
Hi, By default Surefire generate plain text reports which is stored in target/surefire-reports/yourTestName.txt It can be disabled by using the "useFile" parameter. Question - Does somebody use such reports? I'm thinking about removing those at all and saving some CO2 :-) What do you think? -- Sławomir Jaranowski
Re: [DISCUSS] Notes For Maven Plugin Developers
So org.apache.maven.repository.RepositorySystem - should be deprecated ... śr., 23 lis 2022 o 14:53 Tamás Cservenák napisał(a): > Howdy, > > Sorry for the late reply. > > Yes, original plan was to ditch maven-compat (for 4.0.0), but then it > turned out that in "maven 3 universe", to do some stuff you had two > options: > - either rely on something in maven-compat > - or reach directly for resolver (but it was not "popular" choice due > 3.0/3.1 package change for resolver, see maven-artifact-transport etc) > > Now, many plugins still use compat components, so forcing them to use > resolver "only" to later switch to API (forcing two changes in a short > timeframe) is not something we want to do. > Making it happen would be "very good", but still, there was some backlash. > Hence, we decided that in the "transitioning period" (when maven 4 will > still support maven 3 plugins) we should keep compat. > > One typical case of this "duality" is component > org.apache.maven.repository.RepositorySystem that has an interface in > maven-core (so is "like Maven3 stuff") but is implemented in maven-compat > only > > Given migration to M4 API will be a bigger effort (for plugin devs), we > decided to opt for this, to lessen breaking changes. > > T > > On Wed, Nov 16, 2022 at 9:51 AM Christoph Läubrich > wrote: > > > One note about: > > > > > Note: this dependency in test scope is "acceptable" and actually > > required by some testing frameworks (see below). > > > > I think it is actually *not* acceptable and will cause confusions and > > there are already some work going on not requiring it anymore, so > > probably this can be updated to: > > > > 1) not require maven-compat > > 2) support at laest JUnit 4 > > > > I see two ways for this > > 1) update plexustestcase for Junit 4 first > > 2) do not depend on PlexusTestcase but just copy the code into > > maven-plugin-testing > > > > I'm also confused about > > > > > his module is not removed in 3.9.0, nor in first releases of 4.0.x > > > > as I though this was the goal of 3.9.x to get away with the compat > > module to be prepared for 4.0 ... > > > > Am 16.11.22 um 09:43 schrieb Tamás Cservenák: > > > Howdy, > > > > > > Recently we had several queries about testing Maven Plugins, but in > > > general I think we should make plugin developers aware of incoming > > changes. > > > Hence, I assembled the following wiki page, that may become Maven Site > > page > > > as well, and (irrelevant is it becoming site page or not) probably > should > > > be sent out to users ML as well, to get a broader audience. > > > > > > > > > https://cwiki.apache.org/confluence/display/MAVEN/Notes+For+Maven+Plugin+Developers > > > > > > Consider the page as DRAFT, and let me know what you think and what you > > > think is missing from it. > > > > > > Recently I started locally using 3.9.0-SNAPSHOT and found several > plugins > > > we use affected, for example: > > > > > > https://github.com/gaul/modernizer-maven-plugin/issues/152 > > > https://github.com/revelc/impsort-maven-plugin/issues/64 > > > > > > Would be good if we ensure that our own builds will work with latest > > Maven, > > > but also to announce to plugin developers out there about upcoming > > changes. > > > > > > Comments are welcome. > > > > > > Goal is to make the content of that wiki page "complete" (that's what > we > > > need to agree about), and then send it out to user ML. > > > > > > T > > > > > > PS: please let's discuss here on ML first round, so we can edit the > wiki > > > page as discussed. > > > > > > > - > > 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 Resolver 1.9.2
+1 śr., 23 lis 2022 o 13:57 Tamás Cservenák napisał(a): > Howdy, > > We solved 2 issues: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20fixVersion%20%3D%201.9.2 > 20fixVersion%20%3D%201.9.1 > < > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20fixVersion%20%3D%201.9.1 > > > > There are still some issues in JIRA: > https://issues.apache.org/jira/projects/MRESOLVER/issues > > Staging repository: > https://repository.apache.org/content/repositories/maven-1827/ > > Source SHA512: > > 1285c0763f98b26707c14c19f8bb6f551431b5458fb081f944d4c1152f34ff2403d66060f8458a560a7325338b4b82afd6fc0443d3416a148824a6773e987e32 > > 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 > > Vote open for at least 72 hours. > > [ ] +1 > [ ] +0 > [ ] -1 > -- Sławomir Jaranowski
Re: [HEADS UP] Master update to parent pom 38 with JDK 1.8 and new code style
Hi, Great work. Please take care - that commit sha will be changed after rebase PR. Should be added at new PR or direct commit. wt., 22 lis 2022 o 14:43 Guillaume Nodet napisał(a): > As discussed in the last weeks, I've pushed an upgrade to maven parent 38 > which has the new code style enforced. The auto-formatting can be enabled > using the format profile. > > The parent POM raises the minimum JDK requirement to JDK 1.8. > > Note that any component upgrading to the maven parent pom 38 will have this > code style enforced. I would advise the following when upgrading: > * create a commit with just the parent pom change (and related needed > changes) > * run with the -Pformat option and commit the changes > * add a file named .git-blame-ignore-revs containing the sha1 of the > previous commit to make sure the git blame works well and ignore the > reformat code, see [1] > > [1] > > https://github.com/apache/maven/commit/001eef8452b38110a2557446aa81b8fb1ff35f92#diff-f247fbfbe928b907db42554d0b3006b28dd11c25a59be031abda73b11a2c934a > > Cheers, > Guillaume > -- Sławomir Jaranowski
Re: [VOTE] Release Maven Dependency Plugin version 3.4.0
+1 sob., 26 lis 2022 o 22:40 Michael Osipov napisał(a): > Hi, > > We solved 21 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317227=12351068 > > There are still a couple of issues left in JIRA: > https://issues.apache.org/jira/projects/MDEP/issues > > Staging repo: > https://repository.apache.org/content/repositories/maven-1830/ > > https://repository.apache.org/content/repositories/maven-1830/org/apache/maven/plugins/maven-dependency-plugin/3.4.0/maven-dependency-plugin-3.4.0-source-release.zip > > Source release checksum(s): > maven-dependency-plugin-3.4.0-source-release.zip > sha512: > > 27a6fc8e589e5922c2a87a685d52a1c38a30b062e803d42fb7c97a39613fbef525a0920daa40144584c7cc36bad03e6c7bc2fa59b095fde3f8ecc660b0daba21 > > Staging site: > https://maven.apache.org/plugins-archives/maven-dependency-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 Apache Maven Doxia Sitetools version 2.0.0-M4
+1 sob., 26 lis 2022 o 16:52 Michael Osipov napisał(a): > Hi, > > we solved 10 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317320=12352134 > > There are still a couple of issues left in JIRA: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317320%20AND%20status%20%3D%20Open > > Staging repo: > https://repository.apache.org/content/repositories/maven-1829 > > https://repository.apache.org/content/repositories/maven-1829/org/apache/maven/doxia/doxia-sitetools/2.0.0-M4/doxia-sitetools-2.0.0-M4-source-release.zip > > Source release checksum(s): > doxia-sitetools-2.0.0-M4-source-release.zip > sha512: > > 30e02b133f2edc1181cdcd134fd15a14f4d0e705141cfccb7c24c971c00e76d8917b440697f603e2c32ce20cd532876fd93e3ab5f08633f4d0e9ca9d7f496923 > > Staging site: > > https://maven.apache.org/doxia/doxia-sitetools-archives/doxia-sitetools-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] Maven Dependency Tree 3.2.1
+1 śr., 16 lis 2022 o 03:05 Olivier Lamy napisał(a): > Hi, > I'd like to release Maven Dependency Tree 3.2.1 > We made one enhancement > https://issues.apache.org/jira/projects/MSHARED/versions/12352234 > > Staging repository > https://repository.apache.org/content/repositories/maven-1826/ > > source release > https://repository.apache.org/content/repositories/maven-1826/org/apache/maven/shared/maven-dependency-tree/3.2.1/maven-dependency-tree-3.2.1-source-release.zip > > > Staging site > https://maven.apache.org/shared-archives/maven-dependency-tree-LATEST/ > > Vote open for 71h48m [1] > > +1 > 0 > -1 > > > cheers > > [1] > https://www.timeanddate.com/countdown/generic?iso=20221119T1153=1490=cursive=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] Maven Apache Parent 28 - Maven Shared Resources 5 - Maven Parent 38
Please also update documentation sites: https://maven.apache.org/pom-archives/asf-LATEST/ https://maven.apache.org/pom-archives/maven-LATEST/ https://maven.apache.org/shared-archives/maven-shared-resources-LATEST/ wt., 15 lis 2022 o 10:18 Guillaume Nodet napisał(a): > I've staged a few releases: > * Maven Apache Parent Pom 28 > * Maven Shared Resources 5 > * Maven Parent Pom 38 > > Release notes for ASF-28 > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250=12352090 > https://github.com/apache/maven-apache-parent/milestone/1?closed=1 > > Release notes for Maven Shared Resources 5: > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12350687 > https://github.com/apache/maven-shared-resources/milestone/1?closed=1 > > Release notes for MAVEN-38 > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250=12352136 > https://github.com/apache/maven-parent/milestone/1?closed=1 > > Staging repositories: > https://repository.apache.org/content/repositories/maven-1824 > https://repository.apache.org/content/repositories/maven-1825 > https://repository.apache.org/content/repositories/orgapacheapache-1028 > https://repository.apache.org/content/repositories/orgapacheapache-1029 > > Please review and vote ! > > -- > > Guillaume Nodet > -- Sławomir Jaranowski
Re: [VOTE] Release Apache Maven Reporting API version 4.0.0-M3
+1 śr., 23 lis 2022 o 20:40 Michael Osipov napisał(a): > Hi, > > We solved 2 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12352562 > > 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-api > > Staging repo: > https://repository.apache.org/content/repositories/maven-1828/ > > https://repository.apache.org/content/repositories/maven-1828/org/apache/maven/reporting/maven-reporting-api/4.0.0-M3/maven-reporting-api-4.0.0-M3-source-release.zip > > Source release checksum(s): > maven-reporting-api-4.0.0-M3-source-release.zip > sha512: > > a91c3dc94cd7cca86bb1d3f3c6774c627715bc9de0c6821c86ceeb7a906ef8ddc0d944569ca90b6649700bee07df5df04369985e38ff9593d876d9b1431639f6 > > Staging site: > https://maven.apache.org/shared-archives/maven-reporting-api-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 Apache Maven Reporting Exec version 2.0.0-M3
+1 wt., 29 lis 2022 o 22:38 Michael Osipov napisał(a): > Hi, > > We solved 4 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12352600 > > 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-exec > > Staging repo: > https://repository.apache.org/content/repositories/maven-1831/ > > https://repository.apache.org/content/repositories/maven-1831/org/apache/maven/reporting/maven-reporting-exec/2.0.0-M3/maven-reporting-exec-2.0.0-M3-source-release.zip > > Source release checksum(s): > maven-reporting-exec-2.0.0-M3-source-release.zip > sha512: > > ab26e7e479ed35ab4c73fa8f89326e38a6f3c949297bb7215065ea2cf2b2b51ce841a4b02c1d27b92c34572a5936965acd0c8b3d865d8709a3bf38d6eb693aa0 > > Staging site: > https://maven.apache.org/shared-archives/maven-reporting-exec-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 Apache Maven Reporting Impl version 4.0.0-M3
+1 wt., 29 lis 2022 o 22:43 Michael Osipov napisał(a): > Hi, > > We solved 3 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12352179 > > There are no 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-1832/ > > https://repository.apache.org/content/repositories/maven-1832/org/apache/maven/reporting/maven-reporting-impl/4.0.0-M3/maven-reporting-impl-4.0.0-M3-source-release.zip > > Source release checksum(s): > maven-reporting-impl-4.0.0-M3-source-release.zip > sha512: > > 4e5e7c2639623ac7bf673b7e70a3d4620f6fbe7063891dee0e5a6ebc0ed61847dc6614b5979cd47b5a6a5e107afa10fadd90798d7810ce334155a2c168d9d8b3 > > 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 > > -- Sławomir Jaranowski
[RESULT] [VOTE] Release Apache Maven Install Plugin version 3.1.0
Hi, The vote has passed with the following result: +1: Tamás Cservenák, Michael Osipov, Olivier Lamy, Karl Heinz Marbaise PMC quorum: reached I will promote the source release zip file to Apache distribution area and the artifacts to the central repo. -- Sławomir Jaranowski
[ANN] Apache Maven Install Plugin 3.1.0 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Install Plugin, version 3.1.0 https://maven.apache.org/plugins/maven-instll-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-install-plugin 3.1.0 You can download the appropriate sources etc. from the download page: https://maven.apache.org/plugins/maven-install-plugin/download.html Release Notes - Maven Install Plugin - Version 3.1.0 ** Bug * [MINSTALL-179] - installAtEnd when module does not use m-install-p ** Improvement * [MINSTALL-183] - Don't use metadata from main artifact to fetch pom.xml * [MINSTALL-185] - Install all artifacts in one request ** Task * [MINSTALL-181] - Require Java 8 * [MINSTALL-184] - Cleanup IT tests ** Dependency upgrade * [MINSTALL-180] - Upgrade Parent to 37 * [MINSTALL-182] - Bump mockito-core from 2.28.2 to 4.8.1 Enjoy, -The Apache Maven team
Re: [VOTE] Release Maven Resolver 1.9.1
+1 pon., 14 lis 2022 o 15:25 Tamás Cservenák napisał(a): > Howdy, > > We solved 5 issues: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20fixVersion%20%3D%201.9.1 > > There are still some issues in JIRA: > https://issues.apache.org/jira/projects/MRESOLVER/issues > > Staging repository: > https://repository.apache.org/content/repositories/maven-1823/ > > Source SHA512: > > 6b160b2748763a21a59a5664a591135bae9b11e822a8dc065807056f85fa9ad6a6dc4810de5f58118153c486c108500628e19662a5eec1080a9bd92f09a56ea6 > > 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 > > Vote open for at least 72 hours. > > [ ] +1 > [ ] +0 > [ ] -1 > -- Sławomir Jaranowski
Re: [VOTE] Release Maven Resolver 1.9.4
+1 pt., 13 sty 2023 o 08:11 Tamás Cservenák napisał(a): > Howdy, > > We solved 5 issues: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20fixVersion%20%3D%201.9.4 > > There are still some issues in JIRA: > https://issues.apache.org/jira/projects/MRESOLVER/issues > > Staging repository: > https://repository.apache.org/content/repositories/maven-1851 > > Source release SHA512: > > e02988b875a55db1f1eb0976a06d7222cb1598228634735a9afdd27b827d48ae1c37629311613949f67b171bc9feb611f5cbdfe875003326144b20c1d2539ca3 > > 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 > > Vote open for at least 72 hours. > > [ ] +1 > [ ] +0 > [ ] -1 > -- Sławomir Jaranowski
Re: [VOTE] Release Maven Resolver 1.9.4
sob., 14 sty 2023 o 13:56 Elliotte Rusty Harold napisał(a): > -1 > > The version number's wrong. This should be 1.9.3. > - 1.9.4 is the correct version. - vote for 1.9.3 was canceled. - it is in line with the current procedure If you need more discussion please open a new one thread .. we had discussed it. > > On Fri, Jan 13, 2023 at 7:11 AM Tamás Cservenák > wrote: > > > > Howdy, > > > > We solved 5 issues: > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20fixVersion%20%3D%201.9.4 > > > > There are still some issues in JIRA: > > https://issues.apache.org/jira/projects/MRESOLVER/issues > > > > Staging repository: > > https://repository.apache.org/content/repositories/maven-1851 > > > > Source release SHA512: > > > e02988b875a55db1f1eb0976a06d7222cb1598228634735a9afdd27b827d48ae1c37629311613949f67b171bc9feb611f5cbdfe875003326144b20c1d2539ca3 > > > > 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 > > > > Vote open for at least 72 hours. > > > > [ ] +1 > > [ ] +0 > > [ ] -1 > > > > -- > Elliotte Rusty Harold > elh...@ibiblio.org > > - > 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 Plugin Tools 3.7.1
+1 pt., 13 sty 2023 o 08:36 Tamás Cservenák napisał(a): > Howdy, > > We solved 1 issue > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MPLUGIN%20AND%20fixVersion%20%3D%203.7.1 > > There are still a couple of issues left in JIRA: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MPLUGIN%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key > > Staging repo: > https://repository.apache.org/content/repositories/maven-1852/ > > Source release SHA512: > > a4d16ed3f9618990f5327eb8bb1a137c3effaa1f90651925c75ff6df1a16c7bb52de1facb5b90ce4a7ca5714f1b35a28da92de98e7678d55ad9e9ca3246e61bb > > Staging site: > https://maven.apache.org/plugin-tools-archives/plugin-tools-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 > -- Sławomir Jaranowski
Re: [VOTE] Release Maven Fluido Skin version 2.0.0-M2
+1 czw., 12 sty 2023 o 17:09 Michael Osipov napisał(a): > Hi, > > We solved 10 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317926=12352732 > > 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-1850/ > > https://repository.apache.org/content/repositories/maven-1850/org/apache/maven/skins/maven-fluido-skin/2.0.0-M2/maven-fluido-skin-2.0.0-M2-source-release.zip > > Source release checksum(s): > maven-fluido-skin-2.0.0-M2-source-release.zip > sha512: > > ad6bf1ee15c4b959518025090853a36d1294913529839bd7c84a798cb7278c245b70e186b6fd60e53a35710a034b492044d899e5c0290d4a12514dcc3e9ff049 > > 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: [VOTE] Release Maven Fluido Skin version 1.11.2
+1 wt., 17 sty 2023 o 10:30 Michael Osipov napisał(a): > Hi, > > We solved 6 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317926=12352758 > > 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-1853/ > > https://repository.apache.org/content/repositories/maven-1853/org/apache/maven/skins/maven-fluido-skin/1.11.2/maven-fluido-skin-1.11.2-source-release.zip > > Source release checksum(s): > maven-fluido-skin-1.11.2-source-release.zip > sha512: > > 988f647576c1cde614b700e7b136517c692660e7c7440d6ca42d9d6efaae424e68b963dae5599b22d6e63577ae8a3d58acaa23e69e8278d02b283bee15360c11 > > 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: Maven 3.9,0 plan
Build on Jenkins deploys snapshot artifacts to ASF repository, https://repository.apache.org/#nexus-search;gav~org.apache.maven~apache-maven~3.9.0-SNAPSHOT~~ czw., 19 sty 2023 o 22:49 Falko Modler napisał(a): > Hi there, > > So, please anyone able to, test 3.9.0-SNAPSHOT if you can. > > do I have to build it on my own? I've been looking in a few places > including Jenkins but I couldn't find a pre-built archive. > > Thanks! > > Cheers, > > Falko > > > - > 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 Doxia version 2.0.0-M5
+1 - source release contains files with CRLF line ending, so when I try to build code on MacOs I have errors from spotless, like [ERROR] Failed to execute goal com.diffplug.spotless:spotless-maven-plugin:2.28.0:check (default) on project doxia: The following files had format violations: [ERROR] pom.xml [ERROR] @@ -1,513 +1,513 @@ [ERROR] -\r\n [ERROR] - 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 Apache Maven Reporting API version 4.0.0-M4
+1 - spotless and line ending code ... from source-release - surefire, checkstyle, pmd raptors are empty niedz., 22 sty 2023 o 20:06 Michael Osipov napisał(a): > Hi, > > IMPORTANT: Requires Doxia 2.0.0-M5 vote/staging repo! > > We solved 2 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12352772 > > 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-api > > Staging repo: > https://repository.apache.org/content/repositories/maven-1857/ > > https://repository.apache.org/content/repositories/maven-1857/org/apache/maven/reporting/maven-reporting-api/4.0.0-M4/maven-reporting-api-4.0.0-M4-source-release.zip > > Source release checksum(s): > maven-reporting-api-4.0.0-M4-source-release.zip > sha512: > > 92d884e2e26616be65510b64e429efa489b59e593d288ad7877272c212a2926cb43416a992428ffd209bed4303c4955ba3cf056c4c69a801512421f6a77e293e > > Staging site: > https://maven.apache.org/shared-archives/maven-reporting-api-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
Upcoming Maven Enforcer 3.2.0 release
Hi, I'm going to release the next version of Maven Enforcer plugin and build in rules. Probably in next week - about 24-26 of January Prepared release note: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317520=12351838 The most important: - New Enforcer API - https://issues.apache.org/jira/browse/MENFORCER-455 - Get rid of maven-dependency-tree dependency - https://issues.apache.org/jira/browse/MENFORCER-435 - Verify working with Maven 4 - https://issues.apache.org/jira/browse/MENFORCER-447 I will appreciate any tests on your projects. If something else should be added please let me know. -- Sławomir Jaranowski
Re: Upcoming Maven Enforcer 3.2.0 release
Hi, Petr thanks for testing and pointing to Quarkus. It is a very good place to check. I also checked with Quarkus, tried to violate some of the rules and was reported as errors. Root cause for such improvement is that we replaced maven-dependency-tree with a direct resolver API. I expected some improvement but the test exceeded my expectations :-) in positive way pon., 23 sty 2023 o 14:32 Petr Široký napisał(a): > Hello, > > great stuff! Looking forward to that release. > > I gave the latest 3.2.0-SNAPSHOT (26697b16) a quick try with Quarkus repo ( > https://github.com/quarkusio/quarkus), since the project is pretty big > (more than 1k sub-modules) and it also uses enforcer quite extensively > (multiple executions). The current enforcer version is 3.0.0-M3, since > there were multiple bugs in 3.1.0 which I think prevented the upgrade. > > Here are my findings: > - 'mvn validate' still succeeds, there are no enforcer errors. This is I > think good. I obviously did not check if every rule of every module is > being executed, but I did a quick comparison in few modules and everything > _seems_ to be in order. > > - what seems to be very positive is the improvement in execution time. I > compared a sequential and parallel runs, and also mvnd run (using JDK 17 + > Maven 3.8.7 / Maven Deamon 0.8.2): > > 1) Sequential run: > $ mvn validate -Dversion.enforcer.plugin=3.0.0-M3 > === Took ~140s > > $ mvn validate -Dversion.enforcer.plugin=3.2.0-SNAPSHOT > === Took ~35s > > > 2) Parallel run (with 8 threads): > $ mvn validate -T8 -Dversion.enforcer.plugin=3.0.0-M3 > === Took ~30s > > $ mvn validate -T8 -Dversion.enforcer.plugin=3.2.0-SNAPSHOT > === Took ~10s > > > 3) Maven deamon run (with 8 threads and multiple executions to let the > daemon "warm-up"): > $ mvnd validate -T8 -Dversion.enforcer.plugin=3.0.0-M3 > === Took ~80s > $ mvnd validate -T8 -Dversion.enforcer.plugin=3.2.0-SNAPSHOT > === Took ~8s > > Note: I don't quite understand why the Maven daemon run with version > 3.0.0-M3 is so much slower comparing to the non-daemon run (80s vs 35s). I > would have to investigate further, so let's ignore those numbers for now I > guess. > > Are we expecting this kind of improvement? Or could this be somehow caused > by e.g. mistakenly not executing some of the rules? I would need to again > dig deeper, but before that it would be good to know if this is maybe > something we are expecting. > > Thanks, > Petr > > > --- Original Message --- > On Friday, January 20th, 2023 at 19:09, Slawomir Jaranowski < > s.jaranow...@gmail.com> wrote: > > > > > > > > Hi, > > > > I'm going to release the next version of Maven Enforcer plugin and build > in > > rules. > > Probably in next week - about 24-26 of January > > > > Prepared release note: > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317520=12351838 > > > > The most important: > > - New Enforcer API - https://issues.apache.org/jira/browse/MENFORCER-455 > > - Get rid of maven-dependency-tree dependency - > > https://issues.apache.org/jira/browse/MENFORCER-435 > > - Verify working with Maven 4 - > > https://issues.apache.org/jira/browse/MENFORCER-447 > > > > I will appreciate any tests on your projects. > > If something else should be added please let me know. > > > > -- > > Sławomir Jaranowski > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- Sławomir Jaranowski
[VOTE] Release Apache Maven Enforcer version 3.2.0
Hi, We solved 40 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317520=12351838 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MENFORCER%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC Staging repo: https://repository.apache.org/content/repositories/maven-1858/ https://repository.apache.org/content/repositories/maven-1858/org/apache/maven/enforcer/enforcer/3.2.0/enforcer-3.2.0-source-release.zip Source release checksum(s): enforcer-3.2.0-source-release.zip - SHA-512 : f8c33722b25f19ac40c23c2385d26a4cc5b3f352d5e8c0bd30b0c750215a38b00dc965809b206b802ce443bff52d3e02aa15a6569c286ddd04d2d2fd0585530a Staging site: https://maven.apache.org/enforcer-archives/enforcer-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 -- Sławomir Jaranowski
Re: [VOTE] Release Apache Maven Enforcer version 3.2.0
Hi, Can you provide me with your project when I can reproduce it? Or full stack. czw., 26 sty 2023 o 19:21 Delany napisał(a): > Thank you for this. My build on 3.8.7 is failing though: > > [ERROR] org.apache.maven.cli.MavenCli - Rule 0: > org.apache.maven.enforcer.rules.RequirePluginVersions failed with message: > [ERROR] org.apache.maven.cli.MavenCli - Cannot invoke > "org.apache.maven.model.Reporting.getPlugins()" because the return value of > "org.apache.maven.model.Profile.getReporting()" is null > > Delany > > On Thu, 26 Jan 2023 at 19:56, Slawomir Jaranowski > wrote: > > > Hi, > > > > We solved 40 issues: > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317520=12351838 > > > > There are still a couple of issues left in JIRA: > > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MENFORCER%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC > > > > Staging repo: > > https://repository.apache.org/content/repositories/maven-1858/ > > > > > https://repository.apache.org/content/repositories/maven-1858/org/apache/maven/enforcer/enforcer/3.2.0/enforcer-3.2.0-source-release.zip > > > > Source release checksum(s): > > enforcer-3.2.0-source-release.zip - SHA-512 : > > > > > f8c33722b25f19ac40c23c2385d26a4cc5b3f352d5e8c0bd30b0c750215a38b00dc965809b206b802ce443bff52d3e02aa15a6569c286ddd04d2d2fd0585530a > > > > Staging site: > > https://maven.apache.org/enforcer-archives/enforcer-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 > > > > -- > > Sławomir Jaranowski > > > -- Sławomir Jaranowski
Re: [VOTE] Release Apache Maven Enforcer version 3.2.0
The vote will be canceled. I will remove staging repo with next release, so if someone else will test, you can still do it. czw., 26 sty 2023 o 21:39 Slawomir Jaranowski napisał(a): > Thanks Delany, > > I see ...packaging is not important, > There are more places for NPE in this rule ... > > You can try with mvn ... -Denforcer.skipRules=RequirePluginVersions > > > czw., 26 sty 2023 o 21:19 Delany napisał(a): > >> Only happens with type POM >> >> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute >> goal org.apache.maven.plugins:maven-enforcer-plugin:3.2.0:enforce (fail) >> on >> project maven-parent: >> Rule 0: org.apache.maven.enforcer.rules.RequirePluginVersions failed with >> message: >> Cannot invoke "org.apache.maven.model.Reporting.getPlugins()" because the >> return value of "org.apache.maven.model.Profile.getReporting()" is null >> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 >> (MojoExecutor.java:375) >> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute >> (MojoExecutor.java:351) >> at org.apache.maven.lifecycle.internal.MojoExecutor.execute >> (MojoExecutor.java:215) >> at org.apache.maven.lifecycle.internal.MojoExecutor.execute >> (MojoExecutor.java:171) >> at org.apache.maven.lifecycle.internal.MojoExecutor.execute >> (MojoExecutor.java:163) >> at >> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject >> (LifecycleModuleBuilder.java:117) >> at >> >> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call >> (MultiThreadedBuilder.java:210) >> at >> >> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call >> (MultiThreadedBuilder.java:195) >> at java.util.concurrent.FutureTask.run (FutureTask.java:317) >> at java.util.concurrent.Executors$RunnableAdapter.call >> (Executors.java:577) >> at java.util.concurrent.FutureTask.run (FutureTask.java:317) >> at java.util.concurrent.ThreadPoolExecutor.runWorker >> (ThreadPoolExecutor.java:1144) >> at java.util.concurrent.ThreadPoolExecutor$Worker.run >> (ThreadPoolExecutor.java:642) >> at java.lang.Thread.run (Thread.java:1588) >> Caused by: org.apache.maven.plugin.MojoExecutionException: >> Rule 0: org.apache.maven.enforcer.rules.RequirePluginVersions failed with >> message: >> Cannot invoke "org.apache.maven.model.Reporting.getPlugins()" because the >> return value of "org.apache.maven.model.Profile.getReporting()" is null >> at org.apache.maven.plugins.enforcer.EnforceMojo.execute >> (EnforceMojo.java:271) >> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo >> (DefaultBuildPluginManager.java:137) >> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 >> (MojoExecutor.java:370) >> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute >> (MojoExecutor.java:351) >> at org.apache.maven.lifecycle.internal.MojoExecutor.execute >> (MojoExecutor.java:215) >> at org.apache.maven.lifecycle.internal.MojoExecutor.execute >> (MojoExecutor.java:171) >> at org.apache.maven.lifecycle.internal.MojoExecutor.execute >> (MojoExecutor.java:163) >> at >> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject >> (LifecycleModuleBuilder.java:117) >> at >> >> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call >> (MultiThreadedBuilder.java:210) >> at >> >> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call >> (MultiThreadedBuilder.java:195) >> at java.util.concurrent.FutureTask.run (FutureTask.java:317) >> at java.util.concurrent.Executors$RunnableAdapter.call >> (Executors.java:577) >> at java.util.concurrent.FutureTask.run (FutureTask.java:317) >> at java.util.concurrent.ThreadPoolExecutor.runWorker >> (ThreadPoolExecutor.java:1144) >> at java.util.concurrent.ThreadPoolExecutor$Worker.run >> (ThreadPoolExecutor.java:642) >> at java.lang.Thread.run (Thread.java:1588) >> [ERROR] org.apache.maven.cli.MavenCli - >> [ERROR] org.apache.maven.cli.MavenCli - >> [ERROR] org.apache.maven.cli.MavenCli - For more information about the >> errors and possible solutions, please read the following articles: >> [ERROR] org.apache.maven.cli.MavenCli - [Help 1] >> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException >> >
