Re: [VOTE] Release Apache Maven Jarsigner version 3.0.0
+1 On Fri, 26 Oct 2018 at 11:23 pm, Robert Scholte wrote: > Hi, > > We solved 12 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12335540=Text > > There are still a couple of issues left in JIRA: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317922%20AND%20component%20%3D%20maven-jarsigner%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC > > Staging repo: > https://repository.apache.org/content/repositories/maven-1460/ > > https://repository.apache.org/content/repositories/maven-1460/org/apache/maven/shared/maven-jarsigner/3.0.0/maven-jarsigner-3.0.0-source-release.zip > > Source release checksum(s): > maven-jarsigner-3.0.0-source-release.zip sha512: > > 36dfd963ed1e3b3f646b03ade29452422bd0d0aabb6fccb480498ebf9ce2234e2b560332cb20c4fff76e11e39da82816fa652b81c6ebad9e650cfd4b75a15486 > > Staging site: > https://maven.apache.org/shared-archives/maven-jarsigner-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 > > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: [VOTE] Release Apache Maven Jarsigner version 3.0.0
+1 On Fri, Oct 26, 2018 at 3:23 PM Robert Scholte wrote: > Hi, > > We solved 12 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12335540=Text > > There are still a couple of issues left in JIRA: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317922%20AND%20component%20%3D%20maven-jarsigner%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC > > Staging repo: > https://repository.apache.org/content/repositories/maven-1460/ > > https://repository.apache.org/content/repositories/maven-1460/org/apache/maven/shared/maven-jarsigner/3.0.0/maven-jarsigner-3.0.0-source-release.zip > > Source release checksum(s): > maven-jarsigner-3.0.0-source-release.zip sha512: > > 36dfd963ed1e3b3f646b03ade29452422bd0d0aabb6fccb480498ebf9ce2234e2b560332cb20c4fff76e11e39da82816fa652b81c6ebad9e650cfd4b75a15486 > > Staging site: > https://maven.apache.org/shared-archives/maven-jarsigner-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: [VOTE] Release Apache Maven 3.6.0
+1 non-binding from my side, I used our division pom project for testing which runs verify builds for another 11 in-house projects. Regards Mirko > Am 24.10.2018 um 21:50 schrieb Karl Heinz Marbaise : > > Hi, > > We have solved 26 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12338966 > > There are 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%20key%20DESC%2C%20priority%20DESC%2C%20updated%20DESC > > Staging repo: > https://repository.apache.org/content/repositories/maven-1459 > > The distributable binaries and sources can be found here: > https://repository.apache.org/content/repositories/maven-1459/org/apache/maven/apache-maven/3.6.0/ > > Specifically the zip, tarball and source archives can be found here: > > https://repository.apache.org/content/repositories/maven-1459/org/apache/maven/apache-maven/3.6.0/apache-maven-3.6.0-bin.zip > https://repository.apache.org/content/repositories/maven-1459/org/apache/maven/apache-maven/3.6.0/apache-maven-3.6.0-bin.tar.gz > > https://repository.apache.org/content/repositories/maven-1459/org/apache/maven/apache-maven/3.6.0/apache-maven-3.6.0-src.zip > https://repository.apache.org/content/repositories/maven-1459/org/apache/maven/apache-maven/3.6.0/apache-maven-3.6.0-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.6.0-src.tar.gz > > sha1: 255d8057b7f014222e96137001d4f4aa05d4a7cb > sha512: > 5b4b5ca569d5476f9d6a2b8080927f58da9ca10a04c593df3d8c012e60fdcf7dcf70c4bc5db0d068b3a36785ede62a55fd1778b22ecadcf787485681ddc758a8 > > apache-maven-3.6.0-src.zip: > > sha1: 6149f259489acf36e2c04ec0dd713f99336b3346 > sha512: > c5794a6723d8d0fc8ff447b42e5a8c13524a44f8508a305d463f811c8039c7e9166d709077c8373d3cf980ce24feaebb2431cb50fb274933ab3bc2a90355 > > Git tag: > https://gitbox.apache.org/repos/asf?p=maven.git;a=commit;h=97c98ec64a1fdfee7767ce5ffb20918da4f719f3 > > Staging site: > https://maven.apache.org/components/ref/3-LATEST/ > > Vote open for 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 > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[VOTE] Release Apache Maven Jarsigner version 3.0.0
Hi, We solved 12 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12335540=Text There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317922%20AND%20component%20%3D%20maven-jarsigner%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC Staging repo: https://repository.apache.org/content/repositories/maven-1460/ https://repository.apache.org/content/repositories/maven-1460/org/apache/maven/shared/maven-jarsigner/3.0.0/maven-jarsigner-3.0.0-source-release.zip Source release checksum(s): maven-jarsigner-3.0.0-source-release.zip sha512: 36dfd963ed1e3b3f646b03ade29452422bd0d0aabb6fccb480498ebf9ce2234e2b560332cb20c4fff76e11e39da82816fa652b81c6ebad9e650cfd4b75a15486 Staging site: https://maven.apache.org/shared-archives/maven-jarsigner-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: FOSDEM BoF - how do I apply for one?
Hi Robert, thanks for the reply! I also got the following from Gerry Demaret (at i...@fosdem.org): "You can not request a slot in a BoF room at this point. We will announce more information on BoF sessions closer to the event." I feel it's a bit of a shame that you can't plan ahead on a BoF, but I do understand that interest can vary and it's wasteful to reserve a space for a BoF and have no one or just few people show up... thanks :) zoran On Fri, Oct 26, 2018 at 10:56 AM, Robert Scholte wrote: > Hi Zoran, > > BOFs are organized at the location during the event. > To me the word BOF is here a bit misleading. > See it like this: if you are there and have the need to discuss things with > a group, you try to claim a timeslot on a paper on the wall. Everybody can > see this paper and decide to visit it. > So we're often there with a small group wanting to discuss some hard topics > that cannot be done via email. > Visitors will enter the room, we sometimes ask them if they have some > specific questions, but also warn them that these discussions are hardcore. > > In conclusion: there's nothing to do/prepare right now. BOFs are organized > during FOSDEM. > > thanks, > Robert > > > On Thu, 18 Oct 2018 17:02:43 +0200, Zoran Regvart wrote: > >> Hi Mavens, >> for Apache Camel I'd like to organize a BoF at FOSDEM 2019, I noticed >> that Maven had one back in 2017[1], can anyone help me in >> understanding how are BoF sessions organized? >> >> I assume I need to apply for the venue but I'm not clear on how? >> >> thanks :) >> >> zoran >> >> [1] >> https://archive.fosdem.org/2017/schedule/event/apache_maven_jigsaw_bof/ -- Zoran Regvart - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[ANN] Apache Maven PMD Plugin 3.11.0 Released
The Maven team is pleased to announce the release of the Apache Maven PMD Plugin, version 3.11.0 A Maven plugin for the PMD toolkit, that produces a report on both code rule violations and detected copy and paste fragments, as well as being able to fail the build based on these metrics. https://maven.apache.org/plugins/maven-pmd-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-pmd-plugin 3.11.0 Release Notes - Apache Maven PMD Plugin - Version 3.11.0 Bug * [MPMD-268] Missing warnings about deprecated rules * [MPMD-266] Aggregate report in multi-module projects doesn't use correct auxclasspath New Feature * [MPMD-272] Support ignoreAnnotations options for CPD Task * [MPMD-271] Upgrade pmd 6.8.0 * [MPMD-270] JDK 11 compatibility Enjoy, -The Maven team
Re: [maven-javadoc-plugin] branch master updated: revert upgrade plexus-java because enforcer complains.
Just verified: it is already implemented. Upgrading extra-enforcer-rules to 1.0-beta-9 solves this issue. Robert On Thu, 18 Oct 2018 10:24:35 +0200, Robert Scholte wrote: Yes, this is a missing feature in Maven enforcer plugin. It should verify byte code version with meta-inf/versions/X.Iirc I made a start with it. Verzonden vanaf mijn Samsung Galaxy-smartphone. Oorspronkelijk bericht Van: Olivier Lamy Datum: 18-10-18 10:47 (GMT+03:00) Aan: Maven Developers List Onderwerp: Re: [maven-javadoc-plugin] branch master updated: revert upgrade plexus-java because enforcer complains. I reverted that because enforcer complains. [windows-jdk9-m3.5.x_build] [INFO] Restricted to JDK 1.7 yet org.codehaus.plexus:plexus-java:jar:0.9.11:compile contains META-INF/versions/9/org/codehaus/plexus/languages/java/jpms/BinaryModuleInfoParser.class targeted to JDK 1.9 [windows-jdk9-m3.5.x_build] [WARNING] Rule 0: org.apache.maven.plugins.enforcer.EnforceBytecodeVersion failed with message: [windows-jdk9-m3.5.x_build] Found Banned Dependency: org.codehaus.plexus:plexus-java:jar:0.9.11 Sounds like a bug with enforcer? META-INF/versions/9 (META-INF/versions/x) shouldn't be a problem? org.codehaus.plexus:plexus-java:jar:0.9.11 is required for jdk11 (if you compile with target 11) but we cannot upgrade because of this. well users can still upgrade the dependency in their pom but it's not something automatic. WDYT? On Thu, 18 Oct 2018 at 17:42, wrote: This is an automated email from the ASF dual-hosted git repository. olamy pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/maven-javadoc-plugin.git The following commit(s) were added to refs/heads/master by this push: new 972fbbc revert upgrade plexus-java because enforcer complains. 972fbbc is described below commit 972fbbc199350e8b222d0da7f75b1d95d30b7bd9 Author: Olivier Lamy AuthorDate: Thu Oct 18 17:42:38 2018 +1000 revert upgrade plexus-java because enforcer complains. --- pom.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pom.xml b/pom.xml index ac74f4b..fa19d3e 100644 --- a/pom.xml +++ b/pom.xml @@ -234,7 +234,7 @@ under the License. org.codehaus.plexus plexus-java - 0.9.11 + 0.9.8 org.codehaus.plexus - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: FOSDEM BoF - how do I apply for one?
Hi Zoran, BOFs are organized at the location during the event. To me the word BOF is here a bit misleading. See it like this: if you are there and have the need to discuss things with a group, you try to claim a timeslot on a paper on the wall. Everybody can see this paper and decide to visit it. So we're often there with a small group wanting to discuss some hard topics that cannot be done via email. Visitors will enter the room, we sometimes ask them if they have some specific questions, but also warn them that these discussions are hardcore. In conclusion: there's nothing to do/prepare right now. BOFs are organized during FOSDEM. thanks, Robert On Thu, 18 Oct 2018 17:02:43 +0200, Zoran Regvart wrote: Hi Mavens, for Apache Camel I'd like to organize a BoF at FOSDEM 2019, I noticed that Maven had one back in 2017[1], can anyone help me in understanding how are BoF sessions organized? I assume I need to apply for the venue but I'm not clear on how? thanks :) zoran [1] https://archive.fosdem.org/2017/schedule/event/apache_maven_jigsaw_bof/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
