Thanks, now the model validates, but I get a message (when running locally) related to the Eclipselink contribution:
Unable to load repository p2: http://download.eclipse.org/rt/eclipselink/milestone-updates/ 2.5.0.v20121120-ec51fcc_M5 Judging from the last couple of letters ("M5") perhaps there is some confusion about which milestone we're on? Probably just a naming issue? HTH From: Vincent Zurczak <vincent.zurc...@linagora.com> To: cross-project-issues-dev@eclipse.org, Date: 12/20/2012 01:14 PM Subject: Re: [cross-project-issues-dev] Status and outlook for Kepler M4 +3 Sent by: cross-project-issues-dev-boun...@eclipse.org Le 20/12/2012 18:44, David M Williams a écrit : This commit, did "break" aggregation. The reason is you removed the feature from your file, but its still "listed" in the "SOA Development" Category. When ever features are added or removed, I recommend using the b3 aggregator editor. It often effects not only your file, but the simrel.b3aggr file, where categories are defined. The "validate" action will say if the model is still valid and consistent. Both your file, and simrel.b3aggr must to checked in together. Perhaps you did make the change correctly, and simply forgot to check-in the simrel file? But, in any case, we don't need to re-spin now, for a removed feature, since it was disabled anyway, but will have to be fixed before we could aggregate, again. Indeed, my mistake. I have just pushed the simrel file too. Thanks, Vincent. commit e8b21c7ce2d64654edce952cac08c5f608031925 Author: vzurczak <vincent.zurc...@petalslink.com> Date: Thu Dec 20 15:23:23 2012 +0100 Remove a disabled feature. Signed-off-by: vzurczak <vincent.zurc...@petalslink.com> _______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
