[mojo-dev] [jira] (MFINDBUGS-208) Command-line output does not give specific line number

Title: Message Title Garvin LeClaire commented on an issue

[mojo-dev] [jira] (MFINDBUGS-206) More helpful bug summary in output

Title: Message Title Garvin LeClaire commented on an issue

[mojo-dev] [jira] (MOJO-2064) Use CodeNarc 0.22 per default

Title: Message Title Garvin LeClaire commented on an issue

[mojo-dev] [jira] (MOJO-2064) Use CodeNarc 0.22 per default

Title: Message Title Garvin LeClaire closed an issue as Fixed

[mojo-dev] [jira] (MOJO-2065) "mvn clean install" fails

Title: Message Title Garvin LeClaire updated an issue

[mojo-dev] [jira] (MOJO-2065) "mvn clean install" fails

Title: Message Title Garvin LeClaire updated an issue

[mojo-dev] [jira] (MOJO-2063) fix MojoFailureException message for maxPriority2Violations exceeded

Title: Message Title Garvin LeClaire updated an issue

[mojo-dev] [jira] (MOJO-2062) fix typos in Javadoc

Title: Message Title Garvin LeClaire updated an issue

[mojo-dev] [jira] (MOJO-2065) "mvn clean install" fails

Title: Message Title Garvin LeClaire closed an issue as Fixed

[mojo-dev] [jira] (MOJO-2063) fix MojoFailureException message for maxPriority2Violations exceeded

Title: Message Title Garvin LeClaire closed an issue as Fixed

[mojo-dev] [jira] (MOJO-2062) fix typos in Javadoc

Title: Message Title Garvin LeClaire closed an issue as Fixed

[mojo-dev] [jira] (MOJO-2066) JVM used to run Tidy Maven Plugin must now be Java 1.6 or newer

Title: Message Title Stefan Birkner closed an issue as Fixed

[mojo-dev] [jira] (MOJO-2066) JVM used to run Tidy Maven Plugin must now be Java 1.6 or newer

Title: Message Title Stefan Birkner commented on an issue

Re: [mojo-dev] Maven 3 as a minimum for a major plugin upgrade?

I'm fine with that. A generic discussion around this for Mojo would be good, like we did over att Apache Maven. And then update the dev guidelines. /Anders On Wed, Feb 4, 2015 at 9:59 AM, Sergei Ivanov wrote: > Hi Lennart, > > Yes to all three from me: it is time to move on and ditch the legacy

Re: [mojo-dev] Class 'java.util.List' cannot be instantiated...

Hi Lennart, I believe using String[] instead might do the trick. Or if the problem only manifests itself under maven2, then it would make more sense to discontinue support for maven2 instead of wasting resources on legacy platform. Kind regards, -- Sergei > >Wednesday, 4 February 2015 07:59 +

Re: [mojo-dev] Maven 3 as a minimum for a major plugin upgrade?

Hi Lennart, Yes to all three from me: it is time to move on and ditch the legacy. Kind regards, -- Sergei > >Wednesday, 4 February 2015 08:35 + from Lennart Jörelid >: >Hello all, >Since I'm in the process of performing a major upgrade to the jaxb2 plugin, >I'm contemplating setting maven

Re: [mojo-dev] Maven 3 as a minimum for a major plugin upgrade?

I have no objection moving forward to maven 3 as minimum requirement. -D On Wed, Feb 4, 2015 at 12:35 AM, Lennart Jörelid wrote: > Hello all, > > Since I'm in the process of performing a major upgrade to the jaxb2 > plugin, I'm contemplating setting maven 3 as a minimum for using the > plugin

[mojo-dev] Maven 3 as a minimum for a major plugin upgrade?

Hello all, Since I'm in the process of performing a major upgrade to the jaxb2 plugin, I'm contemplating setting maven 3 as a minimum for using the plugin. This implies 3 things, I think: 1. Remove the Maven 2.2/JDK 1.6 platform for the plugin ITs 2. Set a maven prerequisite of 3.0 3. D

[mojo-dev] Class 'java.util.List' cannot be instantiated...

After a few hiccups, all ITs for Maven3 now execute well on the jaxb2-maven-plugin. However, one of the ITs is run by Maven2 on JDK 1.6, and the integration tests there expose the exception shown in the snippet below. I would suspect that the error is created by parameters like the two below: @Pa