Re: [egit-dev] Workspace setput problem with Indigo / Jetty

[Matthias Sohn <matthias.sohn@xxxxxxxxxxxxxx>]

2011/9/19 Hugues Malphettes <hmalphettes@xxxxxxxxxxx>

Hi Jens and Mathias.

I was hoping to reproduce the issue (and find a solution :) ). But it
does not happen for me.

Sorry this might be turning into the debug of the development setup for jgit.
I unzipped a fresh install of Eclipse-PDE-Indigo from last June.

I followed the steps
http://wiki.eclipse.org/EGit/Contributor_Guide#Development_IDE_Configuration
with one difference: I installed jetty directly from the Indigo
repository: "Jetty Target Components 7.4.2".

Then I imported all the jgit projects. There is no compilation issue.
Well, I did fight with org.hamcrest and ended-up adding
Require-Bundle: org.hamcrest.core
to the org.eclipse.jgit.test's MANIFEST.MF to solve the compilation
errors in org.eclipse.jgit.diff.

thanks for this hint, I will fix this dependency 

I am on IRC at freenode on the #jetty channel if someone wants to debug it live.

After a restart of Eclipse my compile errors are gone so I probably had an inconsistent build. 

So I can confirm that using Jetty 7.4.2 from Indigo p2 repository successfully compiles

all jgit bundles and tests. 

But when trying to run the JGit HTTP tests 

           org.eclipse.jgit.http.test/org.eclipse.jgit.http--All-Tests.launch

the tests always hang on the second test case not regarding which tests

I select to be run as JUnit tests. 

If I run the tests one by one they all succeed but I can't run all of them in a sequence. 

This used to work previously. Looks like test teardown doesn't work anymore as expected. 

The Jetty server used in the tests is started/stoppped in HttpTestCase.setup() 

and HttpTestCase.teardown().

-- 
Matthias