Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JENKINS-43446 - java.lang.NoSuchFieldError: DEFAULT_USER_SETTINGS_FILE #11

Merged
merged 3 commits into from Jun 2, 2017

Conversation

tomerc
Copy link
Contributor

@tomerc tomerc commented Apr 10, 2017

Introduce an interceptor for Maven 3.5.0 and above which uses the DEFAULT_USER_SETTINGS_FILE from its new location at "org.apache.maven.cli.configuration.SettingsXmlConfigurationProcessor"

@oleg-nenashev
Copy link
Member

Would be nice to have a description for such long pull request

@tomerc
Copy link
Contributor Author

tomerc commented Apr 11, 2017

Updated comment

@aheritier
Copy link
Member

close/reopen to re-trigger the build which was killed by the timeout (> 300% than the previous build which took 47s)

Copy link
Member

@aheritier aheritier left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@aheritier
Copy link
Member

But one day ... we'll have to refactor the code to avoid all the copy/paste :(

@olamy
Copy link
Member

olamy commented Apr 11, 2017

lgtm.
Well I agree some refactor is needed to avoid all the copy/paste.

Copy link
Member

@oleg-nenashev oleg-nenashev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

semi-blind 👍 since I do not see newly introduced issues

@tomerc
Copy link
Contributor Author

tomerc commented Apr 11, 2017

Please hold off 1 day before merging, I found a bug that needs to be addressed before it's merged

@tomerc
Copy link
Contributor Author

tomerc commented Apr 11, 2017

I added the following:

  1. If in batch mode, disable the ANSI coloring (shows up as gibberish on the Jenkins console)
  2. If the maven.conf system.property does not exist, revert to maven 3.3 logic:
    new File(System.getProperty("maven.home", System.getProperty("user.dir", "")), "conf").getCanonicalPath()
  3. the main method in the launcher now requires ClassWorld as its second paramter

…E - Maven 3.5 requires ClassWorld in the main method
@aheritier
Copy link
Member

@tomerc take your time, I'll do more intensive tests before merging
About colors output I was thinking to propose to add the AnsiColor plugin as a dep of the maven-plugin and automatically configure it if Maven >= 3.5
It shouldn't be so hard. WDYT ?

@tomerc
Copy link
Contributor Author

tomerc commented Apr 11, 2017

@aheritier Thanks! I think if we can make use of the AnsiColor plugin that would be great. Right now the -B option is always passed to the embedder and if I remember what Hevre wrote in the mailing list, if you execute Maven via the CLI with -B it would turn off the colors, so this would make it consistent, but perhaps we can override that for Maven 3.5?

@aheritier
Copy link
Member

Yes confirm, -B deactivates the color like said @hboutemy But yes we can probably hack it :-)

@dreis2211
Copy link
Contributor

Hi @aheritier . Any news on the progress?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
5 participants