HiEclipse Scout will be jumping on the release by Neon M4. We will activating the scout.b3aggrcon file then. scout-rap.b3aggrcon will be deleted as we do not deliver a rap ui anymore.
Greetings Stephan -- Scout Release Engineer, Senior Software Architect **BSI** **Business Systems Integration AG** Täfernstrasse 16a, CH-5405 Baden *T* +41 56 484 19 47 *M* +41 78 728 25 05 www.bsi-software.com **Neue Adresse ab 1.12.2015:** Täfernweg 1, CH-5405 Baden On 22 Oct 2015, at 15:45, David M Williams wrote:
For the record, the aggregation build is now running "clean", with only LDT and BIRT (still) disabled and a MAT feature disabled, since it dependson BIRT.I know BIRT being disabled will effect EPP packages for M3, so I hope itcan be fixed soon. In addition, there are three other files with disabled features orrepositories -- I assume disabled by the project's themselves, at least Idon't recall doing it. objectteams.b3aggrcon - org.eclipse.simrel.build scout-rap.b3aggrcon - org.eclipse.simrel.build scout.b3aggrcon - org.eclipse.simrel.buildFor all cases, please let us know why disabled (no longer participating?)and when you expect to have "fixed". As always, feel free to ask if questions or issues. From: Greg Watson <[email protected]> To: Cross project issues <[email protected]>, Date: 10/21/2015 10:40 AMSubject: Re: [cross-project-issues-dev] Next turn of the crank ...runtime compatibility bundle Sent by: [email protected] I thought I’d fixed PTP already, but I’ll check again. GregOn Oct 21, 2015, at 9:52 AM, David M Williams <[email protected]>wrote:Since no response from Birt, I have disabled BIRT from the aggregation,for now (which required me to also disable MAT chart feature, for now,since depends on BIRT) so that we can see who else might still depend oncompatibility bundle. According to my local builds, I think PTP does? If so, please correct soon, please ... I'd like to know if there's any more, after that is fixed? Thanks! From: David M Williams/Raleigh/IBM@IBMUSTo: Cross project issues <[email protected]>,Date: 10/20/2015 03:02 PMSubject: Re: [cross-project-issues-dev] ... runtime compatibilitybundle ... and LDT ... and Neon M3 Sent by: [email protected]OK, ready to try again? Since the LDT contribution has not changed, I have disabled it from the aggregation build, so that we can see who else stillrefers to the defunct compatibility runtime bundle.According to my local builds, BIRT will be the next project to fail ...now that DTP has been fixed (thanks Konstantin, and others). [CorrectionPlease correct any failures as soon as possible. That is, don't wait until your +N day. You can always contribute your final content later, but build"breaks" should be corrected right away.Same goes for you, LDT team, though I know your "break" isn't obvious, and realize you have some "redesign" work to do to figure out how to deliver"just your code" (and not all dependencies too). Thanks all, From: David M Williams/Raleigh/IBM@IBMUSTo: Cross project issues <[email protected]>,Date: 09/30/2015 11:04 AM Subject: Re: [cross-project-issues-dev] DTP for Neon stream ... runtime.compatibility ... and LDT? ... and Neon M2 Sent by: [email protected] OK, I give up.It appears some projects are not going to be able to react to the removalof runtime.compatibility bundle, for M2, so I have re-enabled the LDT contribution. (Bug 478009 and Bug 478330). This will allow the aggregation build, at least, to complete, so that others can make progress.This won't help projects who have a direct dependancy on, say, DTP (which in turn as a dependency on runtime compatibility bundle) since they dependon it, but do not provide it.For those people, the only work around I know of is to "include" only thatbundle from our M1 repository, or something similar.Less that ideal, but I'd like to push forward and see if we can get outsome form of M2 that can be used to create a cleaner M3!Let me know if suggestions or alternative approaches. (And, FYI, it doesnot appear that extending the deadline a few days will help with theruntime compatibility issue, but, if anyone has been blocked due to thisissue, and needs a few days to work around the problem, I think itreasonable to consider an extension of a few days ... if you make such a request, please be specific ... I'd hate to extend it to Monday instead ofFriday (let's say) and then that still not be enough time.) Thanks, From: David M Williams/Raleigh/IBM@IBMUSTo: Cross project issues <[email protected]>,Date: 09/28/2015 08:47 PM Subject: Re: [cross-project-issues-dev] DTP for Neon stream ... runtime.compatibility ... and LDT? ... and Neon M2 Sent by: [email protected]I hope everyone remembers that Neon M2 is this Friday ... and that meansyour Neon M2 contributions must be done by Wednesday. AND .. it seems, some have not yet reacted to the platform removing org.eclipse. runtime.compatibility bundle (Bug 394739). AND .. some have been "getting it automatically" from the current Sim.Release contributions, because Lua Development Tools (LDT) duplicates it(and many others) in their repository (Bug 478009).Since LDT has not updated their repo yet for Neon, I fear some may have ofa false sense that "everything is ok". Put more bluntly, we all know, some projects do not build against the latest version of their pre-reqs! And, we all know that some projects won't react until "the build fails".Therefore ... I am about to make the build fail for others, by removingLDT's massive contribution.If someone has a better suggestion, that would be good to hear, but I hope I am doing everyone a favor, by making the problem more apparent in theaggregation build. (And, greatest thanks to those of you who HAVE reacted to this change already ... thanks to all your release engineers!) Thank to you all, From: David M Williams/Raleigh/IBM@IBMUSTo: Cross project issues <[email protected]>,Date: 09/21/2015 08:09 PMSubject: Re: [cross-project-issues-dev] DTP for Neon stream ... andLDT? Sent by: [email protected]A question regarding the aggregation build. I thought it was designed to catch issues like this, but I don’t see any failures onHudson. I was wondering that too. :) So ... I looked in the log, at https://hudson.eclipse.org/simrel/job/simrel.neon.runaggregator.BUILD__CLEAN/111/consoleFull and could see - mirroring artifact osgi.bundle,org.eclipse.core.runtime.compatibility,3.2.300.v20150423-0821 and then searching backwards in log, for "Mirroring artifacts from", could see that the LDT project is (also) contributing that bundle, via their repository at .../download.eclipse.org/ldt/releases/stable/1.3I hope that is a temporary condition, since (in this case) do not thinkthe Platform would like others"extending the life" of something they are trying to end. But ... I am notsure. I think the next stepis to hear from the LDT project. I have opened bug 478009 for this issue.I did also use b3 aggregator editor to search for others who might be contributing that bundle, and it appears there are no others. (And, appears that LDT contributes much more potentially problematic bundles, than just that one, since they duplicate a great deal of other's projects, for their "Eclipse product"). _______________________________________________ cross-project-issues-dev mailing list [email protected]To change your delivery options, retrieve your password, or unsubscribefrom this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev _______________________________________________ cross-project-issues-dev mailing list [email protected]To change your delivery options, retrieve your password, or unsubscribefrom this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev _______________________________________________ cross-project-issues-dev mailing list [email protected]To change your delivery options, retrieve your password, or unsubscribefrom this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev _______________________________________________ cross-project-issues-dev mailing list [email protected]To change your delivery options, retrieve your password, or unsubscribefrom this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev _______________________________________________ cross-project-issues-dev mailing list [email protected]To change your delivery options, retrieve your password, or unsubscribefrom this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev _______________________________________________ cross-project-issues-dev mailing list [email protected]To change your delivery options, retrieve your password, or unsubscribefrom this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev _______________________________________________ cross-project-issues-dev mailing list [email protected]To change your delivery options, retrieve your password, or unsubscribe from this list, visithttps://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ cross-project-issues-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
