[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [egit-dev] Tycho Build for EGit
|
I spent some time last time on this and almost got it working, but there
is one interesting problem with egit unit tests that I need some help with.
Egit unit tests use ConnectProviderOperation, which expects to find
single git repository, but finds two. Following maven convention, Tycho
keeps all project build state, including test workspace, under
project/target folder. This results in the following directory structure
on filesystem. So ConnectProviderOperation sees both test git repo and
actual egit repo and fails.
parallelip-egit <= egit source tree root
/.git
/org.eclipse.egit.core.test
/target
/work
/data <= test workspace
/.git
/.metadata
/Project-1
I am planning to refactor ConnectProviderOperation to accept specific
git repository location, but would like to hear what people more
familiar with egit think about this.
--
Regards,
Igor
Chris Aniszczyk wrote:
On Sun, Nov 29, 2009 at 6:58 AM, Robin Rosenberg
<robin.rosenberg@xxxxxxxxxx> wrote:
Take a look at META-INF/MANIFEST.MF. It declares the dependencies. I assume
Tycho does something like the PDE build does, which is what I have used to
build our plugin so far. No pom.xml (i.e. duplicate meta data) needed.
I've been experimenting with a JGit Tycho build locally and having some issues.
I'm in favor of using a Tycho based build if it works in a manifest
first fashion as that's what's used at runtime anyway :) I've been
putting Tycho through the ringer locally with the basic RCP mail
example and some other projects I have.
Jason and co, if you have a build already feel free to send it my way
so I can it locally. Once I'm convinced things work, I'll initiate the
process on getting Tycho installed on build.eclipse.org and make sure
it works from there within Hudson.
Cheers,
