-
-
Notifications
You must be signed in to change notification settings - Fork 77
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
Flatten repositories from JEP-229 plugins #802
Conversation
This workarounds mojohaus/flatten-maven-plugin#362 and strips <repositories> from deployed pom for plugins using JEP-229
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would also be great to have an IT covering the basic build cycle of a JEP-229-based plugin unlike
-Pconsume-incrementals | |
-Pmight-produce-incrementals |
Co-authored-by: Jesse Glick <[email protected]>
I'll see what I can do |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice!
assert installedPom.text.contains("<scm>") | ||
assert !installedPom.text.contains("<properties>") | ||
assert !installedPom.text.contains("<dependencyManagement>") | ||
assert !installedPom.text.contains("<repositories>") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(the point of the PR, FTR)
Co-authored-by: Jesse Glick <[email protected]>
Does this need to be side-ported to https://github.com/jenkinsci/pom? |
Good point, jenkinsci/pom#464 |
This workarounds mojohaus/flatten-maven-plugin#362
and strips
<repositories>
from deployed pom for plugins using JEP-229.Testing done
Submitter checklist