Bug 1076193

Summary: Parsing of pom.xml file of the project running drools is not always possible
Product: [Retired] JBoss BRMS Platform 6 Reporter: Mario Fusco <mfusco>
Component: BREAssignee: Mario Fusco <mfusco>
Status: CLOSED CURRENTRELEASE QA Contact: Marek Winkler <mwinkler>
Severity: high Docs Contact:
Priority: high    
Version: 6.0.0CC: kverlaen, lpetrovi
Target Milestone: ER1   
Target Release: 6.0.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-08-06 19:54:19 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:

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.