| Questions on Aggregator [message #595762] |
Mon, 01 February 2010 03:49 |
 David Williams
Messages: 176
Registered: July 2009 |
Senior Member |
|
|
I have, finally, given the Aggregator a try this weekend, and it looks
like it has a lot of potential. I couldn't quite get it to do what I
wanted it to do, so figured I might be missing something. And, I heard,
this eclipse.b3 list would be a good place to ask.
First, I assume this is (still) the best/latest documentation?
http://wiki.eclipse.org/Buckminster_Aggregator_User_Guide
My fundamental question has to do with including versus excluding.
My goal, as a first-time experiment, was to make a simple composite repo
for Web Tools Platform Milestone "pointing to" the prereq milestone
repositories.
One such repo we would prereq is
http://download.eclipse.org/modeling/emf/updates/milestones/
So, starting off simply, I guess the default it it includes everything,
and I immediately get errors during a "build" that it couldn't find
dependencies for, say,
org.eclipse.emf.teneo.eclipselink
Understandable. We certainly don't pre-req those things like teneo or
eclipselink, and figured I'd just use an "exclusion rule" to not include
that. That "worked", but then there would be something else I had to
exclude. And something after that, and something after that.
After several hours of trying that, I begin to think it would be much
easier just to exclude everything by default, and specify exactly what I
wanted from the repository. Is that what the "mapped feature" is for?
That did not seem to be mentioned in the doc, or examples,
So, in short, how can I include just a few things, from a large, complex
repo like EMF? Do I really have to select scores of things to 'exclude'
just to get the 5 or so things to include?
It was made worse since it seemed like once I 'excluded' something I
could not go back and 'include' it. Is that a bug? Or something I'm
missing?
Another thing I may be missing is that I was thinking I could simply
"point to" the pre-req repositories, and then, when the build went to
"get" webtools features, it would just get exactly what it needed from
the pre-req repositories (much like a p2 'install') and not try to
determine ahead of time if everything in the pre-req repos was
consistent and if everything there could be installed. Is there some
setting/flag I'm missing? Or is this sort of "partial use" scenario
something that is not possible with Aggregator?
Much thanks for any insights.
|
|
|
Powered by
FUDForum. Page generated in 0.03102 seconds
] 
Search
Help
Register
Login
Home
