No connector available to access repository ... of type default using the available factories WagonRepositoryConnectorFactory #25
Comments
|
Were you ever able to resolve or get more information on this issue? |
|
Unfortunately no. Would still love to use it though... |
|
We ended up creating an uber jar of the maven wagon and putting it in the maven lib directory. Then maven was able to load the wagon before trying to connect to S3 and the connection was successful. |
|
The general issue seems to be, that you cannot fetch the parent of a project via S3, because Maven tries to load the parent before it loads the S3 plugin. Adding the dependency to Maven's lib folder is clever, but not a solution for us since we're using a hosted Jenkins where we cannot put JARs into the Maven lib folder. I'm out of ideas for this problem. Not sure if there's a good solution... |
|
Hello, We have exactly the same problem xeraa has. Has anyone found a solution without using the uber jar? |
|
i don't think there is a good solution. and i've written a blog post about the whole thing, which might be interesting: https://medium.com/@xeraa/why-s3-is-not-the-perfect-maven-repository-8b06cb103a57 |
|
Since Maven version 3.3.1 it's possible to add core extensions trough an additional extensions.xml (see https://issues.apache.org/jira/browse/MNG-5771) no patching needed, just add an extensions.xml at ${maven.projectBasedir}/.mvn/extensions.xml to your project: <extensions xmlns="http://maven.apache.org/EXTENSIONS/1.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/EXTENSIONS/1.0.0 http://maven.apache.org/xsd/core-extensions-1.0.0.xsd">
<!-- Repository on AMAZON S3 -->
<extension>
<groupId>org.springframework.build</groupId>
<artifactId>aws-maven</artifactId>
<version>5.0.0.RELEASE</version>
</extension>
</extensions> |
|
This doesn't help this use case at the project level. It needs to be at a global level similar to what was mentioned (but apparently not addressed) by yuri in your referenced issue: https://issues.apache.org/jira/browse/MNG-5771 |
|
Hi everyone, 2 years later, did someone came up with a solution for this? We are just looking for Maven+S3 to avoid Nexus/Artifactory but I'm afraid this problem won't allow us to. |
|
@jfneis what's the OS where you face this issue? And what's the gradle version and how did you install it? |
|
@esaounkine I'm using Ubuntu 16 and Maven, no Gradle at all. |
|
@feliperazeek I was able to do it in project level too. The "fix" I asked for was about a global maven level. |
I've set up the AWS Maven wagon in a project and it's working as expected — the Maven artifact is uploaded to our S3 account with the correct permissions.
However, when I try to reuse the artifact in another project, the download fails, because it cannot find a wagon to fetch from S3. The output of
$ mvn deploy -X:I have added the wagon in both projects:
Do I need to register it somehow for downloads or what could I be doing wrong? I'm sure it's just something stupid on my part, but I'm unable to find it even though I've gone through the documentation multiple times...
The text was updated successfully, but these errors were encountered: