> if it is ok
for me to change some other group's
> b3aggrcon file.
I acted too quickly. :) Because otherwise I would
have said yes, of course its ok ... when there is an obvious error holding
up a green build, and especially when the group is in a different time
zone that makes a quick fix unlikely.
When that happens, just open a bug on cross-project
describing what you did ... or notify the group via this list.
Jeff Johnston <jjohnstn@xxxxxxxxxx>
Cross project issues
02/12/2014 02:36 PM
Kepler SR2 RC3 aggregation fails
I have a fix if it is ok for me to change some other
The example feature has an extraneous -Ys at the end of the identifier.
looked at the update-site referred to and that -Ys shouldn't be there.
Birt also added a new contact but didn't add that contact to the simrel.b3aggr
file so it doesn't validate for me locally using the b3aggrcon tools.
I also have a fix for that, assuming that chezy@xxxxxxxxxxx is Chezy Palani.