Uploaded image for project: 'Red Hat Process Automation Manager'
  1. Red Hat Process Automation Manager
  2. RHPAM-2160

Deploying projects through Business Central does not honour altReleaseDeploymentRepository and altSnapshotDeploymentRepository maven settings

    XMLWordPrintable

Details

    • Hide

      Install RHPAM.7.3.1 and Nexus3 (or any other Maven repository manager) locally.

      Add the following to the "settings.xml" that this installation of RHPAM is using:

          <profile>
            <id>enforce_nexus</id>
            <properties>
              <altReleaseDeploymentRepository>nexus_local_release::http://localhost:8081/repository/maven-releases/</altReleaseDeploymentRepository>
              <altSnapshotDeploymentRepository>nexus_local_snapshot::http://localhost:8081/repository/maven-snapshots/</altSnapshotDeploymentRepository>
            </properties>
          </profile>
        </profiles>
      
      

      and also the following to the "activeProfiles" section:

          <activeProfile>enforce_nexus</activeProfile>
      

      Also in the same "settings.xml" add authentication information for the locally installed Maven repository manager. For example for a Nexus3 with default settings something like the following:

          <server>
            <id>nexus_local_release</id>
            <username>admin</username>
            <password>admin123</password>
          </server>
          <server>
            <id>nexus_local_snapshot</id>
            <username>admin</username>
            <password>admin123</password>
          </server>
        </servers>
      

      Create any kind of project in Business Central and build/deploy it. Project will be visible in the internal RHPAM maven repo, but not in the external Maven/Nexus repo.

      On the other hand and project build/deployed using the same "settings.xml" will end up in the locally installed Maven/Nexus repo. For example create a sample project based on KIE archetypes, as in:

       mvn archetype:generate -DgroupId=com.example.rulis1 -DartifactId=rulis1 \
                              -DarchetypeGroupId=org.kie -DarchetypeArtifactId=kie-drools-archetype -DarchetypeVersion=7.21.0.Final \
                              -DpomEclipseCompatible=true
      

      Build and deploy it. Build artefact should be visible in the external Maven/Nexus repo

      Show
      Install RHPAM.7.3.1 and Nexus3 (or any other Maven repository manager) locally. Add the following to the "settings.xml" that this installation of RHPAM is using: <profile> <id> enforce_nexus </id> <properties> <altReleaseDeploymentRepository> nexus_local_release::http://localhost:8081/repository/maven-releases/ </altReleaseDeploymentRepository> <altSnapshotDeploymentRepository> nexus_local_snapshot::http://localhost:8081/repository/maven-snapshots/ </altSnapshotDeploymentRepository> </properties> </profile> </profiles> and also the following to the "activeProfiles" section: <activeProfile> enforce_nexus </activeProfile> Also in the same "settings.xml" add authentication information for the locally installed Maven repository manager. For example for a Nexus3 with default settings something like the following: <server> <id> nexus_local_release </id> <username> admin </username> <password> admin123 </password> </server> <server> <id> nexus_local_snapshot </id> <username> admin </username> <password> admin123 </password> </server> </servers> Create any kind of project in Business Central and build/deploy it. Project will be visible in the internal RHPAM maven repo, but not in the external Maven/Nexus repo. On the other hand and project build/deployed using the same "settings.xml" will end up in the locally installed Maven/Nexus repo. For example create a sample project based on KIE archetypes, as in: mvn archetype:generate -DgroupId=com.example.rulis1 -DartifactId=rulis1 \ -DarchetypeGroupId=org.kie -DarchetypeArtifactId=kie-drools-archetype -DarchetypeVersion=7.21.0.Final \ -DpomEclipseCompatible=true Build and deploy it. Build artefact should be visible in the external Maven/Nexus repo

    Description

      As reported at [BPMSPLDOC-14] documentation states that it is possible to deploy to external Maven repository through configuring an installation wide "settings.xml" file.

      However providing a "settings.xml" file that has a profile using "altReleaseDeploymentRepository" and "altSnapshotDeploymentRepository" elements and using it to build and project in Business Central does not result in the build artefact deployed in the external Nexus repository.

      Attachments

        Activity

          People

            eignatow Eder Ignatowicz
            rouvas Stathis Rouvas (Inactive)
            Barbora Siskova Barbora Siskova
            Barbora Siskova Barbora Siskova
            Votes:
            3 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: