i can find only this one: https://ci.eclipse.org/simrel/job/simrel.runaggregator.pipeline/lastSuccessfulBuild/artifact/target/repository/final/buildInfo/reporeports/index.html
Am 06.08.19 um 09:09 schrieb Alexander Nyßen: > Well, it reported which plugins were provided in multiple versions. > This way we could check that only one Guava version was able to > satisfy all dependencies. > > Cheers > Alexander > > >> Am 06.08.2019 um 09:08 schrieb Christian Dietrich >> <christian.dietr...@itemis.de <mailto:christian.dietr...@itemis.de>>: >> >> this wont help if its not a explicit singleton but a implicit one >> only (classloaders are not completely isolated) >> >> Am 06.08.19 um 09:07 schrieb Alexander Nyßen: >>> I remember we had a simrel report pointing out such duplicate >>> singletons in the repo. Is that no longer available? >>> >>> Cheers, >>> Alexander >>> >>>> Am 06.08.2019 um 09:04 schrieb Christian Dietrich >>>> <christian.dietr...@itemis.de <mailto:christian.dietr...@itemis.de>>: >>>> >>>> i used that product and it actually found 2 more problematic candidates >>>> >>>> gef dot - regarding guava >>>> and mylyn trac regarding gson >>>> >>>> Am 06.08.19 um 08:59 schrieb Ed Willink: >>>>> >>>>> Hi >>>>> >>>>> The OOMPH integration is unlikely to help; it checks installability. >>>>> >>>>> With a conflicting singleton such as Guava >>>>> - the 'left-hand' subsystem successfully installs using version X >>>>> - the 'right-hand' subsystem successfully installs using version Y >>>>> >>>>> At run-time, any class passed in the 'API' between left and right >>>>> subsystems gets a bad class version. This probably happens as an >>>>> integrating system's class loader must 'choose' whether it uses >>>>> 'left' or 'right' hand class versions. >>>>> >>>>> If the 'API' is clean enough, e.g. no Optional, it can work. >>>>> >>>>> Regards >>>>> >>>>> Ed Willink >>>>> >>>>> On 06/08/2019 07:43, Christian Dietrich wrote: >>>>>> @Michael do you mean this one (see screenshot) >>>>>> >>>>>> Am 05.08.19 um 20:51 schrieb Michael Keppler: >>>>>>> Am 05.08.2019 um 17:43 schrieb Ed Willink: >>>>>>>> But no. Sorry deep integrators must suffer. >>>>>>> Unfortunately there is no cross-project integration testing. But I >>>>>>> vaguely remember Eike or Ed has shown an Oomph setup called "egg-laying >>>>>>> wool-milk-pig" containing everything from a release train at one of the >>>>>>> early Oomph presentations. Maybe one could do at least some manual >>>>>>> integration testing using that Oomph setup? However, I don't find any >>>>>>> link to that anymore. >>>>>>> >>>>>>> Ciao, Michael >>>>>>> >>>>>>> _______________________________________________ >>>>>>> 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://www.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://www.eclipse.org/mailman/listinfo/cross-project-issues-dev >>>>> >>>>> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> >>>>> Virus-free. www.avast.com >>>>> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> >>>>> >>>>> >>>>> <x-msg://16/#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> >>>>> >>>>> _______________________________________________ >>>>> 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://www.eclipse.org/mailman/listinfo/cross-project-issues-dev >>>> _______________________________________________ >>>> cross-project-issues-dev mailing list >>>> cross-project-issues-dev@eclipse.org >>>> <mailto:cross-project-issues-dev@eclipse.org> >>>> To change your delivery options, retrieve your password, or >>>> unsubscribe from this list, visit >>>> https://www.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://www.eclipse.org/mailman/listinfo/cross-project-issues-dev >> _______________________________________________ >> cross-project-issues-dev mailing list >> cross-project-issues-dev@eclipse.org >> <mailto:cross-project-issues-dev@eclipse.org> >> To change your delivery options, retrieve your password, or >> unsubscribe from this list, visit >> https://www.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://www.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://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
