Bug 1305802 - KIE-CI does not warn the user when kjar's dependencies cannot be parsed [NEEDINFO]
Summary: KIE-CI does not warn the user when kjar's dependencies cannot be parsed
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: BRE
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Mario Fusco
QA Contact: Marek Winkler
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-09 09:51 UTC by Marek Winkler
Modified: 2020-03-27 19:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-27 19:11:09 UTC
Type: Bug
mwinkler: needinfo? (alazarot)


Attachments (Terms of Use)

Description Marek Winkler 2016-02-09 09:51:04 UTC
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.

Comment 2 Marek Winkler 2016-02-10 12:46:33 UTC
Created PR with reproducer: https://github.com/droolsjbpm/drools/pull/636


Note You need to log in before you can comment on or make changes to this bug.