0

I am trying to create Spring Boot application with Netbeans Wizard. However, I get an error right after creation.

  Downloading: http://repo.maven.apache.org/maven2/org/springframework/boot/spring-boot-starter-parent/2.2.4.RELEASE/spring-boot-starter-parent-2.2.4.RELEASE.pom

 The build could not read 1 project -> [Help 1]

 The project com.example:demo:0.0.1-SNAPSHOT (C:\Users\me\application\pom.xml) has 1 error
 Non-resolvable parent POM: Could not transfer artifact 
org.springframework.boot:spring-boot-starter-parent:pom:2.2.4.RELEASE from/to central 
  (http://repo.maven.apache.org/maven2): Failed to transfer file: 
  http://repo.maven.apache.org/maven2/org/springframework/boot/spring-boot-starter- 
  parent/2.2.4.RELEASE/spring-boot-starter-parent-2.2.4.RELEASE.pom. Return code is: 
501 , ReasonPhrase:HTTPS Required. and 'parent.relativePath' points at wrong local POM @ line 5, column 10 -> [Help 2]

    To see the full stack trace of the errors, re-run Maven with the -e switch.
     Re-run Maven using the -X switch to enable full debug logging.

   For more information about the errors and possible solutions, please read the 
  following articles:
  [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException

So, Maven is not getting to the central repository, but can anyone tell me why this is?

  • Central is only accessible via https and not http anymore see https://blog.sonatype.com/central-repository-moving-to-https I strongly recommend to upgrade your maven version.... – khmarbaise Feb 21 '20 at 11:47
  • I was using Netbeans Maven plugin. Should I not use that? – javatar Feb 21 '20 at 11:51
  • 1
    Either you need to configure the Netbeans Wizard to use https or upgrade to a newer version. – J Fabian Meier Feb 21 '20 at 12:24
  • @javatar, possibly duplicate, please see [this](https://stackoverflow.com/a/60093266/5681468) – Dmitry.M Feb 21 '20 at 12:47
  • 1
  • Not a duplicate of your question, but see [Netbeans not showing Known Archetypes with new Project from Archetype](https://stackoverflow.com/q/60291007/2985643). The author provides their own solution, and the problem was the use of _http_ instead of _https_. – skomisa Feb 21 '20 at 16:08

0 Answers0