Bug 379538 - Wrong path in BOM to projects of "unknown" type, resulting in materialization error: "Unable to obtain resource .buckminster/Foo from <workspace>/Foo"
Summary: Wrong path in BOM to projects of "unknown" type, resulting in materialization...
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Buckminster (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: buckminster.core-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-15 08:53 EDT by Tobias Bertelsen CLA
Modified: 2019-02-25 14:40 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tobias Bertelsen CLA 2012-05-15 08:53:32 EDT
Build Identifier: Eclipse: 20120216-1857, Buckminster: 1.4.0.v20120405-0435

*********
*The setup:
*********
I have a plugin "Bar" which .classpath includes a reference to a non-java eclipse project called "Foo", so I added a dependency in the .cspex:

<dependency name ="Foo" componentType="unknown"/>

"Foo" doesn't have a .cspec-file (but shows up fine in the "ComponentExporer" with unknown type, if I import it manually)

My RMap primarily uses failOnError="false" instead of patterns to locate files.


*********
*The materialization:
*********
Using the wizard the dependency from Bar to Foo shows up fine, but if I materialize I get the following error:
"Unable to obtain resource .buckminster/Foo from <workspace>/Foo"

Trying to save the bom file reveals why; The providerId and repository attributes is wrong. They point to an other search path, than the one where "Foo" is found. (providerId and repository match each other though)

It seems rather arbitrary which search path it chooses in relation to the Rmap, but it's always the same. If I add a patterns the excludes "Foo" from that path,  a new wrong search path is assigned.


*********
*The workarrounds:
*********
Adding a Cspec to Foo just specifying name and type=buckminster solves the issue,
and I suppose making detailed patterns instead of using failOnError="false" in the Rmap will solve the issue. (Not tested completely)

Reproducible: Always

Steps to Reproduce:
Just redo the setup above.