-
-
Notifications
You must be signed in to change notification settings - Fork 347
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
[Question] MavenLauncher always fails #5030
Comments
Spoon executes |
That helps! I do not know why there have some issues in the original open source project when building classpath. After I cleanup the issue it works! |
Great! I don't know either, but the statistics for building random maven projects from github aren't exactly rosy, so I am not too surprised :P I think this issue can be closed then, feel free to comment or re-open if not :)
I am not aware of any plan currently. Have a look at the submodule policy introduced in #4930 for reference. You can use e.g. jitpack to let it build the module for you, if you want though. |
I am trying to |
I am not sure what you mean. spoon-core is hosted on maven central and maven central supports https. Spoon itself also builds in CI without special settings (and on my computer with maven 3.8.6) without any adjustments. Could you tell me which part of spoon uses an http repository? |
I also did not find where's the misconfiguration. I reproduced by created a new maven project and only import the spoon dependency in pom.xml. And the console displays From Internet resources (https://stackoverflow.com/questions/66980047/maven-build-failure-dependencyresolutionexception), it seems that maven > 3.8.1 will perform like this due to |
@backcover7 Using the following pom: <?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>de.ialistannen</groupId>
<artifactId>Foobar</artifactId>
<version>1.0-SNAPSHOT</version>
<properties>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<maven.compiler.target>19</maven.compiler.target>
<maven.compiler.source>19</maven.compiler.source>
</properties>
<dependencies>
<dependency>
<groupId>fr.inria.gforge.spoon</groupId>
<artifactId>spoon-core</artifactId>
<version>10.2.0</version>
</dependency>
</dependencies>
</project> I can create a project without a problem :) I can also create a project without a problem in the |
Your XML still does not work on my side. Have you ever customized your settings.xml in .m2? Here's my verbose output on my side. ( |
I mean, I also ran it in a docker image as I said above. The docker image does not ship with a .m2 folder and neither did I adjust my config. It also never touches the inria.fr repository (and why would it? The XML above does not configure this repository):
|
Not sure if it's my problem. But it seems the root cause is the dependency |
But nothing in spoon uses the This is really weird. Does it work for you if you use the |
@I-Al-Istannen Sorry for the late reply. It works for me now. |
@Kang-Hou Are you the OP? If so, I am glad and thanks for your comment :) If not, I am also glad but a tad confused ;) |
You can not (except for writing your own mvn wrapper and putting that earlier in the PATH). Spoon uses the maven API and expects that to work. What does your |
I am not sure if there's any configuration problem on my local side, but I cannot use MavenLauncher to load any source code.
I tried to load the following two projects with MavenLauncher, all of them failed.
The error info contains something like
Could not transfer metadata org.codehaus.mojo:javancss-maven-plugin/maven-metadata.xml from/to apache.snapshots
,Error resolving version for plugin
Here is my code.
The text was updated successfully, but these errors were encountered: