[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [ecf-dev] builder offline
|
The rsa service was stored as binary project in the git repo, but also
in the ECF p2 repo. Before all this, the rsa service was resolved from
the p2 repo even though it was available as project in the git repo.
Now since the version number was incremented to 5 in the git repo,
some plugins resolved the rsa from the ecf p2 repo and others tried to
resolve it from the git repo (local). AFAICT the threshold error was
caused by it not being a source project.
By creating a separate rule for rsa to only resolve it from the git
repo as binary, this caused it to resolve correctly but for some
reason it did not use it in the build.
I think this is where the mspec rules kick in?
On Fri, May 4, 2012 at 9:15 AM, Markus Alexander Kuppe
<ecf-dev_eclipse.org@xxxxxxxxxxx> wrote:
> On 05/03/2012 08:41 PM, Scott Lewis wrote:
>> Hi Markus,
>>
>> First...thanks...compile deps seem to resolve now.
>>
>> Would you just say a couple of words (publicly) about what this change
>> does...just so that we can share the knowledge?
>
> The cquery/mspec generally instruct Buckminster where to search for
> artefacts and how to materialize each of them.
> Since .rsa is a binary artefact that sits in our git repo, Bucky needs
> to know where to find it. This is what the lines in the cquery/mspec do.
>
> Markus
> _______________________________________________
> ecf-dev mailing list
> ecf-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ecf-dev