Re: move maven core to java 7?

+1 I just find the change/discussion a bit too fast. You should wait longer than ~10h as the world has more timezone. IMHO waiting for the answer from various members of the community is more like 2/3 days. Cheers -- Olivier On 6 Mar 2015 10:37, "Jason van Zyl" wrote: > Ok, the consensus is to m

Re: move maven core to java 7?

What I'd like to stress here is that we're talking about Maven core, not our plugins. We've had a separate discussion/thread for the plugins and for those we've decided to go with a Java 6 requirement. As plugins were mentioned in this thread as well I want to make sure there is no misunderstanding

Files.walkFileTree performance vs plexus DirectoryScanner

2015-03-05 21:34 GMT+01:00 Igor Fedorenko : > > On 2015-03-05 14:12, Kristian Rosenvold wrote: > >> Actually Files.walkFileTree is just about the only NIO 7 feature we're >> not using. Anyone have any specific pointers/experience that actually >> show this being faster than the current strategy ?

Re: Anyone know if JDK 1.8.0_40 fixes the delay in returning to the command prompt?

It would appear so. I don't see the hang anymore. On Mar 5, 2015, at 2:22 PM, Stephen Connolly wrote: > I know the delay is not always present with 1.8.0_31, so the fact that I am > not seeing it with 1.8.0_40 in the first 5 builds I try is not sufficient > evidence... but anyone else with evid

Subject: [VOTE] Release Apache Maven Archetype 2.3

Hi, This is a vote to release Archetype 2.3, intended as the last version of Archetype built to support Maven 2.2.x. We solved some issues: Release Notes - Maven Archetype - Version 2.3 ** Bug * [ARCHETYPE-345] - archetype:create-from-project do not process and sections into EAR's pom.xm

Re: Subject: [VOTE] Release Apache Maven Archetype 2.3

+1 binding. On Thu, Mar 5, 2015 at 7:21 PM, Benson Margulies wrote: > Hi, > > This is a vote to release Archetype 2.3, intended as the last version > of Archetype built to support Maven 2.2.x. > > We solved some issues: > > Release Notes - Maven Archetype - Version 2.3 > > > ** Bug > * [ARCHE

Re: move maven core to java 7?

Ok, the consensus is to move forward to Java7. I updated the POM and we're in no rush so give it a whirl and we can think about releasing next week if the world doesn't blow up. On Mar 5, 2015, at 2:32 PM, Mirko Friedenhagen wrote: > Hello there, > > I would go for JDK7 as well, in April it w

Re: move maven core to java 7?

Hello there, I would go for JDK7 as well, in April it will be EOLed anyway. I do not understand why someone who is forced to use JDK6 or let alone JDK5 is allowed (or has) to use the newest versions of build tools BTW. IMO it is stressful enough to support two JDKs (on different at least 3 OSes).

Anyone know if JDK 1.8.0_40 fixes the delay in returning to the command prompt?

I know the delay is not always present with 1.8.0_31, so the fact that I am not seeing it with 1.8.0_40 in the first 5 builds I try is not sufficient evidence... but anyone else with evidence to throw onto the stack?

Re: move maven core to java 7?

My preference is to always go for the lowest common denoninator, as it gives the largest possible spread. My 'grumbling' as Stephen put it [ :-) ], is more that I'd like people to have an awareness that there are other platforms out there. For example, the current IBM WAS 8.x stack defaults to Ja

Re: move maven core to java 7?

Hi, On 3/5/15 2:16 PM, Igor Fedorenko wrote: This is chicken-and-egg situation. We won't use java 7 features unless the code targets java 7. Try-with-resources and multi-exception catch are the too features I'd like to start using throughout the code. Although not "critical" per se, I think the

Suggestions User Information about Maven 2.2.1 EoL / Plugins / JDK

Hi, here is my suggestions for the user list announcement regarding Maven 2.2.1 EoL / Plugins version lift / JDK etc. Any enhancement / things which should also be mentioned please reply and make appropriate changes / Thinks which i have missed... --

Re: move maven core to java 7?

