|
| Re: separating metadata from artifacts when mirroring [message #1005408 is a reply to message #1005393] |
Fri, 25 January 2013 10:03  |
|
Hi Lorenzo,
Yes, using a common bundle pool is one of the enhancements that we would
like to add. It wouldn't just benefit in minimizing the output from the
aggregator. It could also act as an input cache for aggregations where
common output is not desired. What kept us from implementing this so far
is lack of time and resources. Please add your thoughts on this topic to
this bugzilla:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=290623
- thomas
On 2013-01-25 09:42, Lorenzo Bettini wrote:
> Hi
>
> I don't know whether this makes sense, but would it be possible to
> generate metadata and artifacts into different directories when
> mirroring through the b3?
>
> I was thinking of this possible scenario: say you have different b3aggr
> files you use to mirror repositories for local builds of different and
> separate things (different projects, features, products) but they all
> have many features/bundles in common (e.g., rcp.sdk); if you
> build/mirror the repositories with these b3aggr files you end up with
> different build root directories with lots of duplicated artifacts. If
> artifacts could be stored in a common bundle pool and metadata in
> separate build directories most of the actual artifacts could be reused...
>
> cheers
> Lorenzo
>
|
|
|
Powered by
FUDForum. Page generated in 0.01948 seconds
] 
Search
Help
Register
Login
Home
