Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
[MPH-217] Ensure packaging is always shown in effective-pom output #405
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
base: master
Are you sure you want to change the base?
Uh oh!
There was an error while loading. Please reload this page.
[MPH-217] Ensure packaging is always shown in effective-pom output #405
Changes from all commits
d7b316abdedfe9f5e9557File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
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.
If given project has parent, like
which
</version>will be replaced in l. 206?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.
I updated IT presented here with:
And here is test result: SUCCESS.
But here is the goal result:
This is of course non-sense for parent.
And, perhaps according to
String.replacejavadoc (Replaces each substring of this string that matches the literal target sequence), every</version>, including plugins' - has explicit<packaging>jar</packaging>companion now.I don't think it's correct...
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.
To clarify above - even without any modification to this PR - manual inspection of
target/it/effective-pom-packaging/build.logshows that too much is done to the effective pom.Perhaps
src/it/projects/effective-pom-packaging/verify.groovycould be fixed to check that only expected changes are there (i.e. no unexpected changes are).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.
Good point and a good reminder of why regexes are dangerous when processing XML. There are other failure modes here too. I might take a whirl at fixing this with some real XML.
Uh oh!
There was an error while loading. Please reload this page.