Re: [VOTE] Release Apache Maven version 3.6.3
+1 (non binding) Tested using fairly big corporate project with dozen of modules and plugins. Regards, Dejan Stojadinović On 2019/11/21 20:06:06, "Robert Scholte" wrote: > Hi, > > This will be a regression release based on some critical issues discovered in > Maven 3.6.2 > > We solved 10 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922&version=12346152&styleName=Text > > Staging repo: > https://repository.apache.org/content/repositories/maven-1542/ > > https://dist.apache.org/repos/dist/dev/maven/maven-3/3.6.3/binaries/apache-maven-3.6.3-bin.tar.gz > https://dist.apache.org/repos/dist/dev/maven/maven-3/3.6.3/binaries/apache-maven-3.6.3-bin.zip > > https://dist.apache.org/repos/dist/dev/maven/maven-3/3.6.3/source/apache-maven-3.6.3-src.tar.gz > > https://dist.apache.org/repos/dist/dev/maven/maven-3/3.6.3/source/apache-maven-3.6.3-src.zip > > > Source release checksum(s): > apache-maven-3.6.3-bin.tar.gz sha512: > c35a1803a6e70a126e80b2b3ae33eed961f83ed74d18fcd16909b2d44d7dada3203f1ffe726c17ef8dcca2dcaa9fca676987befeadc9b9f759967a8cb77181c0 > apache-maven-3.6.3-bin.zip sha512: > 1c095ed556eda06c6d82fdf52200bc4f3437a1bab42387e801d6f4c56e833fb82b16e8bf0aab95c9708de7bfb55ec27f653a7cf0f491acebc541af234eded94d > > apache-maven-3.6.3-src.tar.gz sha512: > 14eef64ad13c1f689f2ab0d2b2b66c9273bf336e557d81d5c22ddb001c47cf51f03bb1465d6059ce9fdc2e43180ceb0638ce914af1f53af9c2398f5d429f114c > > apache-maven-3.6.3-src.zip sha512: > b23b7ae7392eca28ec124cf8ad24bb27405aea5d252d9305bb37a6e317947cc7dc15a564958a113ab75e2010e16c293d6e7c44f7d41d7bad7635d2d76eb4d1ac > > Staging site: > http://maven.apache.org/ref/3-LATEST/ > > Guide to testing staged releases: > https://maven.apache.org/guides/development/guide-testing-releases.html > > Vote open for at least 72 hours. > > [ ] +1 > [ ] +0 > [ ] -1 > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Same snapshot deploy number for entire build - possible
@Dan Tran use 'deployAtEnd': org.apache.maven.plugins maven-deploy-plugin someVersion true https://maven.apache.org/plugins/maven-deploy-plugin/deploy-mojo.html Regards, Dejan S. On 2019/09/13 10:02:33, Dan Tran wrote: > Looks like I need to clear thing a little bit > > Assume I have a reactor of few hundreds of maven modules and my CI > build deploys snapshots, first few good builds, each module deployed to > maven repository have same snapshot number > > Once we encounter a build failure at a module, the snapshot number begins > to vary and over time, all modules no longer have the same snapshot number > anymore > > To be able to determine a consistent snapshot number at each build, I > would like to have an ability the tell deploy maven plugin to use an > assigned number for all modules. > > Possible? > > Thanks > > -D > > > > > > > On Thu, Sep 12, 2019 at 11:31 PM Enrico Olivelli > wrote: > > > Dan, > > Are you running a single 'mvn deploy' or do you have multiple runs? > > I have never seen weird behaviours in multi module projects > > > > Cheers > > Enrico > > > > Il ven 13 set 2019, 08:19 Dan Tran ha scritto: > > > > > Hello, Maven dev > > > > > > any suggestion/thoughts on this issue are very much appreciated > > > > > > Regards > > > > > > -D > > > > > > On Wed, Sep 11, 2019 at 7:06 PM Dan Tran wrote: > > > > > > > Hello Maven Users and Development Team > > > > > > > > Currently, artifact deployed as snapshot at Maven repository has the > > > > following format > > > > > > > > artifactId-version-timestamp-NN > > > > > > > > where NN auto-incremented at each maven module and the number varies > > > > > > > > Is there a way to use same snapshot NN for the entire multi-module > > maven > > > > build? > > > > > > > > If I have to implement a solution, would it be as an extension or I > > have > > > > to tinker with maven-deploy-plugin? > > > > > > > > Very appreciated any advice > > > > > > > > -D > > > > > > > > > > > > > > > > > > > > > > > > > > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: looking for some volunteer
@Tibor please review https://github.com/apache/maven-surefire/pull/233 On 2019/05/06 13:37:02, Tibor Digana wrote: > Hello Dejan, I am glad that you are back again. > yes, feel free. Github is yours. > T > > On Mon, May 6, 2019 at 2:29 PM Dejan Stojadinovic > wrote: > > > This one slipped slipped though the cracks (I was few weeks off the grid > > due to traveling). Let me try to push something soon (if it is not too > > late). > > > > On 2019/04/07 01:19:13, Tibor Digana wrote: > > > Hi Dejan, > > > > > > I almost forgot your email. > > > Pls create a PR on GitHub with a little work even if still incomplete but > > > at least we would not forget it. > > > As you can see in [1] we should create release branches and for your PR > > as > > > well. > > > [1]: https://github.com/apache/maven-surefire/pull/227 > > > > > > Cheers > > > Tibor > > > > > > > > > On Tue, Mar 26, 2019 at 9:24 AM Dejan Stojadinovic > > > wrote: > > > > > > > Thanx Tibor, I left short comments on JIRA issues (just to mark them). > > > > I hope I will squeeze first github PR in a few days. > > > > > > > > Regards, > > > > Dejan > > > > > > > > On 2019/03/24 23:19:08, Tibor Digana wrote: > > > > > Hi Dejan, > > > > > > > > > > Good to hear. In our Jira are two issues related to my original > > email: > > > > > https://issues.apache.org/jira/browse/SUREFIRE-1654 > > > > > https://issues.apache.org/jira/browse/SUREFIRE-1494 > > > > > If you have any questions, feel free to ask here. > > > > > Pls run the build locally (mvn -P run-its install) until our TravisCI > > > > build > > > > > would be ready for you. The build takes cca 1 hour to complete. > > > > > We should solve these two issue in two separate pull requests. > > > > > I guess these tasks require very good preparation and analysis of ITs > > > > > before making any changes. > > > > > > > > > > @Enrico can you pls investigate TravisCI, why it still behaves so > > much > > > > > differently from Jenkins CI and fails? > > > > > Is it really due to the deployed SNAPSHOT versions at ASF Nexus? > > > > > > > > > > Thx > > > > > > > > > > Cheers > > > > > Tibor > > > > > > > > > > > > > > > On Sun, Mar 24, 2019 at 3:23 PM Dejan Stojadinovic < > > dejan2...@gmail.com> > > > > > wrote: > > > > > > > > > > > Hi Tibor, > > > > > > > > > > > > I volunteer for this. I have a solid experience with maven usage > > and > > > > also > > > > > > contributed few (easy) maven commits: > > > > > > https://github.com/apache/maven/commits?author=dejan2609 > > > > > > > > > > > > Regards, > > > > > > Dejan Stojadinović > > > > > > > > > > > > On 2019/03/23 21:47:04, Tibor Digana > > wrote: > > > > > > > It's going to be very pedant work for someone who want to help > > us in > > > > > > > Surefire. > > > > > > > > > > > > > > I am looking for some volunteer who will remove the deprecated > > config > > > > > > param > > > > > > > `forkMode` in favor of `forkCount`. All our ITs should use > > > > `forkCount` > > > > > > > since then. > > > > > > > > > > > > > > Additionally, the volunteer should deprecate `surefire-junit4` > > > > provider. > > > > > > > Instead `surefire-junit47` provider should be selected as default > > > > > > provider > > > > > > > for JUnit4 tests. Again the ITs should be changed and plugin > > > > dependencies > > > > > > > should use `surefire-junit4` provider in place where it was not > > > > > > specified. > > > > > > > > > > > > > > It's easy to do. When you see the usages of `.forkMode()` method > > - > > > > only > > > > > > 20 > > > > > > > in `surefire-its` and 43 usages of `` in > > > > > > > `surefire-its/src/test/resources`. > > > > > > > > > > > > > > Successful build must prove that the changes have been applied > > > > correctly. > > > > > > > The changes should be in a pull request on GitHub. > > > > > > > > > > > > > > Cheers > > > > > > > Tibor > > > > > > > > > > > > > > > > > > > > > - > > > > > > 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 > > > > > > > > > > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: looking for some volunteer
This one slipped slipped though the cracks (I was few weeks off the grid due to traveling). Let me try to push something soon (if it is not too late). On 2019/04/07 01:19:13, Tibor Digana wrote: > Hi Dejan, > > I almost forgot your email. > Pls create a PR on GitHub with a little work even if still incomplete but > at least we would not forget it. > As you can see in [1] we should create release branches and for your PR as > well. > [1]: https://github.com/apache/maven-surefire/pull/227 > > Cheers > Tibor > > > On Tue, Mar 26, 2019 at 9:24 AM Dejan Stojadinovic > wrote: > > > Thanx Tibor, I left short comments on JIRA issues (just to mark them). > > I hope I will squeeze first github PR in a few days. > > > > Regards, > > Dejan > > > > On 2019/03/24 23:19:08, Tibor Digana wrote: > > > Hi Dejan, > > > > > > Good to hear. In our Jira are two issues related to my original email: > > > https://issues.apache.org/jira/browse/SUREFIRE-1654 > > > https://issues.apache.org/jira/browse/SUREFIRE-1494 > > > If you have any questions, feel free to ask here. > > > Pls run the build locally (mvn -P run-its install) until our TravisCI > > build > > > would be ready for you. The build takes cca 1 hour to complete. > > > We should solve these two issue in two separate pull requests. > > > I guess these tasks require very good preparation and analysis of ITs > > > before making any changes. > > > > > > @Enrico can you pls investigate TravisCI, why it still behaves so much > > > differently from Jenkins CI and fails? > > > Is it really due to the deployed SNAPSHOT versions at ASF Nexus? > > > > > > Thx > > > > > > Cheers > > > Tibor > > > > > > > > > On Sun, Mar 24, 2019 at 3:23 PM Dejan Stojadinovic > > > wrote: > > > > > > > Hi Tibor, > > > > > > > > I volunteer for this. I have a solid experience with maven usage and > > also > > > > contributed few (easy) maven commits: > > > > https://github.com/apache/maven/commits?author=dejan2609 > > > > > > > > Regards, > > > > Dejan Stojadinović > > > > > > > > On 2019/03/23 21:47:04, Tibor Digana wrote: > > > > > It's going to be very pedant work for someone who want to help us in > > > > > Surefire. > > > > > > > > > > I am looking for some volunteer who will remove the deprecated config > > > > param > > > > > `forkMode` in favor of `forkCount`. All our ITs should use > > `forkCount` > > > > > since then. > > > > > > > > > > Additionally, the volunteer should deprecate `surefire-junit4` > > provider. > > > > > Instead `surefire-junit47` provider should be selected as default > > > > provider > > > > > for JUnit4 tests. Again the ITs should be changed and plugin > > dependencies > > > > > should use `surefire-junit4` provider in place where it was not > > > > specified. > > > > > > > > > > It's easy to do. When you see the usages of `.forkMode()` method - > > only > > > > 20 > > > > > in `surefire-its` and 43 usages of `` in > > > > > `surefire-its/src/test/resources`. > > > > > > > > > > Successful build must prove that the changes have been applied > > correctly. > > > > > The changes should be in a pull request on GitHub. > > > > > > > > > > Cheers > > > > > Tibor > > > > > > > > > > > > > - > > > > 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 > > > > > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: looking for some volunteer
Thanx Tibor, I left short comments on JIRA issues (just to mark them). I hope I will squeeze first github PR in a few days. Regards, Dejan On 2019/03/24 23:19:08, Tibor Digana wrote: > Hi Dejan, > > Good to hear. In our Jira are two issues related to my original email: > https://issues.apache.org/jira/browse/SUREFIRE-1654 > https://issues.apache.org/jira/browse/SUREFIRE-1494 > If you have any questions, feel free to ask here. > Pls run the build locally (mvn -P run-its install) until our TravisCI build > would be ready for you. The build takes cca 1 hour to complete. > We should solve these two issue in two separate pull requests. > I guess these tasks require very good preparation and analysis of ITs > before making any changes. > > @Enrico can you pls investigate TravisCI, why it still behaves so much > differently from Jenkins CI and fails? > Is it really due to the deployed SNAPSHOT versions at ASF Nexus? > > Thx > > Cheers > Tibor > > > On Sun, Mar 24, 2019 at 3:23 PM Dejan Stojadinovic > wrote: > > > Hi Tibor, > > > > I volunteer for this. I have a solid experience with maven usage and also > > contributed few (easy) maven commits: > > https://github.com/apache/maven/commits?author=dejan2609 > > > > Regards, > > Dejan Stojadinović > > > > On 2019/03/23 21:47:04, Tibor Digana wrote: > > > It's going to be very pedant work for someone who want to help us in > > > Surefire. > > > > > > I am looking for some volunteer who will remove the deprecated config > > param > > > `forkMode` in favor of `forkCount`. All our ITs should use `forkCount` > > > since then. > > > > > > Additionally, the volunteer should deprecate `surefire-junit4` provider. > > > Instead `surefire-junit47` provider should be selected as default > > provider > > > for JUnit4 tests. Again the ITs should be changed and plugin dependencies > > > should use `surefire-junit4` provider in place where it was not > > specified. > > > > > > It's easy to do. When you see the usages of `.forkMode()` method - only > > 20 > > > in `surefire-its` and 43 usages of `` in > > > `surefire-its/src/test/resources`. > > > > > > Successful build must prove that the changes have been applied correctly. > > > The changes should be in a pull request on GitHub. > > > > > > Cheers > > > Tibor > > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: looking for some volunteer
Hi Tibor, I volunteer for this. I have a solid experience with maven usage and also contributed few (easy) maven commits: https://github.com/apache/maven/commits?author=dejan2609 Regards, Dejan Stojadinović On 2019/03/23 21:47:04, Tibor Digana wrote: > It's going to be very pedant work for someone who want to help us in > Surefire. > > I am looking for some volunteer who will remove the deprecated config param > `forkMode` in favor of `forkCount`. All our ITs should use `forkCount` > since then. > > Additionally, the volunteer should deprecate `surefire-junit4` provider. > Instead `surefire-junit47` provider should be selected as default provider > for JUnit4 tests. Again the ITs should be changed and plugin dependencies > should use `surefire-junit4` provider in place where it was not specified. > > It's easy to do. When you see the usages of `.forkMode()` method - only 20 > in `surefire-its` and 43 usages of `` in > `surefire-its/src/test/resources`. > > Successful build must prove that the changes have been applied correctly. > The changes should be in a pull request on GitHub. > > Cheers > Tibor > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Surefire Plugin version 2.22.1
+1 (non-binding). Note: tested using fairly large project. Regards, Dejan Stojadinović On 2018/10/08 08:22:38, Tibor Digana wrote: > Hi, > > We solved 17 issues: > https://issues.apache.org/jira/projects/SUREFIRE/versions/12343425 > > There are still a couple of issues left in JIRA: > https://issues.apache.org/jira/issues/?jql=project%20%3D%20SUREFIRE%20AND%20status%20%3D%20Open%20ORDER%20BY%20priority%20DESC > > Staging repo: > https://repository.apache.org/content/repositories/maven-1455/ > https://repository.apache.org/content/repositories/maven-1455/org/apache/maven/surefire/surefire/2.22.1/surefire-2.22.1-source-release.zip > > Source release checksum(s): > surefire-2.22.1-source-release.zip sha512: > 4a3561aae3478f4eefe0d0d6f8575ace746bbf267663f5361733b382f51d290672c61100d8d15e8b734607c63edfc33b4e61b4e1ddae10af0f2dfc04d20f38a4 > surefire-2.22.1-source-release.zip sha1: > 13ed29cbba215ef7f383985024a0e8be274ba41f > > Staging site: > http://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 at least 72 hours. > > [ ] +1 > [ ] +0 > [ ] -1 > > -- > Cheers > Tibor > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven 3.5.4
+1 (non-binding). Tested via two projects: 1. large multi module project that uses following plugins: * org.apache.maven.plugins: ** maven-clean-plugin:3.1.0 ** maven-enforcer-plugin:3.0.0-M2 ** maven-resources-plugin:3.1.0 ** maven-source-plugin:3.0.1 ** maven-dependency-plugin:3.1.1 ** maven-compiler-plugin:3.7.0 ** maven-jar-plugin:3.1.0 ** maven-war-plugin:3.2.2 ** maven-ear-plugin:3.0.1 ** maven-antrun-plugin:1.8 ** maven-surefire-plugin:2.22.0 ** maven-checkstyle-plugin:3.0.0 ** maven-project-info-reports-plugin:2.9 ** maven-site-plugin:3.7.1 * org.codehaus.mojo: ** animal-sniffer-maven-plugin:1.16 ** build-helper-maven-plugin:3.0.0 ** findbugs-maven-plugin:3.0.5 * other notable plugins: ** org.sonarsource.scanner.maven:sonar-maven-plugin:3.4.0.905 ** org.owasp:dependency-check-maven:3.2.1 ** org.flywaydb:flyway-maven-plugin:4.1.2 2. mid-size legacy project that uses these plugins: * org.reflections:reflections-maven:0.9.9-RC2 * com.webcohesion.enunciate:enunciate-maven-plugin:2.11.1 Environments: * CentOS Linux release 7.5.1804 (Core) + Jenkins 2.89.4 LTS with Maven Integration plugin 3.1.2, Sonatype Nexus 2.14.8-01, SonarQube 6.7.4 LTS * Windows 10 (desktop) Java version (for both Linux and Windows): 1.8.0_171 (Oracle) Regards and thank you for your work. Dejan On 2018/06/19 05:35:37, Romain Manni-Bucau wrote: > +1 tested on my projects and mojo and all is green :) > > Le mar. 19 juin 2018 07:01, Karl Heinz Marbaise a > écrit : > > > Hi, > > > > here is my +1 > > > > Tested on several projects without any issue... > > > > Kind regards > > Karl Heinz Marbaise > > On 17/06/18 22:44, Stephen Connolly wrote: > > > Hi, > > > > > > We solved 16 issues: > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12342826&styleName=Text&projectId=12316922 > > > > > > There are 356 issues left in JIRA for Maven core: > > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC > > > > > > Staging repo: > > > https://repository.apache.org/content/repositories/maven-1438/ > > > > > > The distributable binaries and sources can be found here: > > > > > https://repository.apache.org/content/repositories/maven-1438/org/apache/maven/apache-maven/3.5.4/ > > > > > > Specifically the zip, tarball and source archives can be found here: > > > > > https://repository.apache.org/content/repositories/maven-1438/org/apache/maven/apache-maven/3.5.4/apache-maven-3.5.4-bin.zip > > > > > https://repository.apache.org/content/repositories/maven-1438/org/apache/maven/apache-maven/3.5.4/apache-maven-3.5.4-bin.tar.gz > > > > > https://repository.apache.org/content/repositories/maven-1438/org/apache/maven/apache-maven/3.5.4/apache-maven-3.5.4-src.zip > > > > > https://repository.apache.org/content/repositories/maven-1438/org/apache/maven/apache-maven/3.5.4/apache-maven-3.5.4-src.tar.gz > > > > > > The release artifacts are staged for distribution in: > > > https://dist.apache.org/repos/dist/dev/maven/maven-3/3.5.4 > > > > > > Source release checksum(s): > > > apache-maven-3.5.4-src.tar.gz sha1: > > > 04aefb9462af8cf7ca93808cd246f4c28b8ae4a1 sha256: > > > f3ba1f1b24bbd4c345174ac616d40e26e72dad6022d56317d3ff6f7dd003e2f5 > > > apache-maven-3.5.4-src.zip: sha1: > > 1ee9850a046860d71267a043a29e0aa9acc13bcd > > > sha256: ddcddecc8048d24edd3fa98fe50ae7f6a753389367d24593bf39e37427f643f5 > > > > > > Git tag: > > > > > https://gitbox.apache.org/repos/asf?p=maven.git;a=commit;h=1edded0938998edf8bf061f1ceb3cfdeccf443fe > > > > > > Staging site: > > > https://maven.apache.org/components/ref/3-LATEST/ > > > > > > Vote open for 72 hours. > > > > > > [ ] +1 > > > [ ] +0 > > > [ ] -1 > > > > > > Thanks, > > > > > > Stephen. > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: migrating some code to Git
Count me in (for both actual migration and related tasks). My weapon of choice for SVN -->>GIT would be: https://github.com/nirvdrum/svn2git (I managed to move dozen of repos few years ago). Regards, Dejan On 2017-10-04 01:48, Hervé BOUTEMY wrote: > I'd like to work on Plugin Tools with git > > While at it, looking at our plan [1], I see we have a few other components > that are ready to migrate: > - Doxia core > - Doxia Sitetools > - Enforcer > - Jxr > - Plugin Tools > - Release > > What checks are required before switching these 6 components? > Any volunteer? > > Regards, > > Hervé > > [1] https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration > > - > 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
