infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gavin (JIRA)" <>
Subject [jira] [Commented] (INFRA-14280) Jenkinsbuildfailure due to unparseable pom-file
Date Sun, 04 Jun 2017 23:15:04 GMT


Gavin commented on INFRA-14280:

[~hugo.hirsch] I see you are not subscribed to the builds@ mailing list - this list (for the
last 8 years) is where we talk about jenkins,buildbot etc. As the bug is relevent for builds
folks only, its not something I would post to all committers etc but rather the builds@ list
where we know everyone subscribed is interested in such stuff.

As it happens the heads up was given by someone else posting to that list, but has since been
discussed and a solution is being prepped and we are ready this end to apply.

I encourage you to sign up to buidls@ - I have emailed projects many times in the past with
this advice for those using jenkins,buildbot.

> Jenkinsbuildfailure due to unparseable pom-file
> -----------------------------------------------
>                 Key: INFRA-14280
>                 URL:
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Jenkins
>            Reporter: Philipp Ottlinger
>            Assignee: Gavin
> Hi,
> the builds seem to fail since Friday due to environment issues ....
> {code}
> Caused by: java.lang.NoSuchFieldError: DEFAULT_USER_SETTINGS_FILE
> 	at org.apache.maven.cli.DefaultMavenExecutionRequestBuilder.settings(
> 	at org.apache.maven.cli.DefaultMavenExecutionRequestBuilder.getMavenExecutionRequest(
> 	at org.jvnet.hudson.maven3.launcher.Maven33Launcher.getMavenExecutionRequest(
> 	at org.jvnet.hudson.maven3.launcher.Maven33Launcher.main(
> 	... 21 more
> ERROR: Failed to parse POMs
> java.lang.reflect.InvocationTargetException
> {code}

This message was sent by Atlassian JIRA

View raw message