Jonah,
Note that the generated catalogs also don't use the composite
<?xml version="1.0" encoding="UTF-8"?>
<xmi:XMI xmi:version="2.0"
xmlns:xmi="http://www.omg.org/XMI";
xmlns:p2="http://www.eclipse.org/oomph/p2/1.0";>
<p2:Repository
url="https://download.eclipse.org/technology/epp/packages/2022-06/202205261200"/>
<p2:Repository
url="https://download.eclipse.org/releases/2022-06/202205271000";>
<annotation
source="http://www.eclipse.org/oomph/setup/ReleaseTrain"/>
</p2:Repository>
</xmi:XMI>
You can imagine that when using the ongoing development stream, needing
to do a rollback to undo some bad update might be a significant concern;
garbage collection will quickly deletes unused artifacts (except if
you're using a shared bundle pool).
On 31.05.2022 19:22, Jonah Graham wrote:
HI Nitin,
That is a question I have asked multiple times - I personally find it
problematic having multiple milestones in one composite because it
doesn't reveal problems until the release and slows down p2 resolution.
The last time this came up [1] I added a FAQ to simrel doc [2] -
please let me know if that answers the question.
Anyway, this is why I now avoid using the composite in most cases,
particularly the update from the last version test that is part of the
EPP release procedures[3].
[1] https://www.eclipse.org/lists/cross-project-issues-dev/msg17236.html
[2]
https://wiki.eclipse.org/SimRel/Simultaneous_Release_Cycle_FAQ#Why_do_we_use_composites_anyway.2C_if_there_are_potential_problems_with_them.3F
[3] See "Upgrade from previous release works" in
https://git.eclipse.org/r/plugins/gitiles/epp/org.eclipse.epp.packages/+/refs/heads/master/RELEASING.md
HTH
Jonah
~~~
Jonah Graham
Kichwa Coders
www.kichwacoders.com <http://www.kichwacoders.com>
On Tue, 31 May 2022 at 12:40, Nitin Dahyabhai <thatnit...@gmail.com>
wrote:
Is there a benefit to having a composite of more than one
milestone, or one build for that matter?
On Tue, May 31, 2022 at 11:10 AM Ed Merks <ed.me...@gmail.com> wrote:
Lars,
That's to be expected for a composite that is composed of all the
milestones for 2022-06 so far...
The concern is about duplicates in a simple repository, e.g.,
https://download.eclipse.org/oomph/archive/reports/download.eclipse.org/releases/2022-06/https___download.eclipse.org_releases_2022-06_202205271000.html
On 31.05.2022 16:59, Lars Vogel wrote:
> Hi,
>
> 2022-06 contains multiple versions of the Eclipse platform
SDK, see
>
https://github.com/eclipse-platform/eclipse.platform.releng/issues/32
> for a screenshot.
>
> The Eclipse TLP only contributes one version so someone else
might
> contribute older versions.
>
> AFAIK the simrel is very concerned about multiple versions
of plug-ins
> therefore I post this info here.
>
> Best regards, Lars
>
>
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
--
Regards,
Nitin Dahyabhai
Eclipse WTP PMC
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To 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 unsubscribe from this list,
visithttps://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
