Re: What do if project.build.sourceEncoding is not provided?

Isn't this handled by the content-type headers normally ? Kristian 2014-11-13 23:15 GMT+01:00 Michael Osipov : > Hi folks, > > I'd like to know if we have a general concensus on this: > > I am investigating MPIR-242 and figured out the cause. The input stream is > obtained from the HTTP URL and

Re: Maven shared build failing ?

Yeah. But in this case the project itself builds fine with JDK1.5, and the problem appears to be within jenkins itself. Or maybe jenkins stopped supporting 1.5 like we should do too :) Kristian 2014-11-13 22:02 GMT+01:00 Greg Trasuk : > > That error usually means that you’re running under an old

What do if project.build.sourceEncoding is not provided?

Hi folks, I'd like to know if we have a general concensus on this: I am investigating MPIR-242 and figured out the cause. The input stream is obtained from the HTTP URL and no encoding is given, so ISO-8859-1 is provided as default (yuck!). While I know that some reporting related modules hav

Re: MPMD-192: Just skip the IT with Maven 2.2.1

Hi Mirko, sounds good to me.. Go for it... On 11/13/14 10:01 PM, Mirko Friedenhagen wrote: Hello everybody. I am really out of ideas here. MPMD-89 is a test to ensure that test classes whose name *does not* end on Test are recognized as tests by inspecting their inheritage. I do not think th

Re: MPMD-192: Just skip the IT with Maven 2.2.1

Am 2014-11-13 um 22:01 schrieb Mirko Friedenhagen: Hello everybody. I am really out of ideas here. MPMD-89 is a test to ensure that test classes whose name *does not* end on Test are recognized as tests by inspecting their inheritage. I do not think that this is a a major use case. Succeeds with

Re: Maven shared build failing ?

That error usually means that you’re running under an older JVM. One of the jar files has a class version number that is higher than the running JVM knows about. e.g. compiled under JDK8, running under JDK6 or something like that. If you have access to the Jenkins build configuration, have a

MPMD-192: Just skip the IT with Maven 2.2.1

Hello everybody. I am really out of ideas here. MPMD-89 is a test to ensure that test classes whose name *does not* end on Test are recognized as tests by inspecting their inheritage. I do not think that this is a a major use case. Succeeds with Maven >= 3, but fails with Maven 2.2.1. I have spent

Maven shared build failing ?

Life with jenkins is interesting as always; this one is new to me https://builds.apache.org/job/maven-shared/ Kristian - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apa

[RESULT][VOTE] Release maven-repository-builder 1.0

Hi, The vote has passed with the following result: +1 (binding): Karl, Hervé, Kristian I will promote the artifacts to the central repo and try not to further botch the site. Kristian - To unsubscribe, e-mail: dev-unsubscr...@

Re: [VOTE] Release Apache Maven Toolchains Plugin version 1.1

Hi, check sha1, Ok. Checked with Maven 2.2.1, 3.0.5, 3.1.1, 3.2.1, 3.2.2, 3.2.3 no issues found. So +1 from me. Kind regards Karl Heinz Marbaise On 11/11/14 11:26 PM, Hervé BOUTEMY wrote: Hi, We solved 8 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=12063&styleName=Html

Re: [VOTE] Release Apache Maven Toolchains Plugin version 1.1

+1 Op Tue, 11 Nov 2014 23:26:45 +0100 schreef Hervé BOUTEMY : Hi, We solved 8 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=12063&styleName=Html&version=15920 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=tru

[VOTE] Release ASF Parent POM 16, Maven Parent POM 26, Maven Plugins Parent POM 27

Hi, We solved 1/4/1 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250&version=12328739 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250&version=12328928 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250&version=12328

Re: [VOTE] Release maven-repository-builder 1.0

+1 from me too :) Thanks for publishing the Site properly, Hervé ! Kristian 2014-11-12 0:12 GMT+01:00 Hervé BOUTEMY : > +1 > > I published the site, which was apparently built without -Preporting > > A better index page would be useful, or at least better description > > Regards, > > Hervé > > L

Re: Help needed with MPIR-279

Am 2014-11-13 um 12:07 schrieb Stuart McCulloch: On Thursday, 13 November 2014 at 09:43, Michael Osipov wrote: Am 2014-11-13 um 01:40 schrieb Hervé BOUTEMY: Sorry, I tried but I'm stuck with maven-plugin-testing-harness too... I have committed another changed where I have missed to assigned

Re: Help needed with MPIR-279

On Thursday, 13 November 2014 at 09:43, Michael Osipov wrote: > Am 2014-11-13 um 01:40 schrieb Hervé BOUTEMY: > > Sorry, I tried but I'm stuck with maven-plugin-testing-harness too... > > > I have committed another changed where I have missed to assigned the > localRepository. Though it gives

Re: Help needed with MPIR-279

Am 2014-11-13 um 01:40 schrieb Hervé BOUTEMY: Sorry, I tried but I'm stuck with maven-plugin-testing-harness too... I have committed another changed where I have missed to assigned the localRepository. Though it gives me now: testReport(org.apache.maven.report.projectinfo.ModulesReportTest)