Sonatype Nexus provides the capability to group different repositories into a so-called group repository. So for maintenance, the content is still nicely separated into different repositories, but for consumption via Maven, only one URL to the group repository needs to be specified. This is especially useful when using authorization for reading from repositories since only one "" entry is then needed in the Maven settings.xml instead of one for each repository.
Something like that would be nice for at least p2 repositories in Package Drone. One could then host different frameworks like Eclipse Platform SDK, Eclipse Birt SDK, Eclipse DTP SDK, Google Guava, etc. in individual channels for easier maintenance, but still consume everything or any kind of subset via additionally configured group channels while specifying credentials in the settings.xml only once.
In p2 there is already a concept for that, called "composite repositories". Maybe this can be integrated somehow into Package Drone?
Hello everybody,
Sonatype Nexus provides the capability to group different repositories into a so-called group repository. So for maintenance, the content is still nicely separated into different repositories, but for consumption via Maven, only one URL to the group repository needs to be specified. This is especially useful when using authorization for reading from repositories since only one "" entry is then needed in the Maven settings.xml instead of one for each repository.
Something like that would be nice for at least p2 repositories in Package Drone. One could then host different frameworks like Eclipse Platform SDK, Eclipse Birt SDK, Eclipse DTP SDK, Google Guava, etc. in individual channels for easier maintenance, but still consume everything or any kind of subset via additionally configured group channels while specifying credentials in the settings.xml only once.
In p2 there is already a concept for that, called "composite repositories". Maybe this can be integrated somehow into Package Drone?