-
Bug
-
Resolution: Done
-
Critical
-
6.0.0
Description of problem:
uploading mavenized jar with parent pom specified (see the attached jar) ends up with error in server log, when trying to add this jar to project as dependency (saying that groupId and version is missing - which is observable in UI as well)
Version-Release number of selected component (if applicable):
BRMS-6.0.0.ER2
Steps to Reproduce:
1. import attached jar into Asset repository
2. choose this artifact as dependency of your project
3. see the server log & UI
Expected results:
mavenized jar should be handled properly and groupId and version should be taken from the parent pom element
- blocks
-
RHBPMS-635 Tracking bz for user experience session
- Closed
- is related to
-
RHBRMS-1102 Importing mavenized jar with parent pom specified is not handled correctly
- Verified
- relates to
-
RHBRMS-1102 Importing mavenized jar with parent pom specified is not handled correctly
- Verified