Contrary to its name, the http://findbugs.cs.umd.edu/eclipse-daily/ update site still contains version 3.0.0.20140706-2cfb468 of the FindBugs feature, which is a pity as I would very much like to try out the Quick Fix extension point of the FindBugs Eclipse plugin.
@Bill: looks like the update site stopped to build with commit http://code.google.com/p/findbugs/source/detail?r=cce19ace999f33b53468945203cc7d09c23f5127 which switched FB to 3.0.1 development, because the last working commit was http://code.google.com/p/findbugs/source/detail?r=2cfb4688d8676d34fee0e6f153a6a53354ff2e20 on 3.0.0 "release".
Can you please check why the build is broken (I guess some flag or version increment somewhere in your scripts is needed)?
Regards,
Andrey
FWIW, my local build of the
masterbranch failed withBumping the version in
eclipsePlugin/META-INF/MANIFEST.MFfixed things.Yep, I will fix that ASAP, thanks!
@Bill: unfortunately the daily build silently fails - it would be nice if it could send a mail to the dev team.
Great. Thank you.
Right now I have to work with a locally built and converted update site anyway (because of [bugs:#1301]), so there's no rush. But maybe I'll have some time over the weekend to send you guys a patch for [bugs:#1301]; then the eclipse-daily update site becomes interesting for me again.
Related
Bugs:
#1301Bill, the local build works but the daily update site still shows old version. Can you please check what could be wrong?
Thanks
Andrey
The way the update site is deployed is now changed, see https://sourceforge.net/p/findbugs/bugs/1301/
Bill, can you please check this issue? It would be really great to have nightly build running again.
Regards,
Andrey
Bill,
any update on this? It would be really handy to verify fixes made for RC1.
Otherwise I have to build FB by myself each day and this is definitely not what I can do.
Regards,
Andrey
I agree that daily builds should be fixed, but manual build procedure is not so hard. I simply run ant in findbugs/findbugs directory to build findbugs.jar, then run ant in findbugs/eclipsePlugin directory. After that I update the Eclipse using local folder findbugs/eclipsePlugin/bin_build/site/eclipse-daily as update site. This usually works and doesn't take much time.
Yes, that is not too much work when testing with your local Eclipse installation only. It is, however, more awkward to do during an automated CI job. IMHO, the CI job should simply be able to consume the daily update site rather than having to build it from scratch; builds take long enough already, without everyone re-building FindBugs.
Interesting, looking at http://findbugs.cs.umd.edu/eclipse-daily/site.xml I see that the build works again. Thanks Bill (or whoever did something)!
@Tagir: Sure I can build FB but I need time for this. I'm so busy right now with Eclipse & Egit patches that I have no time at all to do anything else.
Seems that update site is working properly now (at least it was updating three days in a row). Closing this issue.