Community
Participate
Working Groups
The Jetty downloads page has "P2" entries for various 7.x builds but nothing for 8.0 or even 7.2.0.v20101020 which appears to be the latest thing?
http://dev.eclipse.org/mhonarc/lists/jetty-dev/msg00510.html From my understanding, the primary reason is that they are build manually by Hugues but they are working on some automation.
I have CQ's going through for jsp 2.2 support for jetty8, once those and the servlet 3.0 api jar we are using are through then we will get the p2 repo up and running for this. we have the whole signing process automated now so it shouldn't take long once we have the necessary things in orbit.
I have uploaded 8.0.0.M2 here: http://download.eclipse.org/jetty/updates/jetty-bundles-8.x/8.0.0.M2 It is lacking a hudson job for it. It is lacking the org.eclipse.jetty.osgi.* bundles. org.eclipse.jetty.osgi.boot should be back in 8.0.0.M3, jsp support requires some new CQs to be cleared out and some more work. bug 339973 keeps track of that.
hugues, I was looking at this issue and was about to request another build for it on hudson when I noticed that it now appears to be configured to run all the time and not just when we want to push out a new signed release.. I don't think we ought to be Fastlaning this build if its nightly as it appears to be now so, should we keep this build and spark off a couple more builds that we use for actually releasing 7 and 8 bundles?
Jesse, we discussed those changes here: http://dev.eclipse.org/mhonarc/lists/jetty-dev/msg00914.html and you ave me the green light one really late one evening. I think it is necessary to have the nightly execute on the build machine: The jetty nightly installs the jars on the local m2 repo. Then this builds picks them up from there and deploy the nightly onto downloads. I am not clear if that means it has to be "Fastlane" or not. Looking at what we do for eclipse-RTP I would say that if we could use profiles and parameters to run the various types of builds with less jobs that is probably best.
Hugues, do we need to do anything with this for 8.0.0 release?
I still have issues with the tycho signing plugin. I had done a snapshot release and was able to use it back in June. Now the maven config has been changed on hudson@eclipse and I don't have access to the snapshot build of the plugin that works. The released tycho signing plugin still does not work so far. But I did not take the time to find out why.
hugues, its working for other projects so perhaps the usage is just out of date.. which repo and pom is specifically having issues and I'll analyze tomorrow jesse
OK, I tried quite hard and got some md5 check sums when tycho used the produced repo. I can't find those stack traces so I'll try again. Is there a new RC on the 7.5 or 8.0 ?
7.5 rc2 should be in central soon if it isn't already
OK, built 7.5.0.RC2 with the new signing plugin. Then when I try to use it to build the eclipse web starter kit product: https://hudson.eclipse.org/hudson/view/Jetty-RT/job/jetty-rt-products/536/console Installation failed. An error occurred while collecting items to be installed session context was:(profile=EclipseRTWebStarterKit, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). Problems downloading artifact: osgi.bundle,org.eclipse.equinox.ds,1.3.1.R37x_v20110701. MD5 hash is not as expected. Expected: 3455470239dd140ea3695c48b5b6942d and found a3d2582b9db2d1fea32a6a9e2e555800. Problems downloading artifact: osgi.bundle,org.eclipse.equinox.p2.artifact.repository,1.1.101.R37x_v20110714. MD5 hash is not as expected. Expected: f621b97bf29ac9e858774ab35e09a2f3 and found e8673bc6ca1c42d0ec09bb2935a480a6. Problems downloading artifact: osgi.bundle,org.eclipse.equinox.p2.touchpoint.eclipse,2.1.1.R37x_v20110815-0935. MD5 hash is not as expected. Expected: d31144a9909242f0a068eb55c1a1daa9 and found ad14872ecea1a99e7971921d7b471747. Problems downloading artifact: osgi.bundle,org.eclipse.equinox.preferences,3.4.1.R37x_v20110725. MD5 hash is not as expected. Expected: 7b4ed2d511b7f42a0e2589088ae4f95e and found 89c96828e2cd773292eb3166b2a4ff11. Problems downloading artifact: osgi.bundle,org.eclipse.equinox.registry,3.5.101.R37x_v20110810-1611. MD5 hash is not as expected. Expected: ceec1e028aa3db40038d7239e6f5afaf and found dacb1b225099b6a5960dc9cf34859b22. Problems downloading artifact: osgi.bundle,org.eclipse.equinox.security,1.1.1.R37x_v20110822-1018. MD5 hash is not as expected. Expected: c6b0c4160d22c9441980a46476dc1b58 and found 3a07c4a4e813e75ceddaff8aaaa87426. Problems downloading artifact: org.eclipse.update.feature,org.eclipse.equinox.server.core,1.1.0.v20110502-7K7TFBYDzbeA3ypK_98cDL15A4A. MD5 hash is not as expected. Expected: 6e709d79b889e7092c48a5edbaf6af19 and found 7225065e18224d8cf4ee4017f792b19d. Problems downloading artifact: org.eclipse.update.feature,org.eclipse.equinox.server.p2,1.1.0.v20110502-7z7UFVwFS16XCje8f0_QUjX14C7G. MD5 hash is not as expected. Expected: a52a5702f5565775a64f619d9a234ea3 and found d9d8ee19182132654ddcc70384a89032. Problems downloading artifact: osgi.bundle,org.eclipse.osgi,3.7.1.R37x_v20110808-1106. MD5 hash is not as expected. Expected: 00dde65d75c57c118710f448b2dfcfe6 and found 618908f6b115ecf3177890e54632479c. Application failed, log file location: /opt/users/hudsonbuild/.m2/repository/org/sonatype/tycho/tycho-p2-runtime/0.9.1/eclipse/configuration/1314774269223.log
I have tested that the jetty-bundles repo is correct: p2 is able to mirror it. Using the mirror as a validation it has so far caught the checksum issues and other problems. Hence the problem is somewhere in the product build.
can you check out the latest product build on husdon?
err looking at all those bundles, we shouldn't be resigning or packing them, are they being excluded from that process?
(In reply to comment #14) > err > > looking at all those bundles, we shouldn't be resigning or packing them, are > they being excluded from that process? Which bundles exactly? I don't have the answer on the top of my head. It used to work.
8 should be good to go now http://download.eclipse.org/jetty/ we have 8 going nightly now, if there are any issues consuming that please open an issue for it and flag me down
