[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) and 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. Thanks, ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Status and outlook for Mars M3 - disabled items, and Mac executable signing.
Hi David, I just checked soa-bpmn2-modeler and it seems to be enabled for mars on the project website [1] and the repository references by soa-bpmn2-modeler.b3aggrcon is also in place [2]. What else am I missing? Thanks, Bob [1] https://projects.eclipse.org/projects/soa.bpmn2-modeler [2] http://download.eclipse.org/bpmn2-modeler/updates/mars/1.1.1 - Original Message - 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) and 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. Thanks, ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Status and outlook for Mars M3 - disabled items, and Mac executable signing.
What else am I missing? In your contribution file, soa-bpmn2-modeler.b3aggrcon - org.eclipse.simrel.build is says repositories enabled=false Which means it is not being contributed to the simrel repository ... (ending up in .../releases/staging, and ultimately .../releases/mars). From looking at Git history, it appears I disabled it 3 months ago (presumably because it was causing the whole build to fail), and then 6 week ago, you updated the URL, but you forgot (or, didn't know) to remove enabled=false. Hope that clarifies it. Thanks, From: Bob Brodt bbr...@redhat.com To: Cross project issues cross-project-issues-dev@eclipse.org, Date: 11/12/2014 10:50 AM Subject:Re: [cross-project-issues-dev] Status and outlook for Mars M3 - disabled items, and Mac executable signing. Sent by:cross-project-issues-dev-boun...@eclipse.org Hi David, I just checked soa-bpmn2-modeler and it seems to be enabled for mars on the project website [1] and the repository references by soa-bpmn2-modeler.b3aggrcon is also in place [2]. What else am I missing? Thanks, Bob [1] https://projects.eclipse.org/projects/soa.bpmn2-modeler [2] http://download.eclipse.org/bpmn2-modeler/updates/mars/1.1.1 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) and 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. Thanks, ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Status and outlook for Mars M3 - disabled items, and Mac executable signing.
Thanks David! - Original Message - What else am I missing? In your contribution file, soa-bpmn2-modeler.b3aggrcon - org.eclipse.simrel.build is says repositories enabled = false Which means it is not being contributed to the simrel repository ... (ending up in .../releases/staging, and ultimately .../releases/mars). From looking at Git history, it appears I disabled it 3 months ago (presumably because it was causing the whole build to fail), and then 6 week ago, you updated the URL, but you forgot (or, didn't know) to remove enabled=false. Hope that clarifies it. Thanks, From: Bob Brodt bbr...@redhat.com To: Cross project issues cross-project-issues-dev@eclipse.org, Date: 11/12/2014 10:50 AM Subject: Re: [cross-project-issues-dev] Status and outlook for Mars M3 - disabled items, and Mac executable signing. Sent by: cross-project-issues-dev-boun...@eclipse.org Hi David, I just checked soa-bpmn2-modeler and it seems to be enabled for mars on the project website [1] and the repository references by soa-bpmn2-modeler.b3aggrcon is also in place [2]. What else am I missing? Thanks, Bob [1] https://projects.eclipse.org/projects/soa.bpmn2-modeler [2] http://download.eclipse.org/bpmn2-modeler/updates/mars/1.1.1 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) and 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. Thanks, ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
[cross-project-issues-dev] Creating a new category in the simrel update site: Tracing
Hi, We would like to add a new category to the simultaneous release update site called Tracing. It is my understanding that adding such a category needs to be discussed and approved first. We would like to add this category because some features do not fit well into existing categories such as LTTng trace analysis, GDB trace and Pcap analysis. Those features are being moved from the Linux Tools project to the Trace Compass project. We also don't think a Trace Compass category would be good because the categories should be seen as themes to the user and not project structure. Also, we think other features could be placed under the Tracing category, like SystemTap support. Let us know what you think! Regards, Marc-Andre Laperle ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Creating a new category in the simrel update site: Tracing
Seems reasonable ... I wonder if it can be broadened a little to include Testing? But, in any case, please open a cross-project bug, and after a few weeks of discussion we can probably come to a conclusion. (That is, not in time for M3, but in time for M4). Thanks for suggestions to improve the categorization. From: Marc-André Laperle marc-andre.lape...@ericsson.com To: cross-project-issues-dev@eclipse.org cross-project-issues-dev@eclipse.org, Date: 11/12/2014 04:16 PM Subject:[cross-project-issues-dev] Creating a new category in the simrel update site: Tracing Sent by:cross-project-issues-dev-boun...@eclipse.org Hi, We would like to add a new category to the simultaneous release update site called Tracing. It is my understanding that adding such a category needs to be discussed and approved first. We would like to add this category because some features do not fit well into existing categories such as LTTng trace analysis, GDB trace and Pcap analysis. Those features are being moved from the Linux Tools project to the Trace Compass project. We also don't think a Trace Compass category would be good because the categories should be seen as themes to the user and not project structure. Also, we think other features could be placed under the Tracing category, like SystemTap support. Let us know what you think! Regards, Marc-Andre Laperle___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Creating a new category in the simrel update site: Tracing
I opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=451241 Regards, Marc-Andre From: cross-project-issues-dev-boun...@eclipse.org [cross-project-issues-dev-boun...@eclipse.org] on behalf of David M Williams [david_willi...@us.ibm.com] Sent: Wednesday, 12 November 2014 5:58 PM To: Cross project issues Subject: Re: [cross-project-issues-dev] Creating a new category in the simrel update site: Tracing Seems reasonable ... I wonder if it can be broadened a little to include Testing? But, in any case, please open a cross-project bug, and after a few weeks of discussion we can probably come to a conclusion. (That is, not in time for M3, but in time for M4). Thanks for suggestions to improve the categorization. From:Marc-André Laperle marc-andre.lape...@ericsson.com To:cross-project-issues-dev@eclipse.org cross-project-issues-dev@eclipse.org, Date:11/12/2014 04:16 PM Subject:[cross-project-issues-dev] Creating a new category in the simrelupdate site: Tracing Sent by:cross-project-issues-dev-boun...@eclipse.org Hi, We would like to add a new category to the simultaneous release update site called Tracing. It is my understanding that adding such a category needs to be discussed and approved first. We would like to add this category because some features do not fit well into existing categories such as LTTng trace analysis, GDB trace and Pcap analysis. Those features are being moved from the Linux Tools project to the Trace Compass project. We also don't think a Trace Compass category would be good because the categories should be seen as themes to the user and not project structure. Also, we think other features could be placed under the Tracing category, like SystemTap support. Let us know what you think! Regards, Marc-Andre Laperle___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
