[GitHub] maven-indexer pull request: MINDEXER-82

Github user asfgit closed the pull request at: https://github.com/apache/maven-indexer/pull/3 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

[GitHub] maven-indexer pull request: MINDEXER-80

Github user asfgit closed the pull request at: https://github.com/apache/maven-indexer/pull/4 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

[GitHub] maven-indexer pull request: WIP Multiple fixes sixpack

GitHub user cstamas opened a pull request: https://github.com/apache/maven-indexer/pull/5 WIP Multiple fixes sixpack Multiple fixes: MINDEXER-84 updater bug MINDEXER-85 POM reading MINDEXER-86 legacy transport format removed MINDEXER-41 unique by GAVCE from now on

troubleshooting nexus gpg signature validation failures

I am trying to stage maven plugin test 3.2.0 but Nexus does not let me close the staging repository because of gpg signature validation failure. Looks like nexus is configured to check three key servers, http://gpg-keyserver.de/, http://pool.sks-keyservers.net:11371 and http://pgp.mit.edu:11371

[GitHub] maven-indexer pull request: WIP Multiple fixes sixpack

Github user carlspring commented on the pull request: https://github.com/apache/maven-indexer/pull/5#issuecomment-48323441 +1: This looks good to me, especially MINDEXER-41 and being able to search by extensions. --- If your project is set up for it, you can reply to this email and

Re: troubleshooting nexus gpg signature validation failures

Never mind, nexus was just tired, it worked the second time I attempted to close the repo. -- Regards, Igor On 2014-07-08, 15:01, Igor Fedorenko wrote: I am trying to stage maven plugin test 3.2.0 but Nexus does not let me close the staging repository because of gpg signature validation

[VOTE] Release Apache Maven Plugin Testing version 3.2.0

Hi, We solved 4 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11740version=20039 There are no issues left in JIRA Staging repo: https://repository.apache.org/content/repositories/maven-1039/

Re: [VOTE] Release Apache Maven Plugin Testing version 3.2.0

+1 On Jul 8, 2014, at 7:58 AM, Igor Fedorenko i...@ifedorenko.com wrote: Hi, We solved 4 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11740version=20039 There are no issues left in JIRA Staging repo: https://repository.apache.org/content/repositories/maven-1039/

Re: Maven Developer Hangout

and this is even worse when an artifact has been downloaded as part of a plugin used during build: an artifact used by a plugin should not be available as a build dependency so as explained in compatibility notes [1], this not really about fearing different artifacts from multiples repos, but

[VOTE] Release Apache Maven Source Plugin version 2.3

Hi, We solved 5 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11147version=18848 There are still a couple of issues left in JIRA: http://jira.codehaus.org/issues/?jql=project%20%3D%20MSOURCES%20AND%20status%20%3D%20Open%20ORDER%20BY%20priority%20DESC Staging repo:

Re: [VOTE] Release Apache Maven Plugin Testing version 3.2.0

Hi, checked SHA1 Ok. Tested with Maven 3.2.1, 3.1.1, 3.0.5 Based on that I have found a small thing The maven version can't be controlled by prerequisites only via maven-enforcer-plugin so this will not work in Maven 3.X ...but this not an issue for the release... +1 (non binding)

Re: [VOTE] Release Apache Maven Plugin Testing version 3.2.0

I am not sure I understand your concern about Maven versions. The test harness itself can be built with pretty much any version of Maven and I expect any 3.x to work, but the plugins that use plugin testing 3.2.0 will have to use depend on Maven 3.2.1 or newer. -- Regards, Igor On 2014-07-09,

Re: [VOTE] Release Apache Maven Plugin Testing version 3.2.0

Hi Igor, I am not sure I understand your concern about Maven versions. The test harness itself can be built with pretty much any version of Maven Unfortunately this is not true...you can't build with Maven 2.2.1 cause you will get things like this: [INFO] Scanning for projects... [INFO]

Re: [VOTE] Release Apache Maven Plugin Testing version 3.2.0

It's for plugins and that enforces the version of Maven it can run in. Purely a runtime check. It doesn't check anything at build time. On Jul 8, 2014, at 4:40 PM, Karl Heinz Marbaise khmarba...@gmx.de wrote: Hi Igor, I am not sure I understand your concern about Maven versions. The test

[GitHub] maven-plugins pull request: Upgarding to use latest PMD to support...

GitHub user sjonnalagadda opened a pull request: https://github.com/apache/maven-plugins/pull/27 Upgarding to use latest PMD to support JDK 1.8 code base PMD version 5.0.0 used in 3.1 version is not validating JDK 1.8 projects. Bumped PMD to 5.1.1 and changed enforcer plugin rules

Re: Hangout summary?

I don't really mind participating. I just want to be able to read what happened in an async way (notes in our wiki or in the web site). As it I'm able to react on something I will read (even if I don't participate in this hangout or in an irc discussion) IMHO a lot of people are in the same

Re: Hangout summary?

Bloody Kiwis ;-) 6am is fine for me. On Fri, Jul 4, 2014 at 7:52 AM, Mark Derricutt m...@talios.com wrote: On 4 Jul 2014, at 9:33, Robert Scholte wrote: If I'm correct, following have joined at least 2 times or are Maven PMC 22:00-23:00 (CEST) Robert Scholte, Hervé Boutemy, Karl-Heinz

Re: Hangout summary?

On 9 Jul 2014, at 16:19, William Ferguson wrote: Bloody Kiwis ;-) 6am is fine for me. 6am could be fine for me as well, I just might not be wearing pants :) Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org