Unable to build from source v7.15

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)

<profiles>
  <profile>
    <id>camunda-bpm</id>
    <repositories>
      <repository>
        <id>camunda-bpm-nexus</id>
        <name>camunda-bpm-nexus</name>
        <releases>
          <enabled>true</enabled>
        </releases>
        <snapshots>
          <enabled>true</enabled>
        </snapshots>
        <url>https://app.camunda.com/nexus/content/groups/public</url>
      </repository>
    </repositories>
  </profile>
</profiles>
<activeProfiles>
  <activeProfile>camunda-bpm</activeProfile>
</activeProfiles>

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

Full stack: Build Camunda v7.15 from source error · GitHub

Hello my friend!

Take a look at this article below:

If this doesn’t help you… try clearing maven’s cache.
mvn dependency:purge-local-repository

William Robert Alves

1 Like

Thank you a lot.

So I tried to replace all these in code of v7.15

https://app.camunda.com/nexus/content/repositories/camunda-bpm/ → https://artifacts.camunda.com/artifactory/camunda-bpm

https://app.camunda.com/nexus/content/groups/public/ → https://artifacts.camunda.com/artifactory/public/ 

but still, I see maven packages are downloading from https://app.camunda.com/nexus/content/groups/public. The same error. Any idea what I do wrong?

Hello my friend! \o/

Did you update the profile repository?
If you have already updated your settings.xml, try running the command below again:

mvn clean install -Pdistro-tomcat -DskipTests=true

I believe this will help.

William Robert Alves

What do you mean?

In settings.xml I have only this (depending to camunda)

    <profile>
      <id>camunda-bpm</id>
      <repositories>
        <repository>
          <id>camunda-bpm-nexus</id>
          <name>camunda-bpm-nexus</name>
          <releases>
            <enabled>true</enabled>
          </releases>
          <snapshots>
            <enabled>true</enabled>
          </snapshots>
          <url>https://artifacts.camunda.com/artifactory/public/</url>
        </repository>
      </repositories>
    </profile>
  </profiles>
    <activeProfile>camunda-bpm</activeProfile>

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?

Apparently what you did is correct!

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… :thinking:

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.

Hope it works…

William Robert Alves

Forgot to change also local maven settings.xml. Works like a charm. Thank you!

1 Like

Very cool! :smile:
I’m glad I was able to help, my friend! \o

An excellent weekend for all of us!

William Robert Alves

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.