|Re: [cross-project-issues-dev] Status and outlook for Mars M3 - disabled items, and Mac executable signing.|
Today's the last day to contribute to Mars M3 (unless there are exceptional circumstances).
Wanted to call attention to those contributions with some part "disabled". It is not the end of the world if they can not be re-enabled for M3, but I wanted to be sure none were simply "oversights" in changing the files.
mft.b3aggrcon - org.eclipse.simrel.build (2 matches)
mylyn-docs-intent.b3aggrcon - org.eclipse.simrel.build
objectteams.b3aggrcon - org.eclipse.simrel.build
soa-bpmn2-modeler.b3aggrcon - org.eclipse.simrel.build
Second, I should have announced this earlier, but if you haven't heard, there have been changes imposed by an outside Operating System maker. Apple changed it's "signing rules" recently, primarily for Yosemite, (10.10) but actually went in to effect in latest release of Maverick (10.9.5). There are two critical bugs where the work on our end is being tracked:
Bug 446390 - Change location of eclipse.ini (for Max OS X signing)
Bug 445050 - Need to update "Mac signing service"
Both of them "tough bugs". The "bottom line" for Mac executable signing is that it is not going to be possible, for M3. Users can still use the various "run anyway" work-arounds for unsigned executables, and with lots of luck (and effort from many skilled people) I hope we can get signing re-enabled for M4.
cross-project-issues-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
Back to the top