[
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
|
Nitin,
The platform's
https://download.eclipse.org/eclipse/updates/4.24-I-builds/ is
like this:
<?xml version='1.0' encoding='UTF-8'?>
<?compositeMetadataRepository version='1.0.0'?>
<repository name='The Eclipse Project repository'
type='org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepository'
version='1.0.0'>
<properties size='3'>
<property name='p2.timestamp' value='1654000208596'/>
<property name='p2.compressed' value='true'/>
<property name='p2.atomic.composite.loading'
value='true'/>
</properties>
<children size='7'>
<child location='categories'/>
<child location='I20220528-1800'/>
<child location='I20220529-0600'/>
<child location='I20220529-1800'/>
<child location='I20220530-0600'/>
<child location='I20220530-1800'/>
<child location='I20220531-0600'/>
</children>
</repository>
What's the benefit of that?
I don't think there's a big benefit to such a composite; I think
someone once said that this way you can roll back and update...
And sometime people specify very exact versions in their *.target
too.
In any case, it's just always been done this way, and likely if
we changed it we'd find out what assumptions are broken by
changing it...
On 31.05.2022 18:40, Nitin Dahyabhai
wrote:
Is there a benefit to having a composite of more
than one milestone, or one build for that matter?
--
Regards,
Nitin Dahyabhai
Eclipse WTP PMC
_______________________________________________
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