-
Notifications
You must be signed in to change notification settings - Fork 0
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
Unable to load project requiring Maven 4.0.0-beta-5 #20
Comments
For me it looks like this: simplescreenrecorder-2024-11-08_11.30.14.mp4 |
That gives the following:
|
It looks like you have an old version of the plugin. What version of the IDEA and version GMaven do you have? |
Are you sure you've been using the branch I pointed at ? Because it also works if I use I'm using latest IntelliJ IDEA EAP (Build #IU-251.2067, built on October 25, 2024) and GMaven 233.30 |
Got it. Thank you. I'll fix it today. |
Try 242.3.1 version from beta https://plugins.jetbrains.com/plugin/22370-gmaven/versions/beta/630492?noRedirect=true |
Thx, it goes a bit further, but still does not load the project:
|
Sorry. My stupid mistake. I was in a hurry and didn't check all the tests. |
Same error.
|
My IDEA plugin zip archive (gmaven-242.3.2.zip) contains next jars:
Sync result stored in file -DresultFilePath=/Users/gnodet/work/git/mvnd/target/.gmaven.pom.json |
Installing the plugin manually in the repo did work. I think initially, gmaven was trying to use maven wrapper 3.9.9 instead of the version configured in |
Thank you for taking the time to help me find the problem with my plugin. Problem in first run deal with: "mvn install:install-file" to local repo.
I will be glad if my plugin helps you in your work. |
I reproduced this locally. The problem is the space is not escaped correctly. Created issue for removed this logic "mvn install:install-file" and deploy my maven-plugin to maven central and migrate on it. |
fixed since 242.4 |
Trying to load mvnd with the following branch (with Maven 4.x poms)
apache/maven-mvnd#1175
leads to the following error:
The text was updated successfully, but these errors were encountered: