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

Upgrade to Maven 3.8.1 and related dependency versions #38

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

aloubyansky
Copy link

This PR upgrades the Maven version to 3.8.1 and related dependency, such as the resolver and wagon, versions to the ones compatible with/included in the Maven 3.8.1 build.

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.

+1 from me. There is no particular reason to keep 3.5.4 as the target Maven version. It is already very old

@oleg-nenashev oleg-nenashev requested a review from olamy June 22, 2021 18:11
@olamy
Copy link
Member

olamy commented Jun 23, 2021

sounds good but does the plugin still work if using maven 3.6.3?

@oleg-nenashev
Copy link
Member

oleg-nenashev commented Jun 23, 2021 via email

@oleg-nenashev
Copy link
Member

@olamy @jenkinsci/core WDYT? I am +1 for merging and releasing

Comment on lines +115 to +116
<version>4.2.1</version>
<classifier>no_aop</classifier>
Copy link
Member

Choose a reason for hiding this comment

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

Copy link
Member

Choose a reason for hiding this comment

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

(Changing to a version newer than in core is certainly incorrect.)

Copy link
Author

Choose a reason for hiding this comment

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

Thanks for your time reviewing it. Just in case, the reason I updated this version is because Maven 3.8.1 depends on it. It doesn't necessarily mean it's a proper one in this case, just wanted to mention where it came from.

Copy link
Member

Choose a reason for hiding this comment

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

Maven 3.8.1 depends on it

Or claims to. Regardless, unless you take special steps, code loaded inside the Jenkins controller or agent is going to used the 4.0 bundled in core.

Copy link
Author

Choose a reason for hiding this comment

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

No problem. Thanks.

Copy link
Member

Choose a reason for hiding this comment

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

the 4.0 bundled in core

As of jenkinsci/jenkins#5858 this will be 5.x. The dependency should be deleted, and if necessary excluded from some other dependency.

Probably ought to have a RealJenkinsRule test verifying that this upgrade breaks nothing, and try on a recently weekly.

@cassidea
Copy link

cassidea commented Jan 5, 2022

Push

This issues blocks https://issues.jenkins.io/browse/JENKINS-59078

Would be very nice to use a Maven 3.6.1 feature before it's 3 years old.

pom.xml Outdated Show resolved Hide resolved
Comment on lines +115 to +116
<version>4.2.1</version>
<classifier>no_aop</classifier>
Copy link
Member

Choose a reason for hiding this comment

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

the 4.0 bundled in core

As of jenkinsci/jenkins#5858 this will be 5.x. The dependency should be deleted, and if necessary excluded from some other dependency.

Probably ought to have a RealJenkinsRule test verifying that this upgrade breaks nothing, and try on a recently weekly.

Co-authored-by: Jesse Glick <jglick@cloudbees.com>
@aloubyansky
Copy link
Author

@jglick sorry, I am busy with other issues currently and won't have time working on this further. I'll let you or somebody else close it as incomplete or drive this home. Thanks.

@cassidea
Copy link

cassidea commented Nov 3, 2022

Push

This issue still blocks https://issues.jenkins.io/browse/JENKINS-59078

@jglick
Copy link
Member

jglick commented Nov 3, 2022

Best to uninstall the very problematic and basically unmaintained maven-plugin and switch to Pipeline builds, adding the pipeline-maven plugin if desired.

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