[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[buckminster-dev] Naming of components that are not projects
|
When Buckminster materializes needed components, some of them will not
map to Eclipse projects. This is particularly true for pre-compiled
binaries. Buckminster needs a place to store such artifacts on the local
file system since projects will express references to them in classpaths
etc.
The meta-data for the artifacts are always stored in the workspace,
hence it's not advisable to share the artifact locations between
different workspaces. In order to do that, Buckminster would need to
have a global meta-data repository (might be something to think more
about for the future). So storing the artifacts somewhere relative to
the workspace sounds like a good idea.
There's a danger of colliding with projects that reside physically in
the workspace root. In order to minimize such collisions, all
"non-projects" should reside below one single directory. What should
this directory be called by default? It should of course also be
settable using a preference.
Suggestions:
- nonProjects
- externalComponents
- ...
Ideas, suggestions?
Regards,
Thomas Hallgren
