[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [cross-project-issues-dev] Multiple version of org.eclipse.sdk.feature.group in the 2022-06 simrel
|
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="" class="moz-txt-link-rfc2396E" href="https://download.eclipse.org/technology/epp/packages/2022-06/202205261200">"https://download.eclipse.org/technology/epp/packages/2022-06/202205261200"/>
<p2:Repository
url="" class="moz-txt-link-rfc2396E" href="https://download.eclipse.org/releases/2022-06/202205271000">"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].
HTH
Jonah
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev