search

Maximvdw / MVdWPlaceholderAPI

MVdW Placeholder API
8 stars 15 forks source link

Building error [Probably DependencyResolutionException] #21

Open GABRYCA opened 4 years ago

GABRYCA commented 4 years ago

Maven version isn't found for this plugin, i'm trying 3.0.1-SNAPSHOT and 3.0.2-SNAPSHOT but nothing

2.1.1-SNAPSHOT it's the only working

GABRYCA commented 4 years ago

Sorry, i fixed this by changing the spigot repository from public to snapshot: `

spigot-repo https://hub.spigotmc.org/nexus/content/repositories/snapshots/

`

GABRYCA commented 4 years ago

No, another error, changing the title, please help me.

When i build with maven: ` Downloading from mvdw-software: http://repo.mvdw-software.be/content/groups/public/org/spigotmc/spigot-api/1.14.4-R0.1-SNAPSHOT/maven-metadata.xml [WARNING] Could not transfer metadata org.spigotmc:spigot-api:1.14.4-R0.1-SNAPSHOT/maven-metadata.xml from/to mvdw-software (http://repo.mvdw-software.be/content/groups/public/): sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target [WARNING] Failure to transfer org.spigotmc:spigot-api:1.14.4-R0.1-SNAPSHOT/maven-metadata.xml from http://repo.mvdw-software.be/content/groups/public/ was cached in the local repository, resolution will not be reattempted until the update interval of mvdw-software has elapsed or updates are forced. Original error: Could not transfer metadata org.spigotmc:spigot-api:1.14.4-R0.1-SNAPSHOT/maven-metadata.xml from/to mvdw-software (http://repo.mvdw-software.be/content/groups/public/): sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target Downloading from mvdw-software: http://repo.mvdw-software.be/content/groups/public/net/md-5/bungeecord-chat/1.13-SNAPSHOT/maven-metadata.xml [WARNING] Could not transfer metadata net.md-5:bungeecord-chat:1.13-SNAPSHOT/maven-metadata.xml from/to mvdw-software (http://repo.mvdw-software.be/content/groups/public/): sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target [WARNING] Failure to transfer net.md-5:bungeecord-chat:1.13-SNAPSHOT/maven-metadata.xml from http://repo.mvdw-software.be/content/groups/public/ was cached in the local repository, resolution will not be reattempted until the update interval of mvdw-software has elapsed or updates are forced. Original error: Could not transfer metadata net.md-5:bungeecord-chat:1.13-SNAPSHOT/maven-metadata.xml from/to mvdw-software (http://repo.mvdw-software.be/content/groups/public/): sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target Downloading from mvdw-software: http://repo.mvdw-software.be/content/groups/public/net/md-5/bungeecord-parent/1.13-SNAPSHOT/maven-metadata.xml [WARNING] Could not transfer metadata net.md-5:bungeecord-parent:1.13-SNAPSHOT/maven-metadata.xml from/to mvdw-software (http://repo.mvdw-software.be/content/groups/public/): sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target Downloading from mvdw-software: http://repo.mvdw-software.be/content/groups/public/org/bukkit/bukkit/1.13.1-R0.1-SNAPSHOT/maven-metadata.xml [WARNING] Could not transfer metadata org.bukkit:bukkit:1.13.1-R0.1-SNAPSHOT/maven-metadata.xml from/to mvdw-software (http://repo.mvdw-software.be/content/groups/public/): sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target [WARNING] Failure to transfer org.bukkit:bukkit:1.13.1-R0.1-SNAPSHOT/maven-metadata.xml from http://repo.mvdw-software.be/content/groups/public/ was cached in the local repository, resolution will not be reattempted until the update interval of mvdw-software has elapsed or updates are forced. Original error: Could not transfer metadata org.bukkit:bukkit:1.13.1-R0.1-SNAPSHOT/maven-metadata.xml from/to mvdw-software (http://repo.mvdw-software.be/content/groups/public/): sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target Downloading from mvdw-software: http://repo.mvdw-software.be/content/groups/public/be/maximvdw/MVdWPlaceholderAPI/3.0.1-SNAPSHOT/maven-metadata.xml [WARNING] Could not transfer metadata be.maximvdw:MVdWPlaceholderAPI:3.0.1-SNAPSHOT/maven-metadata.xml from/to mvdw-software (http://repo.mvdw-software.be/content/groups/public/): sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target [WARNING] Failure to transfer be.maximvdw:MVdWPlaceholderAPI:3.0.1-SNAPSHOT/maven-metadata.xml from http://repo.mvdw-software.be/content/groups/public/ was cached in the local repository, resolution will not be reattempted until the update interval of mvdw-software has elapsed or updates are forced. Original error: Could not transfer metadata be.maximvdw:MVdWPlaceholderAPI:3.0.1-SNAPSHOT/maven-metadata.xml from/to mvdw-software (http://repo.mvdw-software.be/content/groups/public/): sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target Downloading from mvdw-software: http://repo.mvdw-software.be/content/groups/public/be/maximvdw/MVdWPlaceholderAPI/3.0.1-SNAPSHOT/MVdWPlaceholderAPI-3.0.1-SNAPSHOT.pom [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 5.357 s [INFO] Finished at: 2019-11-19T18:46:23+01:00 [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal on project PrisonRanks: Could not resolve dependencies for project it.gabryca.prison_ranks:PrisonRanks:jar:0.1-SNAPSHOT: Failed to collect dependencies at be.maximvdw:MVdWPlaceholderAPI:jar:3.0.1-SNAPSHOT: Failed to read artifact descriptor for be.maximvdw:MVdWPlaceholderAPI:jar:3.0.1-SNAPSHOT: Could not transfer artifact be.maximvdw:MVdWPlaceholderAPI:pom:3.0.1-SNAPSHOT from/to mvdw-software (http://repo.mvdw-software.be/content/groups/public/): sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException

Process finished with exit code 1 `

I get that error, i'm using the version 3.0.1-SNAPSHOT

Terminal-Access commented 3 years ago

This error is because maven now denies access to any repo's that have not moved to using secure web protocal "https" as you can see from the repository address above its insecure, and the owner of the website has not set up a valid certificate if you try and switch the URL to "https" this is a huge issue however luckly ther is a work around within maven.

Update - Fix 1 Have found that the ".com" tld for this repository has a valid cert and look to be a complete mirror of the ".be" repo. so simply switching the url and protocall will allow you to rebuild again.

Step 1: replace the ".bd" domain TLD with the ".com" domain TLD "MVdWPlaceholderAPI"

https://repo.mvdw-software.be/content/groups/public/

Step 2: Change To:

https://repo.mvdw-software.com/content/groups/public/

Long term fix for .be domain: Author/website owner of the ".be" domain TLD will need update the domain to use "https" and a valid ssl certificate. (for ssl certs look in to letsencrypt, they are free! and widly supported now.)

Hope this helps!

GABRYCA commented 3 years ago

This error is because maven now denied access to any repo's that have not moved to using secure web protocal "https" as you can see from the repository address above its insecure, and the owner of the website has not set up a valid certificate if you try and switch the URL to "https" this is a huge issue however luckly ther is a work around within maven.

Quick Fix: Add the following to your .m2 settings.yml - in the section:

<mirror>
  <id>mvdw-software-mirror</id>
  <mirrorOf>mvdw-software</mirrorOf>
  <url>http://repo.mvdw-software.be/content/groups/public/</url>
  <blocked>false</blocked>
</mirror>

"false" Tells maven to allow insecure http protocal use, this will allow you to use the repo again when building projects.

Long term fix: Author/website owner will need update the domain to use "https" and a valid ssl certificate. (for ssl certs look in to letsencrypt, they are free! and widly supported now.)

Hope this helps!

Hi, Thanks for the help, it's really appreciated. Have a nice day.

Terminal-Access commented 3 years ago

This error is because maven now denied access to any repo's that have not moved to using secure web protocal "https" as you can see from the repository address above its insecure, and the owner of the website has not set up a valid certificate if you try and switch the URL to "https" this is a huge issue however luckly ther is a work around within maven. Quick Fix: Add the following to your .m2 settings.yml - in the section:

<mirror>
    <id>mvdw-software-mirror</id>
    <mirrorOf>mvdw-software</mirrorOf>
    <url>http://repo.mvdw-software.be/content/groups/public/</url>
    <blocked>false</blocked>
</mirror>

"false" Tells maven to allow insecure http protocal use, this will allow you to use the repo again when building projects. Long term fix: Author/website owner will need update the domain to use "https" and a valid ssl certificate. (for ssl certs look in to letsencrypt, they are free! and widly supported now.) Hope this helps!

Hi, Thanks for the help, it's really appreciated. Have a nice day.

Not a problem, your very welcome, I have just updated my reply above with an alt quick fix that dosent require editing the .m2 settings.yml file.

Have a great day!

Terminal-Access commented 3 years ago

This error is because maven now denies access to any repo's that have not moved to using secure web protocal "https" as you can see from the repository address above its insecure, and the owner of the website has not set up a valid certificate if you try and switch the URL to "https" this is a huge issue however luckly ther is a work around within maven.

Update - Fix 1 Have found that the ".com" tld for this repository has a valid cert and look to be a complete mirror of the ".be" repo. so simply switching the url and protocall will allow you to rebuild again.

Step 1: replace the ".bd" domain TLD with the ".com" domain TLD "MVdWPlaceholderAPI"

<url>https://repo.mvdw-software.be/content/groups/public/<url/>

Step 2: Change To:

<url>https://repo.mvdw-software.com/content/groups/public/</url>

Long term fix for .be domain: Author/website owner of the ".be" domain TLD will need update the domain to use "https" and a valid ssl certificate. (for ssl certs look in to letsencrypt, they are free! and widly supported now.)

Hope this helps!

Updated Initial responce with a better/more perminant fix. removed the temp quick fixes.