Fix dependency resolving in visual studio code #26
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
slachiewicz
approved these changes
Jul 24, 2023
|
Sorry, accidentally closed it, just reopened it now |
|
Thanks for merging. Do you have an idea if a 2.1.1 release is somewhere coming? |
Sorry for long waiting, it should make it to Maven Central in few hours: https://repo1.maven.org/maven2/org/codehaus/mojo/native2ascii-maven-plugin/ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In visual studio code, we cannot open our project correctly due to the encoding in the maven lifecycle metadata xml file being ISO-8859-1.
We get this error:
Cannot read lifecycle mapping metadata for artifact org.codehaus.mojo:native2ascii-maven-plugin:maven-plugin:2.1.0:runtime Cause: UTF-8 BOM plus xml decl of ISO-8859-1 is incompatible (position: START_DOCUMENT seen <?xml version="1.0" encoding="ISO-8859-1"... @1:42)