[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 is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[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 is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[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 Also, artifacts made searchable by ext Some build related fixes You can merge this pull request into a Git repository by running: $ git pull https://github.com/cstamas/maven-indexer sixpack Alternatively you can review and apply these changes as the patch at: https://github.com/apache/maven-indexer/pull/5.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5 commit 22fbfe07ae012e1c2c115dc9ebed1dc3dae14b8a Author: Tamas Cservenak ta...@cservenak.net Date: 2014-06-29T17:28:03Z Multiple fixes: MINDEXER-84 updater bug MINDEXER-85 POM reading MINDEXER-86 legacy transport format removed MINDEXER-41 unique by GAVCE from now on commit 11bd6b96465cb6b9d3f51378e5dc47616541fb61 Author: Tamas Cservenak ta...@cservenak.net Date: 2014-06-29T17:41:00Z Add file ext to be searchable. commit 85dace84a9088c59b4de17ea2a957c24f45febb1 Author: Tamas Cservenak ta...@cservenak.net Date: 2014-07-08T08:59:41Z Merge remote-tracking branch 'asf/master' into sixpack Conflicts: indexer-core/src/main/java/org/apache/maven/index/incremental/DefaultIncrementalHandler.java indexer-core/src/main/java/org/apache/maven/index/packer/DefaultIndexPacker.java commit 875d7b4c6f6de0a965b443cb963a937cac9f24b6 Author: Tamas Cservenak ta...@cservenak.net Date: 2014-07-08T10:09:02Z Fixing the tests and more relates to previous changes mostly in tests, to not pollute randomly created files the build itself --- 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 is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
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 and all three appear to fail to validate my key. Here is actual error message for one of the servers No public key: Key with id: (f704b943ed330e1b) was not able to be located on http://pool.sks-keyservers.net:11371. Upload your public key and try the operation again. This is not a new key and am quite certain I used it for Apache releases in the past. http://gpg-keyserver.de/ appears to be down, at least from where I am right now, http://pgp.mit.edu:11371 times out with http 502. http://pool.sks-keyservers.net:11371 finds the key in question. I am lost at this point. Any help will be appreciated. -- Regards, Igor - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[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 have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
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 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 and all three appear to fail to validate my key. Here is actual error message for one of the servers No public key: Key with id: (f704b943ed330e1b) was not able to be located on http://pool.sks-keyservers.net:11371. Upload your public key and try the operation again. This is not a new key and am quite certain I used it for Apache releases in the past. http://gpg-keyserver.de/ appears to be down, at least from where I am right now, http://pgp.mit.edu:11371 times out with http 502. http://pool.sks-keyservers.net:11371 finds the key in question. I am lost at this point. Any help will be appreciated. -- Regards, Igor - 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 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/ http://repository.apache.org/content/repositories/maven-1039/org/apache/maven/plugin-testing/maven-plugin-testing/3.2.0/maven-plugin-testing-3.2.0-source-release.zip Source release checksum(s): maven-plugin-testing-3.2.0-source-release.zip sha1: 53bf150ffb13ba07a76748cbe8103530fd4465d9 Staging site: http://maven.apache.org/plugin-testing-archives/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
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/ http://repository.apache.org/content/repositories/maven-1039/org/apache/maven/plugin-testing/maven-plugin-testing/3.2.0/maven-plugin-testing-3.2.0-source-release.zip Source release checksum(s): maven-plugin-testing-3.2.0-source-release.zip sha1: 53bf150ffb13ba07a76748cbe8103530fd4465d9 Staging site: http://maven.apache.org/plugin-testing-archives/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 Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io - We all have problems. How we deal with them is a measure of our worth. -- Unknown
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 eliminating the effects of unintended artifact sharing via the local repository Regards, Hervé [1] https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility+Notes#Maven3.xCompatibilityNotes-ResolutionfromLocalRepository Le lundi 7 juillet 2014 11:28:18 Igor Fedorenko a écrit : On 2014-07-07, 1:56, Mark Derricutt wrote: That would in part align things with Aether's somewhat annoying/retarded behaviour of saying oh I see com.acme:special tool:1.0-alpha-1 but it came from repo-1, not repo-2 - so suck it up - I can't resolve this.. I can understand the idea behind this - two artefacts from two different repositories _may_ share the same GAV and yet be totally different, but I find that to be so rare that that I probably never want this to not resolve ( that causes lots of annoying issues with using a mirror, and having to temporarily disable said mirror ). I don't think this has much/anything to do with the same GAV coming from different remote URLs. The project does not have access to repo-1 and Maven does not know if repo-2 has the artifact. Without this check project may get access to artifacts that simply happen to be cached locally during some prior build, which I rather strongly believe is a bad thing. -- Regards, Igor I could see this change also breaking under mirrors, or maybe that's just when using mirror:* On 5 Jul 2014, at 4:56, Robert Scholte wrote: To me it would make sense if you could add a reference to the repository per dependency, like dependency groupIdcom.acme/groupId artifactIdspecialtool/artifactId version1.0-alpha-1/version repositoryIdacme-store/repositoryId !-- only look in this repo, I know it's not in Central -- /dependency - 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 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: https://repository.apache.org/content/repositories/maven-1040 http://repository.apache.org/content/repositories/maven-1040/org/apache/maven/plugins/maven-source-plugin/2.3/maven-source-plugin-2.3-source-release.zip Source release checksum(s): maven-source-plugin-2.3-source-release.zip sha1: 351db6ba2fec1e27bf60ed0a5e7683ca3ab925c0 Staging site: http://maven.apache.org/plugins-archives/maven-source-plugin-LATEST/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html 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
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) from me. Kind regards Karl-Heinz Marbaise Staging repo: https://repository.apache.org/content/repositories/maven-1039/ http://repository.apache.org/content/repositories/maven-1039/org/apache/maven/plugin-testing/maven-plugin-testing/3.2.0/maven-plugin-testing-3.2.0-source-release.zip Source release checksum(s): maven-plugin-testing-3.2.0-source-release.zip sha1: 53bf150ffb13ba07a76748cbe8103530fd4465d9 Staging site: http://maven.apache.org/plugin-testing-archives/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
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, 0:18, Karl Heinz Marbaise wrote: 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) from me. Kind regards Karl-Heinz Marbaise Staging repo: https://repository.apache.org/content/repositories/maven-1039/ http://repository.apache.org/content/repositories/maven-1039/org/apache/maven/plugin-testing/maven-plugin-testing/3.2.0/maven-plugin-testing-3.2.0-source-release.zip Source release checksum(s): maven-plugin-testing-3.2.0-source-release.zip sha1: 53bf150ffb13ba07a76748cbe8103530fd4465d9 Staging site: http://maven.apache.org/plugin-testing-archives/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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
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] [ERROR] BUILD FAILURE [INFO] [INFO] Unable to build project '/Users/kama/Downloads/maven-plugin-testing-3.2.0/pom.xml; it requires Maven version 3.1.1 [INFO] This is based on the prerequisites in the pomin Maven 3. prerequisites is not checked anymore. The pom contains: prerequisites maven3.1.1/maven /prerequisites So this means only Maven 3.1.1 should be used to build it. But i can build it with Maven 3.0.5... So checking for a build requirement can only be done via maven-enforcer-plugin correctly at the moment...for Maven 3.X version. http://jira.codehaus.org/browse/MNG-4840 http://jira.codehaus.org/browse/MNG-5297 Kind regards Karl-Heinz 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, 0:18, Karl Heinz Marbaise wrote: 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) from me. Kind regards Karl-Heinz Marbaise Staging repo: https://repository.apache.org/content/repositories/maven-1039/ http://repository.apache.org/content/repositories/maven-1039/org/apache/maven/plugin-testing/maven-plugin-testing/3.2.0/maven-plugin-testing-3.2.0-source-release.zip Source release checksum(s): maven-plugin-testing-3.2.0-source-release.zip sha1: 53bf150ffb13ba07a76748cbe8103530fd4465d9 Staging site: http://maven.apache.org/plugin-testing-archives/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
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 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] [ERROR] BUILD FAILURE [INFO] [INFO] Unable to build project '/Users/kama/Downloads/maven-plugin-testing-3.2.0/pom.xml; it requires Maven version 3.1.1 [INFO] This is based on the prerequisites in the pomin Maven 3. prerequisites is not checked anymore. The pom contains: prerequisites maven3.1.1/maven /prerequisites So this means only Maven 3.1.1 should be used to build it. But i can build it with Maven 3.0.5... So checking for a build requirement can only be done via maven-enforcer-plugin correctly at the moment...for Maven 3.X version. http://jira.codehaus.org/browse/MNG-4840 http://jira.codehaus.org/browse/MNG-5297 Kind regards Karl-Heinz 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, 0:18, Karl Heinz Marbaise wrote: 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) from me. Kind regards Karl-Heinz Marbaise Staging repo: https://repository.apache.org/content/repositories/maven-1039/ http://repository.apache.org/content/repositories/maven-1039/org/apache/maven/plugin-testing/maven-plugin-testing/3.2.0/maven-plugin-testing-3.2.0-source-release.zip Source release checksum(s): maven-plugin-testing-3.2.0-source-release.zip sha1: 53bf150ffb13ba07a76748cbe8103530fd4465d9 Staging site: http://maven.apache.org/plugin-testing-archives/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 Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io - the course of true love never did run smooth ... -- Shakespeare
[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 to do JDK check with 1.6 based on pmd pom.xml You can merge this pull request into a Git repository by running: $ git pull https://github.com/sjonnalagadda/maven-plugins trunk Alternatively you can review and apply these changes as the patch at: https://github.com/apache/maven-plugins/pull/27.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #27 commit b2f7946b927f14d4447537b9d77f89490c220cd9 Author: Sridhar Jonnalagadda sridharjonnalagadda...@air-watch.com Date: 2014-07-08T23:17:16Z Upgarding to use latest PMD to support JDK 1.8 code base --- 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 is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
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 state. Olivier On 4 July 2014 07:52, 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 Marbaise, Mark Struberg 21:00-22:00 (IST) Stephen Connolly The current time for me is 8am Friday - with a 30-40 minute drive to the office before hand ( in order to start work at 9:15ish ). Any earlier would be harsh for me, but better for any .au folk. Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
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 Marbaise, Mark Struberg 21:00-22:00 (IST) Stephen Connolly The current time for me is 8am Friday - with a 30-40 minute drive to the office before hand ( in order to start work at 9:15ish ). Any earlier would be harsh for me, but better for any .au folk. Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
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 For additional commands, e-mail: dev-h...@maven.apache.org
