Re: Maven 4.0.0

EventSpies are not useless, I use them in netbeans extensively. I inject them using maven.ext.class.path property Milos On Thu, Jan 23, 2014 at 3:57 AM, Jason van Zyl wrote: > I know there is the roadmap page > (https://cwiki.apache.org/confluence/display/MAVEN/Roadmap), but I started a > Mav

Re: Adding a classpath element within a Mojo

Igor, I'm having some difficulty getting the LifecycleParticipant to resolve Maven components. In particular, the org.apache.maven.project.ProjectDependenciesResolver. While it gets resolved, none of it's internal attributes get resolved. So calls to projectDependenciesResolver.resolve crash with

Maven 4.0.0

I know there is the roadmap page (https://cwiki.apache.org/confluence/display/MAVEN/Roadmap), but I started a Maven 4.0.0 page with some general notes and I just want to hook in the JIRA macro to pull in all the 4.0.0 issues at the bottom, but I have figured that out yet. I just want to be able

Re: JIRA Cleanup

I changed the strategy slightly as I thought it might be crappy if the issue was created 5 years ago, but the person updated it 2 months ago. So I took all the issues that have not been updated in the last year and unassigned and closed those out. Got to about the same number and thought this mo

Re: JIRA Cleanup

Yup, it's very straight forward to add a comment to each of the issues that will be closed. When I publish the accompanying documentation I can point the comment at the documentation. Good call. On Jan 22, 2014, at 12:16 PM, Jason van Zyl wrote: > Sure, good idea. I assume there's a relatively

Re: JIRA Cleanup

Sure, good idea. I assume there's a relatively straight forward way to do that with a bulk operation. On Jan 22, 2014, at 12:09 PM, Paul Benedict wrote: > I advise that we add a comment in each closing issue explaining that it was > closed specifically because it's more than 2 years old and to

Re: JIRA Cleanup

I advise that we add a comment in each closing issue explaining that it was closed specifically because it's more than 2 years old and to re-open it only if it is still valid. Otherwise, it will look very rude to close a ticket without an explanation. BTW, what I just recommended was done by JBoss

Re: JIRA Cleanup

Ok, I'm going to pull the ripcord tonight (8 hours from now). On Jan 21, 2014, at 9:19 PM, Jason van Zyl wrote: > So after looking at the issues more closely even at the 5 year-old mark there > are still too many. At the 2 year-old mark it's a bit more reasonable. If I > close all issues older

Re: JDK 8 Build 124 & JDK 7 Update 60 build 03 are available on java.net

On 22/01/2014 12:26, Kristian Rosenvold wrote: Thanks, we saw that already. Preliminary checks seem to indicate things are much better ! Glad to hear that. I'll be running through our tests on windows, linux and OSX to see if there's anything else interesting to be found, I'll post a summary

Re: JDK 8 Build 124 & JDK 7 Update 60 build 03 are available on java.net

Thanks, we saw that already. Preliminary checks seem to indicate things are much better ! I'll be running through our tests on windows, linux and OSX to see if there's anything else interesting to be found, I'll post a summary in couple of days time. Kristian 2014/1/22 Rory O'Donnell Oracle,

JDK 8 Build 124 & JDK 7 Update 60 build 03 are available on java.net

Hi Robert,Kristian, JDK 8 Build b124 Early Access Build is now available for download & test. JDK 7u60 b03 Early Access Build is also available for download & test. A fix for JDK-8030781 is included in b124. Please log