+1 for the upgrade On Thu, Mar 5, 2015 at 7:53 PM, Hervé BOUTEMY wrote: > +1 > (both for the move to java 7, Robert's concerns and Stephen justification) > > another reason: the next Maven core minor version bump isn't expected > before a > while > > let's use the 3.3.0 minor version choice done

Re: move maven core to java 7?

On 2015-03-05 14:12, Kristian Rosenvold wrote: Actually Files.walkFileTree is just about the only NIO 7 feature we're not using. Anyone have any specific pointers/experience that actually show this being faster than the current strategy ? I ran some tests about a year ago on a large 200K files

[GitHub] maven pull request: [MNG-5738] Addition of command line flag '--le...

Github user hboutemy commented on the pull request: https://github.com/apache/maven/pull/32#issuecomment-77440946 yes, it was just fixed in http://jira.codehaus.org/browse/MNG-5779 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub a

[GitHub] maven-plugins pull request: [MPMD-207] Add CPD support for javascr...

GitHub user adangel opened a pull request: https://github.com/apache/maven-plugins/pull/48 [MPMD-207] Add CPD support for javascript and jsp https://jira.codehaus.org/browse/MPMD-207 You can merge this pull request into a Git repository by running: $ git pull https://github.com

[GitHub] maven-plugins pull request: [MPMD-206] Make the source directories...

GitHub user adangel opened a pull request: https://github.com/apache/maven-plugins/pull/47 [MPMD-206] Make the source directories configurable Pull request for: https://jira.codehaus.org/browse/MPMD-206 The parameters are manually set to the defaults value instead of using de

[GitHub] maven pull request: [MNG-5738] Addition of command line flag '--le...

Github user mcculls commented on the pull request: https://github.com/apache/maven/pull/32#issuecomment-77430685 @ChristianSchulte I believe that was recently fixed in master: https://github.com/apache/maven/commit/57a6196422873eaf2f00a282b33894a74dcfd19c --- If your project is set u

Re: move maven core to java 7?

2015-03-05 17:26 GMT+01:00 Robert Scholte : > Op Thu, 05 Mar 2015 14:16:24 +0100 schreef Igor Fedorenko > : > >> Improvements to standard library, nio in particular, is another big >> reason for me. For example, Files#walkFileTree is significantly faster >> than comparable File-based implementation

[GitHub] maven pull request: [MNG-5738] Addition of command line flag '--le...

Github user ChristianSchulte commented on the pull request: https://github.com/apache/maven/pull/32#issuecomment-77428933 I have no experience with the cobertura plugin. I just added ``` org.codehaus.mojo cobertura-maven-plugin 2.7 ``` t

Re: move maven core to java 7?

+1 (both for the move to java 7, Robert's concerns and Stephen justification) another reason: the next Maven core minor version bump isn't expected before a while let's use the 3.3.0 minor version choice done on Maven features be used on this internal JDK choice update too Regards, Hervé Le

Re: Maven 3.2.6

yes, the fix did it: I just closed MNG-5779 (the build failure was during install phase, since checkstyle:check happens there) thank you Hervé Le jeudi 5 mars 2015 08:00:31 Jason van Zyl a écrit : > Did you try it again, worked for me locally now with the last change. > > I just kicked off a 3

Re: move maven core to java 7?

Op Thu, 05 Mar 2015 14:16:24 +0100 schreef Igor Fedorenko : This is chicken-and-egg situation. We won't use java 7 features unless the code targets java 7. Try-with-resources and multi-exception catch are the too features I'd like to start using throughout the code. Although not "critical" pe

Re: move maven core to java 7?

Robert, I think it's reasonable at this point to move to Java 1.7. I'd really prefer to use new features and given Java 1.7 is about to be EOL'd I don't think it's very practical staying on Java 1.6. On Mar 5, 2015, at 8:09 AM, Stephen Connolly wrote: > We never got a final official policy.

Re: move maven core to java 7?

We never got a final official policy. I believe the consensus was at least: * all Java versions currently supported by Oracle and one back on a Major version bump. I think we should go with all Java versions currently supported by Oracle on a Minor version bump... but there was some grumbling fr

Re: Maven 3.2.6

Did you try it again, worked for me locally now with the last change. I just kicked off a 3 hour testing process for the new 3.3.0-SNAPSHOT so I'll be more confident after that works. I'd really like to bump up to Java 1.7 as well before the release. I think it's an appropriate time given the b

Re: move maven core to java 7?

Stephen, as the keeper of long discussions we've had about JDK versions what did we actually decide a while back? On Mar 5, 2015, at 7:43 AM, Stephen Connolly wrote: > +1 > > On 5 March 2015 at 12:19, Igor Fedorenko wrote: > >> With maven core version change to 3.3.0 on master, any objectio

Re: move maven core to java 7?

+1 On 5 March 2015 at 12:19, Igor Fedorenko wrote: > With maven core version change to 3.3.0 on master, any objections I > change compile source/target to java 7? > > -- > Regards, > Igor > > - > To unsubscribe, e-mail: dev-unsu

Re: libs in mavens /lib folder

Ah ok - I'm not familiar with these exports. I'll check tonight - need another computer to do so - but got the issue with tomee-embedded-maven-plugin using javaee-api jar as dependency (which of course contains all javax.*) so if maven provides it as well it can be broken - either the exception i m

Re: move maven core to java 7?

+1 On Mar 5, 2015, at 4:19 AM, Igor Fedorenko wrote: > With maven core version change to 3.3.0 on master, any objections I > change compile source/target to java 7? > > -- > Regards, > Igor > > - > To unsubscribe, e-mail: dev

Re: libs in mavens /lib folder

Not sure I understand - the packages currently exported are limited to the ones that plugins/extensions need to use to communicate with Maven core (such as javax.inject to request injection) Do you have a plugin or testcase which is behaving incorrectly with Maven 3.2.5? On Thursday, 5 March

Re: libs in mavens /lib folder

Hmm, will test soon but seems the imports are not complete, it misses: javax.decorator, javax.inject, javax.annotation and the whole javax.enterprise AFAIK Romain Manni-Bucau @rmannibucau | Blog | Github

Re: libs in mavens /lib folder

I believe that was fixed in https://jira.codehaus.org/browse/MNG-5620 (Maven 3.2.2) - can you recreate it with Maven 3.2.5? On Thursday, 5 March 2015 at 15:06, Romain Manni-Bucau wrote: > no issue for maven itself but plugins are now easily broken: > > loader constraint violation: loader (insta

Re: libs in mavens /lib folder

no issue for maven itself but plugins are now easily broken: loader constraint violation: loader (instance of org/codehaus/plexus/classworlds/realm/ClassRealm) previously initiated loading for a different type with name "javax/enterprise/util/TypeLiteral" Romain Manni-Bucau @rmannibucau

Re: libs in mavens /lib folder

Why are you confused? From 3.1.0 to 3.3.0-SNAPSHOT the distribution, in expanded form, has gone from ~6mb to ~9mb where the biggest contributors to the size are Guava and the Wagon/HTTP related libraries. Those things have just gotten bigger (Guava), or they have more dependencies (Wagon, commo

Re: libs in mavens /lib folder

On Thursday, 5 March 2015 at 14:42, Mark Struberg wrote: > Hi! > > I'm quite confused by the sheer amount of libs we already have in our lib > folder. For maven-3.2.1 this is > > 133957 7. Mai 2013 aether-api-0.9.0.M2.jar > 12637 14. Feb 2014 aether-api.license > 34117 7. Mai 2013 aether-conne

Re: libs in mavens /lib folder

Hi +1, javax.* are quite impacting since they break quite easily (and randomly) all plugins relying on it. Romain Manni-Bucau @rmannibucau | Blog | Github | LinkedIn

libs in mavens /lib folder

Hi! I'm quite confused by the sheer amount of libs we already have in our lib folder. For maven-3.2.1 this is 133957 7. Mai 2013 aether-api-0.9.0.M2.jar 12637 14. Feb 2014 aether-api.license 34117 7. Mai 2013 aether-connector-wagon-0.9.0.M2.jar 12637 14. Feb 2014 aether-connector-wagon.license 1

Re: move maven core to java 7?

This is chicken-and-egg situation. We won't use java 7 features unless the code targets java 7. Try-with-resources and multi-exception catch are the too features I'd like to start using throughout the code. Although not "critical" per se, I think they make writing correct maintainable code notice

Re: move maven core to java 7?

+1 --  Thanks, ~t~ On 5 Mar 2015 at 13:28:25, Anders Hammar (and...@hammar.net) wrote: I think this is what we decided on - support latest and one prior released JDK version. IF we do, we need to update the README file in the distro as well as the system requirements page online. /Ande

Re: move maven core to java 7?

I don't know the numbers, but I think JDK6 is still used a lot by the community. Current code builds fine with JDK6. Which JDK7 specific features do you want to use, which are not possible with the current codebase? Without any critical codechanges I'd go for -1. Robert Op Thu, 05 Mar 2015

Re: move maven core to java 7?

+1 :) K 2015-03-05 13:27 GMT+01:00 Anders Hammar : > I think this is what we decided on - support latest and one prior released > JDK version. > > IF we do, we need to update the README file in the distro as well as the > system requirements page online. > > /Anders > > On Thu, Mar 5, 2015 at 1:

Re: move maven core to java 7?

I think this is what we decided on - support latest and one prior released JDK version. IF we do, we need to update the README file in the distro as well as the system requirements page online. /Anders On Thu, Mar 5, 2015 at 1:19 PM, Igor Fedorenko wrote: > With maven core version change to 3.

move maven core to java 7?

With maven core version change to 3.3.0 on master, any objections I change compile source/target to java 7? -- Regards, Igor - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@ma