Is it possible to name repositories?

[ViToni]

My setup includes some extensions with their respective repositories. These repositories are later also found under "Available Software Sites". However I can see only the location without any names.
I'm wondering if it's possible to also add something more telling as name to the location (looking at

oomph/plugins/org.eclipse.oomph.p2/model/P2.ecore

Lines 90 to 100 in a1f5605

	<eClassifiers xsi:type="ecore:EClass" name="Repository" eSuperTypes="../../org.eclipse.oomph.base/model/Base.ecore#//ModelElement">
	<eStructuralFeatures xsi:type="ecore:EAttribute" name="uRL" lowerBound="1" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EString">
	<eAnnotations source="http:///org/eclipse/emf/ecore/util/ExtendedMetaData">
	<details key="kind" value="attribute"/>
	<details key="name" value="url"/>
	</eAnnotations>
	<eAnnotations source="http://www.eclipse.org/oomph/setup/Redirect"/>
	</eStructuralFeatures>
	<eStructuralFeatures xsi:type="ecore:EAttribute" name="type" lowerBound="1" eType="#//RepositoryType"
	defaultValueLiteral="Combined"/>
	</eClassifiers>

(if it's the proper place to look for) does not show any more attributes of the repository element)).

If having names for locations would be an worthwhile feature, maybe instead of extending the repository element, the repository could inherit the label of the parent setupTask?

[merks]

I'm not sure how "implementable" this would be. We even try to remove the repositories that we use during a "transaction":

oomph/plugins/org.eclipse.oomph.p2.core/src/org/eclipse/oomph/p2/internal/core/ProfileTransactionImpl.java

Line 961 in 1bced3d

metadataRepositoryManager.removeRepository(uri);

But p2 often adds repositories that we (Oomph) really don't want added. E.g., p2 will typically add repository references that are contained in other repositories.

Also repositories themselves have names:

So one might hope that p2 will generally use the name that the repository specifies as its name.

So while providing a name seems useful, how that can be implemented within the actual p2 engine is not entire clear nor how that interacts with other things that engine is doing, e.g., touchpoints that add named repositories.

E.g., products can specify names.

And so can touchpoint instructions:

addRepository(type:0,location:https${#58}//download.eclipse.org/eclipse/updates/4.36,name:The Eclipse Project Updates,enabled:true);

In other words, implementing such a thing would require some deep exploration of the bowels of p2...

[ViToni]

Thanks, Ed.

Implementing such a tiny detail might be not worth the hassle after what I think I understood from your explanation.

Many thanks for this great piece of software! It helps tremendously with our standardized setup.