Community
Participate
Working Groups
During the fix of bug 339692 I tried to add the Jetty milestone repository: http://download.eclipse.org/jetty/updates/jetty-rt-3.7milestones But when using this repository the build fails with this problem: [INFO] [Software being installed: org.eclipse.rtp.package.web.feature.feature.group 0.1.0.qualifier, Missing requirement: org.eclipse.rtp.package.web.feature.feature.group 0.1.0.qualifier requires 'org.eclipse.jetty.all.dependencies.feature.group 0.0.0' but it could not be found]
The jetty M6 build is not ready.
It is ready now.
Are you building with the latest and greatest from a bunch of milestone repositories *or* are you using /releases/staging (or /releases/indigo) as input? In EPP we decided against the former approach and are using the simultaneous release train repository /releases/staging only since project specific repositories tend to be a bit unreliable.
Thanks for raising this point Markus. We are currently building against jetty's, eclipse-platform's and orbit's milestones repositories. The eclipse-platform build is very reliable (thanks Kim!) and we have an insider for the jetty repository (myself ;)). I think it is a requirement to build against those: RTP does generate a p2 repository. I believe it is contributed to Indigo's aggregated repo. In this situation it is a circular circular dependency to build RTP against a set of bundles itself contributed in a previous aggregated build. Maybe I am missing a requirement for EPP: my guess was that RTP was just like eclipse-WTP regarding EPP: eclipse-WTP builds its repo. It is contributed to the staged build. EPP builds the WTP packages pointing at the aggregated staged repo.
I think also it's a good idea to build against the milestone repositories because of this circular dependency issue. Anyway, for Indigo this doesn't matter because we are NOT contributing to the aggregate repo. But for future release trains we will contribute.