Bug 1305802
| Summary: | KIE-CI does not warn the user when kjar's dependencies cannot be parsed | ||
|---|---|---|---|
| Product: | [Retired] JBoss BRMS Platform 6 | Reporter: | Marek Winkler <mwinkler> |
| Component: | BRE | Assignee: | Mario Fusco <mfusco> |
| Status: | CLOSED EOL | QA Contact: | Marek Winkler <mwinkler> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.2.0 | CC: | alazarot |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-03-27 19:11:09 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Created PR with reproducer: https://github.com/droolsjbpm/drools/pull/636 The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |
Description of problem: KIE-CI does not warn the user when kjar's dependencies cannot be parsed because of missing <version> (the version is defined in parent pom's <dependencyManagement>). Please note that KIE-CI logs a message when the <version> is specified, but not in expected format (fir instance, ${project.version}). This issue could be covered by BZ 1305798, but I have created this BZ in order to add a warning/error in the case of missing <version> in the short term. The lack of any warning/error might be very confusing for users who can hit this issue usually in OSGi environment. Version-Release number of selected component (if applicable): BRMS 6.2.1 How reproducible: always Steps to Reproduce: The same reproducer as for BZ 1305798. I am going to provide a test for this later. Actual results: No error/warning in the log, parsing of the kjar's pom.xml succeeds. Expected results: At least an error/warning should be produced. Not sure if parsing of the kjar's pom.xml should fail, we should probably not change this behaviour for 6.2.