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.

Sign up for GitHub

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

Jump to bottom

Fixes #321 fail the build when parsing XML of child modules fails due to invalid XML #399

Merged
merged 1 commit into from
May 20, 2020
Merged

Fixes #321 fail the build when parsing XML of child modules fails due to invalid XML #399

merged 1 commit into from
May 20, 2020

Conversation

stefanseifert
Copy link
Contributor

Fixes #321

@stefanseifert stefanseifert mentioned this pull request May 20, 2020
Closed
@khmarbaise khmarbaise self-assigned this May 20, 2020
@khmarbaise khmarbaise added this to the 2.8.0 milestone May 20, 2020
@khmarbaise khmarbaise merged commit 9e1d45c into mojohaus:master May 20, 2020
@stefanseifert
Copy link
Contributor Author

that was fast, thanks!

@stefanseifert stefanseifert deleted the issue/321-invalid-pom branch May 20, 2020 16:33
@khmarbaise
Copy link
Member

Clean; separate IT's. cleanly defined. Exactly focused change. The CI worked without breaking anything. You're welcome. Well done. Thanks

@khmarbaise khmarbaise mentioned this pull request May 29, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@khmarbaise khmarbaise

Labels
enhancement
Projects
None yet
Milestone
2.8
Development

Successfully merging this pull request may close these issues.

Updating invalid pom.xml is skipped silently
2 participants
@stefanseifert @khmarbaise