Re: [MNG-5551] Java 8 + Maven status
I have updated dependency (maven shade) to use asm 5.0.1, and I hope to get version 0.8 of dependency released RealSoon (tm). Kristian 2014-03-27 21:16 GMT+01:00 Mirko Friedenhagen mfriedenha...@gmail.com: Steven, thanks, I now could reproduce this. Installing a local SNAPSHOT of the shared library and plugin did resolve this. So I guess we have to release both pretty soon :-). Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen) https://bitbucket.org/mfriedenhagen/ On Thu, Mar 27, 2014 at 8:37 PM, Steven Schlansker stevenschlans...@gmail.com wrote: Here is a reproduction case: https://github.com/stevenschlansker/mdep-439-analyze-java8 On Mar 27, 2014, at 10:26 AM, Mirko Friedenhagen mfriedenha...@gmail.com wrote: Steven, I can not reproduce that maven-dependency-plugin:analyze:2.8 fails with JDK8. I have created a small library with a Lambda (call it L) and ran dependency:analyze without probems. I installed this library and made a new component depend on L and ran dependency:analyze successfully again. As stated in MDEP-439[1], can you or someone else provide a sample? Otherwise I will close this bug. [1] http://jira.codehaus.org/browse/MDEP-439 Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen) https://bitbucket.org/mfriedenhagen/ On Thu, Mar 27, 2014 at 1:28 PM, Matt Benson gudnabr...@gmail.com wrote: Oh, good news on the dependency plugin bit--I almost forgot that you had mentioned its underlying library having already upgraded its trunk to version 4. I was thinking more about jdependency, which supports the shade plugin. Matt On Mar 27, 2014 7:22 AM, Matt Benson gudnabr...@gmail.com wrote: Oh, well... It's no secret that ASM 3, being interface-based, is wholly incompatible with ASM 4, which took the approach of using abstract classes to significantly reduce the amount of code needed to accomplish a given task. ASM 5 claims to be compatible with 4, which is why I, not realizing that the plugins in question were based on ASM 3, suggested that simply dropping in the new jar should suffice. The good news is that the upgrade process is not terribly onerous, if only someone steps to do it. Matt On Mar 27, 2014 5:25 AM, Mirko Friedenhagen mfriedenha...@gmail.com wrote: Mark, the analyze goal depends on the org.apache.maven.shared:maven-dependency-analyzer:1.4 which depends on asm 3.3.1. The trunk already moved to 4.2. I will see what happens when switching to asm 5 :-) Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen) https://bitbucket.org/mfriedenhagen/ On Thu, Mar 27, 2014 at 5:45 AM, Mark Derricutt m...@talios.com wrote: What version of the maven-dependency-plugin? I'm using 2.8 fine under JDK8 and have been for some time - this is using the `copy-dependencies` goal and nothing else tho... On 27 Mar 2014, at 6:15, Steven Schlansker wrote: Java 8 has now been out for a week and Maven is still not really compatible. In particular, the maven-shade-plugin and maven-dependency-plugin do not work due to an old version of ASM that throws ArrayIndexOutOfBoundsException on Java 8 class files. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [MNG-5551] Java 8 + Maven status
why didn't we detect the failure when building the plugin and running ITs with JDK 8 = somthing we did a long time ago and that I was conviced would give us more accurate results than what we finally have? I had a quick look at ITs, and it seems that the compiler plugin is configured to generate 1.5 bytecode IMHO, we need to add an IT generating 1.8 bytecode to make tests and show the failure before fixing and being sure the fix is complete. I didn't have time to really test, but I hope such discussion can help us improve JDK8 support more rapidly And find every other place where JDK8 compatibility won't be automatic: looking for asm is one way, but I suppose there may be problems for tools not using asm Regards, Hervé Le vendredi 28 mars 2014 07:40:53 Kristian Rosenvold a écrit : I have updated dependency (maven shade) to use asm 5.0.1, and I hope to get version 0.8 of dependency released RealSoon (tm). Kristian 2014-03-27 21:16 GMT+01:00 Mirko Friedenhagen mfriedenha...@gmail.com: Steven, thanks, I now could reproduce this. Installing a local SNAPSHOT of the shared library and plugin did resolve this. So I guess we have to release both pretty soon :-). Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen) https://bitbucket.org/mfriedenhagen/ On Thu, Mar 27, 2014 at 8:37 PM, Steven Schlansker stevenschlans...@gmail.com wrote: Here is a reproduction case: https://github.com/stevenschlansker/mdep-439-analyze-java8 On Mar 27, 2014, at 10:26 AM, Mirko Friedenhagen mfriedenha...@gmail.com wrote: Steven, I can not reproduce that maven-dependency-plugin:analyze:2.8 fails with JDK8. I have created a small library with a Lambda (call it L) and ran dependency:analyze without probems. I installed this library and made a new component depend on L and ran dependency:analyze successfully again. As stated in MDEP-439[1], can you or someone else provide a sample? Otherwise I will close this bug. [1] http://jira.codehaus.org/browse/MDEP-439 Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen) https://bitbucket.org/mfriedenhagen/ On Thu, Mar 27, 2014 at 1:28 PM, Matt Benson gudnabr...@gmail.com wrote: Oh, good news on the dependency plugin bit--I almost forgot that you had mentioned its underlying library having already upgraded its trunk to version 4. I was thinking more about jdependency, which supports the shade plugin. Matt On Mar 27, 2014 7:22 AM, Matt Benson gudnabr...@gmail.com wrote: Oh, well... It's no secret that ASM 3, being interface-based, is wholly incompatible with ASM 4, which took the approach of using abstract classes to significantly reduce the amount of code needed to accomplish a given task. ASM 5 claims to be compatible with 4, which is why I, not realizing that the plugins in question were based on ASM 3, suggested that simply dropping in the new jar should suffice. The good news is that the upgrade process is not terribly onerous, if only someone steps to do it. Matt On Mar 27, 2014 5:25 AM, Mirko Friedenhagen mfriedenha...@gmail.com wrote: Mark, the analyze goal depends on the org.apache.maven.shared:maven-dependency-analyzer:1.4 which depends on asm 3.3.1. The trunk already moved to 4.2. I will see what happens when switching to asm 5 :-) Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen) https://bitbucket.org/mfriedenhagen/ On Thu, Mar 27, 2014 at 5:45 AM, Mark Derricutt m...@talios.com wrote: What version of the maven-dependency-plugin? I'm using 2.8 fine under JDK8 and have been for some time - this is using the `copy-dependencies` goal and nothing else tho... On 27 Mar 2014, at 6:15, Steven Schlansker wrote: Java 8 has now been out for a week and Maven is still not really compatible. In particular, the maven-shade-plugin and maven-dependency-plugin do not work due to an old version of ASM that throws ArrayIndexOutOfBoundsException on Java 8 class files. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail:
Re: [MNG-5551] Java 8 + Maven status
I have updated quite a few places to asm 4.x compliance (and hence 5.x). Do let me know if I missed something, I can do the rest. (The api changes are fairly significant so I'm assuming I can do further upgrades about twice as fast as someone who hasn't done it...) K 2014-03-28 8:11 GMT+01:00 Hervé BOUTEMY herve.bout...@free.fr: why didn't we detect the failure when building the plugin and running ITs with JDK 8 = somthing we did a long time ago and that I was conviced would give us more accurate results than what we finally have? I had a quick look at ITs, and it seems that the compiler plugin is configured to generate 1.5 bytecode IMHO, we need to add an IT generating 1.8 bytecode to make tests and show the failure before fixing and being sure the fix is complete. I didn't have time to really test, but I hope such discussion can help us improve JDK8 support more rapidly And find every other place where JDK8 compatibility won't be automatic: looking for asm is one way, but I suppose there may be problems for tools not using asm Regards, Hervé Le vendredi 28 mars 2014 07:40:53 Kristian Rosenvold a écrit : I have updated dependency (maven shade) to use asm 5.0.1, and I hope to get version 0.8 of dependency released RealSoon (tm). Kristian 2014-03-27 21:16 GMT+01:00 Mirko Friedenhagen mfriedenha...@gmail.com: Steven, thanks, I now could reproduce this. Installing a local SNAPSHOT of the shared library and plugin did resolve this. So I guess we have to release both pretty soon :-). Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen) https://bitbucket.org/mfriedenhagen/ On Thu, Mar 27, 2014 at 8:37 PM, Steven Schlansker stevenschlans...@gmail.com wrote: Here is a reproduction case: https://github.com/stevenschlansker/mdep-439-analyze-java8 On Mar 27, 2014, at 10:26 AM, Mirko Friedenhagen mfriedenha...@gmail.com wrote: Steven, I can not reproduce that maven-dependency-plugin:analyze:2.8 fails with JDK8. I have created a small library with a Lambda (call it L) and ran dependency:analyze without probems. I installed this library and made a new component depend on L and ran dependency:analyze successfully again. As stated in MDEP-439[1], can you or someone else provide a sample? Otherwise I will close this bug. [1] http://jira.codehaus.org/browse/MDEP-439 Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen ) https://bitbucket.org/mfriedenhagen/ On Thu, Mar 27, 2014 at 1:28 PM, Matt Benson gudnabr...@gmail.com wrote: Oh, good news on the dependency plugin bit--I almost forgot that you had mentioned its underlying library having already upgraded its trunk to version 4. I was thinking more about jdependency, which supports the shade plugin. Matt On Mar 27, 2014 7:22 AM, Matt Benson gudnabr...@gmail.com wrote: Oh, well... It's no secret that ASM 3, being interface-based, is wholly incompatible with ASM 4, which took the approach of using abstract classes to significantly reduce the amount of code needed to accomplish a given task. ASM 5 claims to be compatible with 4, which is why I, not realizing that the plugins in question were based on ASM 3, suggested that simply dropping in the new jar should suffice. The good news is that the upgrade process is not terribly onerous, if only someone steps to do it. Matt On Mar 27, 2014 5:25 AM, Mirko Friedenhagen mfriedenha...@gmail.com wrote: Mark, the analyze goal depends on the org.apache.maven.shared:maven-dependency-analyzer:1.4 which depends on asm 3.3.1. The trunk already moved to 4.2. I will see what happens when switching to asm 5 :-) Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ ( http://osrc.dfm.io/mfriedenhagen) https://bitbucket.org/mfriedenhagen/ On Thu, Mar 27, 2014 at 5:45 AM, Mark Derricutt m...@talios.com wrote: What version of the maven-dependency-plugin? I'm using 2.8 fine under JDK8 and have been for some time - this is using the `copy-dependencies` goal and nothing else tho... On 27 Mar 2014, at 6:15, Steven Schlansker wrote: Java 8 has now been out for a week and Maven is still not really compatible. In particular, the maven-shade-plugin and maven-dependency-plugin do not work due to an old version of ASM that throws ArrayIndexOutOfBoundsException on Java 8 class files.
Jenkins job stability: was Re: [MNG-5551] Java 8 + Maven status
Hello, as a fresh subscriber to notifications I really wonder how often the jobs have failed in the last two weeks. - One reason seems to be, that during staging of plugins and especially shared components the jobs are failing because of staged dependencies are not available in central. I proposed to include all of maven-staging to the settings of Jenkins for IT and shared, but there were some concerns by Karl-Heinz(?) Same goes for the pom staging. - Yesterday maven-dependency-analyzer was not able to compile it's tests, because the TestCase symbol from junit was missing, my guess would be a defect local repository because of concurrent downloads. - All in all right now the jobs do irritate me more than help me. - IMO once a Jenkins job fails oftenly out of the blue it rapidly starts to become useless :-) So I have two proposals: - Include maven-staging in a special settings file included in maven-shared and maven-plugin only to be used in Jenkins. - Configure jobs to use a private repository in the Jenkins workspace and purge it beforehand. What do you think? Regards Mirko -- Sent from my mobile On Mar 28, 2014 8:12 AM, Hervé BOUTEMY herve.bout...@free.fr wrote: why didn't we detect the failure when building the plugin and running ITs with JDK 8 = somthing we did a long time ago and that I was conviced would give us more accurate results than what we finally have? I had a quick look at ITs, and it seems that the compiler plugin is configured to generate 1.5 bytecode IMHO, we need to add an IT generating 1.8 bytecode to make tests and show the failure before fixing and being sure the fix is complete. I didn't have time to really test, but I hope such discussion can help us improve JDK8 support more rapidly And find every other place where JDK8 compatibility won't be automatic: looking for asm is one way, but I suppose there may be problems for tools not using asm Regards, Hervé Le vendredi 28 mars 2014 07:40:53 Kristian Rosenvold a écrit : I have updated dependency (maven shade) to use asm 5.0.1, and I hope to get version 0.8 of dependency released RealSoon (tm). Kristian 2014-03-27 21:16 GMT+01:00 Mirko Friedenhagen mfriedenha...@gmail.com: Steven, thanks, I now could reproduce this. Installing a local SNAPSHOT of the shared library and plugin did resolve this. So I guess we have to release both pretty soon :-). Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen) https://bitbucket.org/mfriedenhagen/ On Thu, Mar 27, 2014 at 8:37 PM, Steven Schlansker stevenschlans...@gmail.com wrote: Here is a reproduction case: https://github.com/stevenschlansker/mdep-439-analyze-java8 On Mar 27, 2014, at 10:26 AM, Mirko Friedenhagen mfriedenha...@gmail.com wrote: Steven, I can not reproduce that maven-dependency-plugin:analyze:2.8 fails with JDK8. I have created a small library with a Lambda (call it L) and ran dependency:analyze without probems. I installed this library and made a new component depend on L and ran dependency:analyze successfully again. As stated in MDEP-439[1], can you or someone else provide a sample? Otherwise I will close this bug. [1] http://jira.codehaus.org/browse/MDEP-439 Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen) https://bitbucket.org/mfriedenhagen/ On Thu, Mar 27, 2014 at 1:28 PM, Matt Benson gudnabr...@gmail.com wrote: Oh, good news on the dependency plugin bit--I almost forgot that you had mentioned its underlying library having already upgraded its trunk to version 4. I was thinking more about jdependency, which supports the shade plugin. Matt On Mar 27, 2014 7:22 AM, Matt Benson gudnabr...@gmail.com wrote: Oh, well... It's no secret that ASM 3, being interface-based, is wholly incompatible with ASM 4, which took the approach of using abstract classes to significantly reduce the amount of code needed to accomplish a given task. ASM 5 claims to be compatible with 4, which is why I, not realizing that the plugins in question were based on ASM 3, suggested that simply dropping in the new jar should suffice. The good news is that the upgrade process is not terribly onerous, if only someone steps to do it. Matt On Mar 27, 2014 5:25 AM, Mirko Friedenhagen mfriedenha...@gmail.com wrote: Mark, the analyze goal depends on the org.apache.maven.shared:maven-dependency-analyzer:1.4 which depends on asm 3.3.1. The trunk already moved to 4.2. I will see what happens when switching to asm 5 :-) Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ ( http://osrc.dfm.io/mfriedenhagen) https://bitbucket.org/mfriedenhagen/ On Thu, Mar
Re: Jenkins job stability: was Re: [MNG-5551] Java 8 + Maven status
Well, the Windows IT build [1] has failed constantly for over a month. :-( /Anders [1] https://builds.apache.org/view/M-R/view/Maven/job/core-it-maven-3-win/ On Fri, Mar 28, 2014 at 12:32 PM, Mirko Friedenhagen mfriedenha...@gmail.com wrote: Hello, as a fresh subscriber to notifications I really wonder how often the jobs have failed in the last two weeks. - One reason seems to be, that during staging of plugins and especially shared components the jobs are failing because of staged dependencies are not available in central. I proposed to include all of maven-staging to the settings of Jenkins for IT and shared, but there were some concerns by Karl-Heinz(?) Same goes for the pom staging. - Yesterday maven-dependency-analyzer was not able to compile it's tests, because the TestCase symbol from junit was missing, my guess would be a defect local repository because of concurrent downloads. - All in all right now the jobs do irritate me more than help me. - IMO once a Jenkins job fails oftenly out of the blue it rapidly starts to become useless :-) So I have two proposals: - Include maven-staging in a special settings file included in maven-shared and maven-plugin only to be used in Jenkins. - Configure jobs to use a private repository in the Jenkins workspace and purge it beforehand. What do you think? Regards Mirko -- Sent from my mobile On Mar 28, 2014 8:12 AM, Hervé BOUTEMY herve.bout...@free.fr wrote: why didn't we detect the failure when building the plugin and running ITs with JDK 8 = somthing we did a long time ago and that I was conviced would give us more accurate results than what we finally have? I had a quick look at ITs, and it seems that the compiler plugin is configured to generate 1.5 bytecode IMHO, we need to add an IT generating 1.8 bytecode to make tests and show the failure before fixing and being sure the fix is complete. I didn't have time to really test, but I hope such discussion can help us improve JDK8 support more rapidly And find every other place where JDK8 compatibility won't be automatic: looking for asm is one way, but I suppose there may be problems for tools not using asm Regards, Hervé Le vendredi 28 mars 2014 07:40:53 Kristian Rosenvold a écrit : I have updated dependency (maven shade) to use asm 5.0.1, and I hope to get version 0.8 of dependency released RealSoon (tm). Kristian 2014-03-27 21:16 GMT+01:00 Mirko Friedenhagen mfriedenha...@gmail.com: Steven, thanks, I now could reproduce this. Installing a local SNAPSHOT of the shared library and plugin did resolve this. So I guess we have to release both pretty soon :-). Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen) https://bitbucket.org/mfriedenhagen/ On Thu, Mar 27, 2014 at 8:37 PM, Steven Schlansker stevenschlans...@gmail.com wrote: Here is a reproduction case: https://github.com/stevenschlansker/mdep-439-analyze-java8 On Mar 27, 2014, at 10:26 AM, Mirko Friedenhagen mfriedenha...@gmail.com wrote: Steven, I can not reproduce that maven-dependency-plugin:analyze:2.8 fails with JDK8. I have created a small library with a Lambda (call it L) and ran dependency:analyze without probems. I installed this library and made a new component depend on L and ran dependency:analyze successfully again. As stated in MDEP-439[1], can you or someone else provide a sample? Otherwise I will close this bug. [1] http://jira.codehaus.org/browse/MDEP-439 Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen ) https://bitbucket.org/mfriedenhagen/ On Thu, Mar 27, 2014 at 1:28 PM, Matt Benson gudnabr...@gmail.com wrote: Oh, good news on the dependency plugin bit--I almost forgot that you had mentioned its underlying library having already upgraded its trunk to version 4. I was thinking more about jdependency, which supports the shade plugin. Matt On Mar 27, 2014 7:22 AM, Matt Benson gudnabr...@gmail.com wrote: Oh, well... It's no secret that ASM 3, being interface-based, is wholly incompatible with ASM 4, which took the approach of using abstract classes to significantly reduce the amount of code needed to accomplish a given task. ASM 5 claims to be compatible with 4, which is why I, not realizing that the plugins in question were based on ASM 3, suggested that simply dropping in the new jar should suffice. The good news is that the upgrade process is not terribly onerous, if only someone steps to do it. Matt On Mar 27, 2014 5:25 AM, Mirko Friedenhagen mfriedenha...@gmail.com wrote: Mark, the analyze goal
Re: [ANN] The Git branch for Maven 3.2.x has unreleased changes that look OK to release
Cool! The pipeline is working! On 26 March 2014 15:02, Apache Jenkins Server jenk...@builds.apache.orgwrote: This is an automated email to notify the Maven developer list that there are unreleased changes in the Maven 3.2.x GIT branch that have passed all the integration tests and are therefore potentially releasable. https://builds.apache.org/job/maven-3.2-release-status This email does not indicate whether the changes should be released, only that there is something that could be released. -Jenkins
Re: Jenkins job stability: was Re: [MNG-5551] Java 8 + Maven status
I would rather get some good pipelining going so that we have a better quality of jobs in the first place, e.g. see the job pipeline I have set up https://builds.apache.org/job/maven-3.2-release-status/ I want to add other tests into this pipeline and once we have a strong template for a good pipeline then we can replicate for other needs (note that the reality is I will transfer the pipeline to the literate job type once I get that out the door as it makes the whole shebang a whole lot easier to setup and visualize... plus it makes branch development nicer too) On 28 March 2014 11:32, Mirko Friedenhagen mfriedenha...@gmail.com wrote: Hello, as a fresh subscriber to notifications I really wonder how often the jobs have failed in the last two weeks. - One reason seems to be, that during staging of plugins and especially shared components the jobs are failing because of staged dependencies are not available in central. I proposed to include all of maven-staging to the settings of Jenkins for IT and shared, but there were some concerns by Karl-Heinz(?) Same goes for the pom staging. - Yesterday maven-dependency-analyzer was not able to compile it's tests, because the TestCase symbol from junit was missing, my guess would be a defect local repository because of concurrent downloads. - All in all right now the jobs do irritate me more than help me. - IMO once a Jenkins job fails oftenly out of the blue it rapidly starts to become useless :-) So I have two proposals: - Include maven-staging in a special settings file included in maven-shared and maven-plugin only to be used in Jenkins. - Configure jobs to use a private repository in the Jenkins workspace and purge it beforehand. What do you think? Regards Mirko -- Sent from my mobile On Mar 28, 2014 8:12 AM, Hervé BOUTEMY herve.bout...@free.fr wrote: why didn't we detect the failure when building the plugin and running ITs with JDK 8 = somthing we did a long time ago and that I was conviced would give us more accurate results than what we finally have? I had a quick look at ITs, and it seems that the compiler plugin is configured to generate 1.5 bytecode IMHO, we need to add an IT generating 1.8 bytecode to make tests and show the failure before fixing and being sure the fix is complete. I didn't have time to really test, but I hope such discussion can help us improve JDK8 support more rapidly And find every other place where JDK8 compatibility won't be automatic: looking for asm is one way, but I suppose there may be problems for tools not using asm Regards, Hervé Le vendredi 28 mars 2014 07:40:53 Kristian Rosenvold a écrit : I have updated dependency (maven shade) to use asm 5.0.1, and I hope to get version 0.8 of dependency released RealSoon (tm). Kristian 2014-03-27 21:16 GMT+01:00 Mirko Friedenhagen mfriedenha...@gmail.com: Steven, thanks, I now could reproduce this. Installing a local SNAPSHOT of the shared library and plugin did resolve this. So I guess we have to release both pretty soon :-). Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen) https://bitbucket.org/mfriedenhagen/ On Thu, Mar 27, 2014 at 8:37 PM, Steven Schlansker stevenschlans...@gmail.com wrote: Here is a reproduction case: https://github.com/stevenschlansker/mdep-439-analyze-java8 On Mar 27, 2014, at 10:26 AM, Mirko Friedenhagen mfriedenha...@gmail.com wrote: Steven, I can not reproduce that maven-dependency-plugin:analyze:2.8 fails with JDK8. I have created a small library with a Lambda (call it L) and ran dependency:analyze without probems. I installed this library and made a new component depend on L and ran dependency:analyze successfully again. As stated in MDEP-439[1], can you or someone else provide a sample? Otherwise I will close this bug. [1] http://jira.codehaus.org/browse/MDEP-439 Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen ) https://bitbucket.org/mfriedenhagen/ On Thu, Mar 27, 2014 at 1:28 PM, Matt Benson gudnabr...@gmail.com wrote: Oh, good news on the dependency plugin bit--I almost forgot that you had mentioned its underlying library having already upgraded its trunk to version 4. I was thinking more about jdependency, which supports the shade plugin. Matt On Mar 27, 2014 7:22 AM, Matt Benson gudnabr...@gmail.com wrote: Oh, well... It's no secret that ASM 3, being interface-based, is wholly incompatible with ASM 4, which took the approach of using abstract classes to significantly reduce the amount of code needed to accomplish a given task. ASM 5 claims to be compatible with 4, which is why I, not
Re: Operating system requirement
The requirements also says: Disk No minimum requirement. Approximately 100MB will be used for your local repository, however this will vary depending on usage ... AFAICT there _is_ a minimum requirement which is needed to store a basic set of plugins. And of course there is the Maven application itself, though that is tiny (under 6Mb for 3.0.5) 100MB is quite a small repository; they can easily grow to 1GB or more. So you think we should change to for example: Approximately 10MB is required for the Maven installation itself. In addition to that, additional disk space will be used for your local Maven repository. The size of your local repository will vary depending on usage but calculate for at least 500MB. Maven 3.2.1 is around 8MB, but Maven 3.0 is around 3.5MB and 2.x is even smaller. Stating approx 10MB will give us some space. My local repo is 1.5GB so I'm guessing an average dev would need at least 500MB. ok? /Anders /Anders [1] http://maven.apache.org/download.cgi#Requirements - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Getting back maven-scm build to green?
Hi, To stay on the track of Mirko's last email, my original PR for SCM-741 [1] seems to make the IT fail in maven-scm CI [2]. After analyzing the failure logs, I've created another PR that should hopefully fix the issue (first PR worked locally, but the issue seems specific to CI env) : https://github.com/apache/maven-scm/pull/11 If someone can have a look, I'll be glad to help if anything else is necessary. Cheers [1] https://github.com/apache/maven-scm/pull/8 [2] https://builds.apache.org/job/maven-scm -- Baptiste
Re: Maven 3.2.1 release notes
Make sure to use the existing URL of http://maven.apache.org/release-notes.html to get to the starting point of this. This URL is found in our distros as well as on the site. /Anders On Tue, Mar 25, 2014 at 5:13 AM, Jason van Zyl ja...@takari.io wrote: If no one else minds I'll convert it all to single markdown document. On Mar 24, 2014, at 7:50 PM, Olivier Lamy ol...@apache.org wrote: sounds good go for that On 25 March 2014 10:13, Jason van Zyl ja...@takari.io wrote: Fat fingers. I meant to say a single curated set of release notes. On Mar 24, 2014, at 3:49 PM, Olivier Lamy ol...@apache.org wrote: so need some work. The release-notes-all.apt.vm expect to parse apt file but the 3.2.1 release notes has been made using markdown. If someone has idea go for it (ATM I don't have enough time for that). Cheers Olivier On 25 March 2014 09:27, Olivier Lamy ol...@apache.org wrote: working on fixing that. As the format has changed (apt - md) the velocity script cannot see it. On 25 March 2014 08:45, Andrew Holland aholl...@a1dutch.co.uk wrote: Hi, Maven 3.2.1 release notes seem to be missing from http://maven.apache.org/release-notes-all.html Regards Andy -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy -- 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 Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io - First, the taking in of scattered particulars under one Idea, so that everyone understands what is being talked about ... Second, the separation of the Idea into parts, by dividing it at the joints, as nature directs, not breaking any limb in half as a bad carver might. -- Plato, Phaedrus (Notes on the Synthesis of Form by C. Alexander) -- 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 Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io - To think is easy. To act is hard. But the hardest thing in the world is to act in accordance with your thinking. -- Johann von Goethe
Re: Operating system requirement
+1, my repo is about 1.3GB so saying 500+ MB or more depending on your usage seems sensible. 2014-03-28 13:09 GMT+01:00 Anders Hammar and...@hammar.net: The requirements also says: Disk No minimum requirement. Approximately 100MB will be used for your local repository, however this will vary depending on usage ... AFAICT there _is_ a minimum requirement which is needed to store a basic set of plugins. And of course there is the Maven application itself, though that is tiny (under 6Mb for 3.0.5) 100MB is quite a small repository; they can easily grow to 1GB or more. So you think we should change to for example: Approximately 10MB is required for the Maven installation itself. In addition to that, additional disk space will be used for your local Maven repository. The size of your local repository will vary depending on usage but calculate for at least 500MB. Maven 3.2.1 is around 8MB, but Maven 3.0 is around 3.5MB and 2.x is even smaller. Stating approx 10MB will give us some space. My local repo is 1.5GB so I'm guessing an average dev would need at least 500MB. ok? /Anders /Anders [1] http://maven.apache.org/download.cgi#Requirements - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
Re: Getting back maven-scm build to green?
I've merged it... though who knows! On 28 March 2014 12:37, Baptiste Mathus bmat...@batmat.net wrote: Hi, To stay on the track of Mirko's last email, my original PR for SCM-741 [1] seems to make the IT fail in maven-scm CI [2]. After analyzing the failure logs, I've created another PR that should hopefully fix the issue (first PR worked locally, but the issue seems specific to CI env) : https://github.com/apache/maven-scm/pull/11 If someone can have a look, I'll be glad to help if anything else is necessary. Cheers [1] https://github.com/apache/maven-scm/pull/8 [2] https://builds.apache.org/job/maven-scm -- Baptiste
Re: Jenkins job stability: was Re: [MNG-5551] Java 8 + Maven status
Hello Stephen, I am a big fan of pipelines here: 1. clean test-compile 2. clean verify of modules with changes or excluding failsafe/invoker 3. clean verify of all modules with inclusion of invoker tests. Regards Mirko -- Sent from my mobile On Mar 28, 2014 1:02 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: I would rather get some good pipelining going so that we have a better quality of jobs in the first place, e.g. see the job pipeline I have set up https://builds.apache.org/job/maven-3.2-release-status/ I want to add other tests into this pipeline and once we have a strong template for a good pipeline then we can replicate for other needs (note that the reality is I will transfer the pipeline to the literate job type once I get that out the door as it makes the whole shebang a whole lot easier to setup and visualize... plus it makes branch development nicer too) On 28 March 2014 11:32, Mirko Friedenhagen mfriedenha...@gmail.com wrote: Hello, as a fresh subscriber to notifications I really wonder how often the jobs have failed in the last two weeks. - One reason seems to be, that during staging of plugins and especially shared components the jobs are failing because of staged dependencies are not available in central. I proposed to include all of maven-staging to the settings of Jenkins for IT and shared, but there were some concerns by Karl-Heinz(?) Same goes for the pom staging. - Yesterday maven-dependency-analyzer was not able to compile it's tests, because the TestCase symbol from junit was missing, my guess would be a defect local repository because of concurrent downloads. - All in all right now the jobs do irritate me more than help me. - IMO once a Jenkins job fails oftenly out of the blue it rapidly starts to become useless :-) So I have two proposals: - Include maven-staging in a special settings file included in maven-shared and maven-plugin only to be used in Jenkins. - Configure jobs to use a private repository in the Jenkins workspace and purge it beforehand. What do you think? Regards Mirko -- Sent from my mobile On Mar 28, 2014 8:12 AM, Hervé BOUTEMY herve.bout...@free.fr wrote: why didn't we detect the failure when building the plugin and running ITs with JDK 8 = somthing we did a long time ago and that I was conviced would give us more accurate results than what we finally have? I had a quick look at ITs, and it seems that the compiler plugin is configured to generate 1.5 bytecode IMHO, we need to add an IT generating 1.8 bytecode to make tests and show the failure before fixing and being sure the fix is complete. I didn't have time to really test, but I hope such discussion can help us improve JDK8 support more rapidly And find every other place where JDK8 compatibility won't be automatic: looking for asm is one way, but I suppose there may be problems for tools not using asm Regards, Hervé Le vendredi 28 mars 2014 07:40:53 Kristian Rosenvold a écrit : I have updated dependency (maven shade) to use asm 5.0.1, and I hope to get version 0.8 of dependency released RealSoon (tm). Kristian 2014-03-27 21:16 GMT+01:00 Mirko Friedenhagen mfriedenha...@gmail.com : Steven, thanks, I now could reproduce this. Installing a local SNAPSHOT of the shared library and plugin did resolve this. So I guess we have to release both pretty soon :-). Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen) https://bitbucket.org/mfriedenhagen/ On Thu, Mar 27, 2014 at 8:37 PM, Steven Schlansker stevenschlans...@gmail.com wrote: Here is a reproduction case: https://github.com/stevenschlansker/mdep-439-analyze-java8 On Mar 27, 2014, at 10:26 AM, Mirko Friedenhagen mfriedenha...@gmail.com wrote: Steven, I can not reproduce that maven-dependency-plugin:analyze:2.8 fails with JDK8. I have created a small library with a Lambda (call it L) and ran dependency:analyze without probems. I installed this library and made a new component depend on L and ran dependency:analyze successfully again. As stated in MDEP-439[1], can you or someone else provide a sample? Otherwise I will close this bug. [1] http://jira.codehaus.org/browse/MDEP-439 Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ ( http://osrc.dfm.io/mfriedenhagen ) https://bitbucket.org/mfriedenhagen/ On Thu, Mar 27, 2014 at 1:28 PM, Matt Benson gudnabr...@gmail.com wrote: Oh, good news on the dependency plugin bit--I almost forgot that you had mentioned its underlying library having already upgraded its trunk to version 4. I was thinking more about
[GitHub] maven-scm pull request: Remove server block.
Github user asfgit closed the pull request at: https://github.com/apache/maven-scm/pull/11 --- 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: Operating system requirement
On 28 March 2014 12:09, Anders Hammar and...@hammar.net wrote: The requirements also says: Disk No minimum requirement. Approximately 100MB will be used for your local repository, however this will vary depending on usage ... AFAICT there _is_ a minimum requirement which is needed to store a basic set of plugins. And of course there is the Maven application itself, though that is tiny (under 6Mb for 3.0.5) 100MB is quite a small repository; they can easily grow to 1GB or more. So you think we should change to for example: Approximately 10MB is required for the Maven installation itself. In addition to that, additional disk space will be used for your local Maven repository. The size of your local repository will vary depending on usage but calculate for at least 500MB. Maven 3.2.1 is around 8MB, but Maven 3.0 is around 3.5MB and 2.x is even smaller. Stating approx 10MB will give us some space. My local repo is 1.5GB so I'm guessing an average dev would need at least 500MB. ok? +1 /Anders /Anders [1] http://maven.apache.org/download.cgi#Requirements - 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: Getting back maven-scm build to green?
I thought you had to install a Jenkins plugin to get a green build ;-) Regards Mirko -- Sent from my mobile On Mar 28, 2014 2:38 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: I've merged it... though who knows! On 28 March 2014 12:37, Baptiste Mathus bmat...@batmat.net wrote: Hi, To stay on the track of Mirko's last email, my original PR for SCM-741 [1] seems to make the IT fail in maven-scm CI [2]. After analyzing the failure logs, I've created another PR that should hopefully fix the issue (first PR worked locally, but the issue seems specific to CI env) : https://github.com/apache/maven-scm/pull/11 If someone can have a look, I'll be glad to help if anything else is necessary. Cheers [1] https://github.com/apache/maven-scm/pull/8 [2] https://builds.apache.org/job/maven-scm -- Baptiste
