Community
Participate
Working Groups
As per http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg07400.html
Johannes, maybe you also know how to fix this?
Hi, I may have a look. I know that a lot of projects use https://wiki.eclipse.org/WTP/Releng/Tools/addRepoProperties for this. But as this needs the information where the update site is uploaded to, I have to check how to integrate it with the current build/build jobs
Moving to 2.2.0
Moving to next release. Johannes, can you work on this?
Will do
Moving to 2.4.0. Johannes?
Yes, but today I finally found some time to work on this. I have a first isolated draft that takes an existing p2 repository and creates a new repository including the p2.mirrorURL: https://github.com/jfaltermeier/nebula/commit/4fc44fa8c4461ff29a204f74e11c94b2fda1d75a This could run as part of the release job: 1. "Mirror" the p2 repository to publish 2. add p2 mirrorURL and recreate p2 repository 3. upload this new repository We could also change the regular build to (optionally) add the mirror urls. However this way one has to know that this build will be uploaded and where it will be uploaded to, so that the correct metadata is added. Having wrong mirrorURLs is worse than having none at all as far as I know. --- Problem with the approach on above branch is, that the category.xml is copied and the urls for the target platform as well. So this should be more closely aligned to the actual build to avoid overhead on release day.
(In reply to Johannes Faltermeier from comment #7) Thanks, Johannes, is this something we can take into the release?
Moved to Github; https://github.com/eclipse/nebula/issues/350