You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 30, 2019. It is now read-only.
I would configure my repositories in settings.xml instead of in my pom.xml. This works fine for the built in wagon since these are in the class path, but how to do the same for s3? E.g.:
One solution is to copy aws-maven and all of its dependencies to the maven installation or the JDK installation, but considering that we have many maven installs and usually update versions quite often I would like to have Maven resolve aws-maven automatically from settings.xml (after all isn't this the whole point of Maven?). Is that possible?
The text was updated successfully, but these errors were encountered:
In my case, I have a parent pom with the distributionManagement and s3 wagon extension configured. Now, in a build server, I couldn't build the child project. As s3 wagon is configured in parent, it could not download the parent. If I can configure the wagon in settings.xml instead of parent, this problem will be solved.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I would configure my repositories in settings.xml instead of in my pom.xml. This works fine for the built in wagon since these are in the class path, but how to do the same for s3? E.g.:
One solution is to copy aws-maven and all of its dependencies to the maven installation or the JDK installation, but considering that we have many maven installs and usually update versions quite often I would like to have Maven resolve aws-maven automatically from settings.xml (after all isn't this the whole point of Maven?). Is that possible?
The text was updated successfully, but these errors were encountered: