[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
[eclipse.org-architecture-council] [Bug 331385] New: Recommend / enforce p2 repository structure for projects
|
https://bugs.eclipse.org/bugs/show_bug.cgi?id=331385
Product/Component: Community / Architecture Council
Summary: Recommend / enforce p2 repository structure for
projects
Classification: Eclipse Foundation
Product: Community
Version: unspecified
Platform: PC
OS/Version: Mac OS X
Status: NEW
Severity: normal
Priority: P3
Component: Architecture Council
AssignedTo: eclipse.org-architecture-council@xxxxxxxxxxx
ReportedBy: pascal@xxxxxxxxxxxx
Pretty much every project now has its p2 repository. Still, from a consumer
point of view, it is quite often a jungle to figure out the repos targeted for
N, I, M and also maintenance streams.
I would like to explore the possibility of coming up with naming conventions
(in this case paths) for p2 repositories.
What do you think?
--
Configure bugmail: https://bugs.eclipse.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.