[GitHub] maven-indexer pull request: Update to lucene 4.6 with new API
Github user everflux 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
Re: [VOTE] Release ASF Parent POM version 14
On Fri, 7 Mar 2014 18:15:51 +1100 Olivier Lamy ol...@apache.org wrote: +1 Do we have still to stay on java 1.4 in the compiler configuration ? I don't want to start a new war BTW... Just asking. thanks, tony. +1 -- Olivier On Mar 7, 2014 8:19 AM, Hervé BOUTEMY herve.bout...@free.fr wrote: Hi, Changes since the last release: http://svn.apache.org/viewvc/maven/pom/tags/apache-14/pom.xml?r1=HEADr2=1434717diff_format=h Staging repo: https://repository.apache.org/content/repositories/orgapacheapache-1000/ https://repository.apache.org/content/repositories/orgapacheapache-1000/org/apache/apache/14/apache-14-source-release.zip Source release checksum: apache-14-source-release.zip sha1: 6bed0856a4cc8d9ee5f4481b8a1e0a4460076073 Staging site: http://maven.apache.org/pom-archives/asf-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 -- Tony Chemit tél: +33 (0) 2 40 50 29 28 http://www.codelutin.com email: che...@codelutin.com twitter: https://twitter.com/tchemit - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release ASF Parent POM version 14
Same remark as before. I'd suggest that we change that for the top _maven_ pom. On Fri, Mar 7, 2014 at 6:31 AM, Tony Chemit che...@codelutin.com wrote: On Fri, 7 Mar 2014 18:15:51 +1100 Olivier Lamy ol...@apache.org wrote: +1 Do we have still to stay on java 1.4 in the compiler configuration ? I don't want to start a new war BTW... Just asking. thanks, tony. +1 -- Olivier On Mar 7, 2014 8:19 AM, Hervé BOUTEMY herve.bout...@free.fr wrote: Hi, Changes since the last release: http://svn.apache.org/viewvc/maven/pom/tags/apache-14/pom.xml?r1=HEADr2=1434717diff_format=h Staging repo: https://repository.apache.org/content/repositories/orgapacheapache-1000/ https://repository.apache.org/content/repositories/orgapacheapache-1000/org/apache/apache/14/apache-14-source-release.zip Source release checksum: apache-14-source-release.zip sha1: 6bed0856a4cc8d9ee5f4481b8a1e0a4460076073 Staging site: http://maven.apache.org/pom-archives/asf-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 -- Tony Chemit tél: +33 (0) 2 40 50 29 28 http://www.codelutin.com email: che...@codelutin.com twitter: https://twitter.com/tchemit - 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 ASF Parent POM version 14
+1 from me. Kind regards Karl-Heinz Marbaise Hi, Changes since the last release: http://svn.apache.org/viewvc/maven/pom/tags/apache-14/pom.xml?r1=HEADr2=1434717diff_format=h Staging repo: https://repository.apache.org/content/repositories/orgapacheapache-1000/ https://repository.apache.org/content/repositories/orgapacheapache-1000/org/apache/apache/14/apache-14-source-release.zip Source release checksum: apache-14-source-release.zip sha1: 6bed0856a4cc8d9ee5f4481b8a1e0a4460076073 Staging site: http://maven.apache.org/pom-archives/asf-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 Mit freundlichem Gruß Karl-Heinz Marbaise -- SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893 Dipl.Ing.(FH) Karl-Heinz MarbaiseICQ#: 135949029 Hauptstrasse 177 USt.IdNr: DE191347579 52146 Würselen http://www.soebes.de - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Filtering version 1.2
+1 from me... Source release checksum(s): maven-filtering-1.2-source-release.zip sha1: 50185091c5be24ee3a01296224d9d4eee77852c9 Checked with the downloaded source and the file in staging repo and they are the same... Unpacked source code package and tested mvn clean verify with the following Maven versions: Maven 2.0.11 Maven 3.0.5 Maven 3.1.1 Maven 3.2.1 +1... Staging site: http://maven.apache.org/shared-archives/maven-filtering-LATEST/ Looks good. I make a little supplemental. I would suggest that we add more examples how to use the component and in particular the new filename filtering ...(or do i missed a thing on the site?). 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 Filtering version 1.2
Indeed, that should be documented on the site. It wasn't part of the patch, I just forgot to expand the usage page. thanks, Robert Op Fri, 07 Mar 2014 18:43:14 +0100 schreef Karl Heinz Marbaise khmarba...@gmx.de: +1 from me... Source release checksum(s): maven-filtering-1.2-source-release.zip sha1: 50185091c5be24ee3a01296224d9d4eee77852c9 Checked with the downloaded source and the file in staging repo and they are the same... Unpacked source code package and tested mvn clean verify with the following Maven versions: Maven 2.0.11 Maven 3.0.5 Maven 3.1.1 Maven 3.2.1 +1... Staging site: http://maven.apache.org/shared-archives/maven-filtering-LATEST/ Looks good. I make a little supplemental. I would suggest that we add more examples how to use the component and in particular the new filename filtering ...(or do i missed a thing on the site?). 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
Re: [VOTE] Release Apache Maven Filtering version 1.2
On 3/7/14 7:59 PM, Robert Scholte wrote: Indeed, that should be documented on the site. It wasn't part of the patch, I just forgot to expand the usage page. No Problem. I would suggest to create a issue for that so it wouldn't be forgotten... Kind regards Karl-Heinz thanks, Robert Op Fri, 07 Mar 2014 18:43:14 +0100 schreef Karl Heinz Marbaise khmarba...@gmx.de: +1 from me... Source release checksum(s): maven-filtering-1.2-source-release.zip sha1: 50185091c5be24ee3a01296224d9d4eee77852c9 Checked with the downloaded source and the file in staging repo and they are the same... Unpacked source code package and tested mvn clean verify with the following Maven versions: Maven 2.0.11 Maven 3.0.5 Maven 3.1.1 Maven 3.2.1 +1... Staging site: http://maven.apache.org/shared-archives/maven-filtering-LATEST/ Looks good. I make a little supplemental. I would suggest that we add more examples how to use the component and in particular the new filename filtering ...(or do i missed a thing on the site?). 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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
maven-assembly-plugin / Maven default folder layout
Hi, I stumbled over a small thing. The page about the default folder layout https://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html mentioned a location for the maven-assembly-plugin descriptors: src/main/assembly/ So the location is a suggestion to locate assembly descriptors but the maven-assembly-plugin itself does not have such a default value for that ? In my opinion the maven-assembly-plugin should have a default location as mentioned above (descriptors default value to search for src/main/assembly/ descriptors) or we should change the above description.. What do you thing ? Ideas ? 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: maven-assembly-plugin / Maven default folder layout
Hi, This is the standard (preferred) directory layout, so it doesn't have to be the default. I actually think that src/main/assembly/ should be src/assembly/, otherwise it would imply that there can also be a src/test/assembly/. I wouldn't separate the descriptors into different folders. Robert Op Fri, 07 Mar 2014 20:14:48 +0100 schreef Karl Heinz Marbaise khmarba...@gmx.de: Hi, I stumbled over a small thing. The page about the default folder layout https://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html mentioned a location for the maven-assembly-plugin descriptors: src/main/assembly/ So the location is a suggestion to locate assembly descriptors but the maven-assembly-plugin itself does not have such a default value for that ? In my opinion the maven-assembly-plugin should have a default location as mentioned above (descriptors default value to search for src/main/assembly/ descriptors) or we should change the above description.. What do you thing ? Ideas ? 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
Re: maven-assembly-plugin / Maven default folder layout
Am 2014-03-07 20:25, schrieb Robert Scholte: Hi, This is the standard (preferred) directory layout, so it doesn't have to be the default. I actually think that src/main/assembly/ should be src/assembly/, otherwise it would imply that there can also be a src/test/assembly/. I wouldn't separate the descriptors into different folders. +1 That's the first thing which came to my mind too. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: maven-assembly-plugin / Maven default folder layout
Am 2014-03-07 20:25, schrieb Robert Scholte: Hi, This is the standard (preferred) directory layout, so it doesn't have to be the default. I actually think that src/main/assembly/ should be src/assembly/, otherwise it would imply that there can also be a src/test/assembly/. I wouldn't separate the descriptors into different folders. +1 That's the first thing which came to my mind too. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: maven-assembly-plugin / Maven default folder layout
+1 Regards, Hervé Le vendredi 7 mars 2014 20:25:04 Robert Scholte a écrit : Hi, This is the standard (preferred) directory layout, so it doesn't have to be the default. I actually think that src/main/assembly/ should be src/assembly/, otherwise it would imply that there can also be a src/test/assembly/. I wouldn't separate the descriptors into different folders. Robert Op Fri, 07 Mar 2014 20:14:48 +0100 schreef Karl Heinz Marbaise khmarba...@gmx.de: Hi, I stumbled over a small thing. The page about the default folder layout https://maven.apache.org/guides/introduction/introduction-to-the-standard- directory-layout.html mentioned a location for the maven-assembly-plugin descriptors: src/main/assembly/ So the location is a suggestion to locate assembly descriptors but the maven-assembly-plugin itself does not have such a default value for that ? In my opinion the maven-assembly-plugin should have a default location as mentioned above (descriptors default value to search for src/main/assembly/ descriptors) or we should change the above description.. What do you thing ? Ideas ? 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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: IT failures
I just finished checking generated plugin.xml: apart from ordering of goals, there are only updates of default values as expected, and sometimes addition of empty description so I'm completely confident now and I found that maven-it-plugin-dependency-collection has annotations, but it has a plugin.xml hard-coded too, so the annotations are not used. I supposed this was required because there was a missing annotation, that is now available: I'll update the IT and check that plugin.xml can now be normally generated Regards, Hervé Le mardi 11 février 2014 01:07:46 Hervé BOUTEMY a écrit : I understand the value of core ITs and fear about such changes I both think such a change has a value to keep existing ITs written a long time ago easier for newcomers to understand But yes, I see my update wasn't careful enough In the next days, I'll check that generated plugin.xml is exactly the same before and after the change, and report If I can't get precise comparison (or of course get some diffs), I'll revert my commit, since stability is the major concern Please let me a few days, and eventually ping me back if I don't report Regards, Hervé Le dimanche 9 février 2014 21:21:38 Jason van Zyl a écrit : On Feb 9, 2014, at 2:45 PM, Hervé BOUTEMY herve.bout...@free.fr wrote: I ran the ITs before comitting, it was ok I'm running them once again on my machine, to check if something is now failing ITs need maintenance like every piece of code, old expression field of plugin-tools is now part of past and is every day harder to understand For external, consumer facing projects I would agree. But the purpose of the ITs is stability and multiple points of variation doesn't help with this. The ITs should remain immutable or they can cause issues like we see today where an IT working against released versions functions correctly for years and then all of a sudden doesn't work. If you want to use new versions of tools for newer ITs, I think having a diversity of versions is fine in the ITs but when an IT is created it should remain the way it is when it's created. I don't agree with this change and I think it potentially destabilizes the most valuable resource we have for testing stability, but if you don't see this as an issue then I leave it to you to decide. Regards, Hervé Le dimanche 9 février 2014 14:05:20 Jason van Zyl a écrit : Hervé, The following IT fails after your changes: Tests run: 732, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 450.697 sec FAILURE! testit0064(org.apache.maven.it.MavenIT0064MojoConfigViaSettersTest) Time elapsed: 0.547 sec FAILURE! junit.framework.AssertionFailedError: Expected file was not found: /Users/jvanzyl/js/tesla/maven-integration-testing/core-it-suite/target/ te st -classes/it0064/target/fooValue at junit.framework.Assert.fail(Assert.java:47) at org.apache.maven.it.Verifier.assertFilePresent(Verifier.java:1014) at org.apache.maven.it.MavenIT0064MojoConfigViaSettersTest.testit0064(Mave nI T0 064MojoConfigViaSettersTest.java:51) Do you get the same? Why did you change so many plugins in the ITs? They are supposed the be a (mostly) immutable set of tests and not a body of code that should be updated just because there are new versions. They should remain constant over time, which they have been up until now. I don't think it's particularly useful and when we get a failure like this now it's really hard to tell, with multiple points of variation, whether it's a change in Maven itself or a change in the ITs 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 - 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 - To do two things at once is to do neither. -- Publilius Syrus, Roman slave, first century B.C. - 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:
