Bug 1076193 - Parsing of pom.xml file of the project running drools is not always possible
Summary: Parsing of pom.xml file of the project running drools is not always possible
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: BRE
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ER1
: 6.0.2
Assignee: Mario Fusco
QA Contact: Marek Winkler
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-13 18:21 UTC by Mario Fusco
Modified: 2014-08-06 19:54 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-08-06 19:54:19 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Mario Fusco 2014-03-13 18:21:12 UTC
At the moment we parse the pom.xml file also of the project running drools (and not only of the KieProject itself) with the purpose of trying to figure out if the user declared some additional repository in that pom so we could try to download the KieProject also from there. 

However parsing the pom.xml file of the running project is not always possible as reported here http://drools.46999.n3.nabble.com/rules-users-Avoid-parsiong-project-pom-xml-when-running-Drools-td4028690.html and when it happens the whole KieContainer creation fails.

I think we should keep this feature but also fail silently (or probably just emit a warning) when for any reason we are not able to parse the pom of the running project as in that case. This means that when this happens we will just use the repositories declared in the settings.xml file.

Comment 2 Mario Fusco 2014-03-13 18:34:43 UTC
Fixed by https://github.com/droolsjbpm/drools/commit/37ae0a625

Comment 3 Marek Winkler 2014-05-06 09:32:47 UTC
Verified on BRMS 6.0.2 ER2.


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