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?
Thanks, From: Beth Tibbitts <[email protected]> To: Cross project issues <[email protected]>, Date: 02/12/2014 02:26 PM Subject: Re: [cross-project-issues-dev] Kepler SR2 RC3 aggregation fails Sent by: [email protected] Any news on this? ...Beth Beth Tibbitts [email protected] On Wed, Feb 12, 2014 at 6:04 AM, Ken Lee <[email protected]> wrote: Hi all, I just noticed that the Kepler aggregation job [1] fails due to a missing feature of the BIRT project: org.eclipse.birt.example.feature.group. The last commit was pushed by the BIRT project itself. Could anyone of them fix that? Thanks in advance. Ken [1] https://hudson.eclipse.org/hudson/view/Repository%20Aggregation/job/simrel.kepler.runaggregator/805/console _______________________________________________ cross-project-issues-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev _______________________________________________ cross-project-issues-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________ cross-project-issues-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
