Although I have added to global maven settings.xml this sequence (different from recommended by default for v7.15 in CONTRIBUTION.md file because is not valid anymore)
I not able build source files via mvn clean install -Pdistro-tomcat -DskipTests=true, received error:
[ERROR] Failed to execute goal on project camunda-bpm-tomcat: Could not resolve dependencies for project org.camunda.bpm.tomcat:camunda-bpm-tomcat:pom:7.15.0: Failed to collect dependencies at org.camunda.bpm.distro:camunda-sql-scripts:jar:7.15.0: Failed to read artifact descriptor for org.camunda.bpm.distro:camunda-sql-scripts:jar:7.15.0: Could not transfer artifact org.camunda.bpm.distro:camunda-sql-scripts:pom:7.15.0 from/to fix-maven-snapshots-issue-with-nexus (allow-parent-pom-resolving-when-snapshot): Cannot access allow-parent-pom-resolving-when-snapshot with type default using the available connector factories: BasicRepositoryConnectorFactory: Cannot access allow-parent-pom-resolving-when-snapshot using the registered transporter factories: HttpTransporterFactory, FileTransporterFactory, WagonTransporterFactory -> [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
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <args> -rf :camunda-bpm-tomcat
EDIT: even when I call mvn dependency:purge-local-repository a lot of repositories are downloading from old place https://app.camunda.com/nexus/content but in code of v7.15 it is replaced everywhere.
EDIT2: should I create mirror inside settings.xml?
I’m sorry but I’m going to ask you a silly question, after the settings.xml changes, you saved the file, right?
I asked because it really seems to me that everything is correct…
If everything is right, an alternative is to configure a <mirror> to force the download of the dependencies from the correct place and after… execute mvn dependency:purge-local-repository again.