-
Bug
-
Resolution: Done
-
Critical
-
6.0.3
-
None
Description of problem:
If we declared a remote repository in pom.xml of your BPM Suite project, it will not look for artifacts on the remote server. Here's an example of a repository declared in pom.xml:
<project ...>
<repositories>
<repository>
<id>my.repo</id>
<url>https://my-nexus/content/repositories/public/</url>
</repository>
</repositories>
</project>
Version-Release number of selected component (if applicable):
6.0.3
How reproducible:
Always.
Steps to Reproduce:
1. Create a project in BPM Suite
2. Declare an artifact as a dependency which is in a nexus or any other remote repository
3. Declare the repository in pom.xml as showed above
Actual results:
The artifact is not downloaded from the remote repository and it is not possible to build the project
Expected results:
The artifact should be downloaded to the local maven and the project should be built.
Additional info:
it seems that it ignores the repository declared in pom.xml, but it works when we declare it in settings.xml
- is related to
-
RHBRMS-1079 Importing mavenized jar is not handled correctly - pom import from custom repository
- Closed
- relates to
-
RHBRMS-1079 Importing mavenized jar is not handled correctly - pom import from custom repository
- Closed