| Summary: | Durable build | ||
|---|---|---|---|
| Product: | [RT] Jetty | Reporter: | Greg Wilkins <gregw> |
| Component: | build | Assignee: | Jesse McConnell <jesse.mcconnell> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | CC: | jesse.mcconnell, jetty-inbox |
| Version: | 7.1.5 | ||
| Target Milestone: | 7.1.x | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Greg Wilkins
I have uploaded the Orbit jars to http://download.eclipse.org/jetty/orbit/ and modified the jetty-distribution pom to use that as the source of the orbit jars. The jetty-osgi pom needs to be similarly updated and ideally a common place for the version properties to be set created (is it possible to get properties just by depending on the pom of another module?). jetty-distribution committed r2230 hugues, can you look at updating osgi? (In reply to comment #2) > jetty-distribution committed r2230 > > hugues, can you look at updating osgi? In my understanding, it is not possible to use those jars in the osgi's build. The OSGi build is specifically made to contribute jetty to the eclipse aggregated repository. It is required that all its dependencies are loaded from the other p2 repositories that are also contributed to that same aggregated build. In our case, all our dependencies are located in the orbit repository and in the eclipse-platform repository. Each time one of these change their contribution to the aggregated build, we need to re-run our build to use the jars provided there. I think greg is referring to the jetty-osgi goop in trunk, not the stuff under eclipse your not rerunning trunk builds when you have to regen things, just the eclipse side afaik so we ought to be able to make jetty-osgi bits pull with ant same as before this is the non-tycho builds...jetty/trunk/jetty-osgi Understood, I had forgotten that to run the pax tests, we had to mimick a distribution. Updating the test-osgi pom.xml and runnin the tests at the moment. Done with commit 2234. Re-assigning to Greg as the jetty-osgi part is done. Assign to jesse to check what has been done and close issue if all is OK I am happy with what I have seen regarding this. |