Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Kepler SR2 RC3 aggregation fails



I did not notice that changing contacts need other change. Thanks for the knowledge.

And yes, the "example feature" error is a typo and thanks for fixing that.






From: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of David M Williams
Sent: 2014
213 3:40
To: Cross project issues
Subject: Re: [cross-project-issues-dev] Kepler SR2 RC3 aggregation fails


Sorry for the delay, but I've just now fixed (I think).

The Birt contribution had two errors (which I detail here in case I "corrected" in wrong way ... and so others can learn):
a) A contact was added to the birt.b3aggrcon file, but that contact did not exist in the simrel.aggr file -- a common error ... Contacts should be added with the b3 aggregation editor, since effects two files, and then  both files have to be committed/pushed.
b) after fixing that, it seemed that their "example feature" had an extra "-Ys" at the end ... I assume just a type?


From:        Beth Tibbitts <beth@xxxxxxxxxx>
To:        Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>,
Date:        02/12/2014 02:26 PM
Subject:        Re: [cross-project-issues-dev] Kepler SR2 RC3 aggregation fails
Sent by:        cross-project-issues-dev-bounces@xxxxxxxxxxx

Any news on this?


Beth Tibbitts

On Wed, Feb 12, 2014 at 6:04 AM, Ken Lee <Ken.Lee@xxxxxxxxx> wrote:
Hi all,


I just noticed that the Kepler aggregation job [1] fails due to a missing feature of the BIRT project:

The last commit was pushed by the BIRT project itself. Could anyone of them fix that?


Thanks in advance.






cross-project-issues-dev mailing list

cross-project-issues-dev mailing list

Back to the top