[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [buckminster-dev] Partially resolved BOM
|
I wrote bug report with ID 170411.
Regards
Karel
----- Original Message -----
From: "Thomas Hallgren" <thomas@xxxxxxx>
To: "Buckminster developer discussions" <buckminster-dev@xxxxxxxxxxx>
Sent: Sunday, January 14, 2007 9:50 PM
Subject: Re: [buckminster-dev] Partially resolved BOM
Hi Karel,
Looks like you've encountered a bug in the Buckminster resolver. I think
that what happens is that instead of adding an unresolved node to the
BOM it, in fact, adds nothing at all. The effect is that the
isFullyResolved() method reports true since it doesn't encounter any
unresolved nodes.
Can you please add a bugzilla on this?
Kind Regards,
Thomas Hallgren
Karel Brezina wrote:
Hi,
for my tests I need to create a partially resolved BOM. However how to
create one?
As a source I used JUnit test
'org.eclipse.buckminster.core.test.rmap.BillOfMaterialsTest' with a
reduced RMap (I replaced '<rm:locator searchPathRef="buckminster.test"
pattern="^buckminster\.test\..+" />' with '<rm:locator
searchPathRef="buckminster.test" pattern="^buckminster\.test\.simple_d"
/>' in test.rmap).
This created a reduced BOM (just with 'simple_d' component), but the
problem is that 'bom.isFullyResolved() == true'.
Isn't there any problem with 'bom.isFullyResolved()' method? Should I
use a different method to check a partially resolved BOM?
Can someone help me in this issue?
Regards
Karel
_______________________________________________
buckminster-dev mailing list
buckminster-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/buckminster-dev
