Re: [jgit-dev] Is it actually possible to set up a new JGit developer en

["Lay, Stefan" <stefan.lay@xxxxxxx>]

Yes, the same steps work for me too.

Actually I had just described the complete setup for the eclipsecon
Tutorial last week[1]. Basically the steps were the same.
The only difference was that I already had the Execution Environments
installed in the IDE (so I don't need step 4.2) and that I described how
to use a local p2-repository. But with egit-4.3.target it also works.

There is also a target platform description in org.eclipse.jgit.target. A
drawback with using a target platform however is that it is only useful in
a tycho/osgi environment. If you want to build jgit for example together
with gerrit, you cannot use a target platform.

There was a change by Matthias where he proposed a p2f file for Jgit[2].
It was abandoned because of missing interest.

Another remark: I think in the contributor guide we should not tell people
to ignore missing API baselines but tell them to set such a baseline.

Stefan

[1]https://docs.google.com/document/d/10u_ZNQyjhRRo_ZpZ5ElUsYqt6QrozEXjdp5P
XRbXVYA/edit
[2]https://git.eclipse.org/r/#/c/11009/

On 25.03.14 22:51, "Robin Rosenberg" <robin.rosenberg@xxxxxxxxxx> wrote:

----- Ursprungligt meddelande -----
> Från: "Dave Borowitz" <dborowitz@xxxxxxxxxx>
> Till: "Tomasz Zarna" <tzarna@xxxxxxxxx>
> Kopia: "jgit-dev" <jgit-dev@xxxxxxxxxxx>
> Skickat: tisdag, 25 mar 2014 20:46:10
> Ämne: Re: [jgit-dev] Is it actually possible to set up a new JGit
>developer environment these days?
> 
> 
> 
> Well that's kind of my point, that setting up an environment from
>scratch is
> not a hermetic, reproducible process, and depends on whether you are
>lucky
> enough to have accumulated the right state in your IDE over the years to
> make things work.

Indeed, it's a mess and I've struggled with it too. Try this. If it works
for
someone else we might update the Wiki. It requires you to get the EGit
sources
since the platform definition is there.

1. Download eclipse Kepler SR1 (I suppose SR2 works too).
2. Unpack eclipse-kepler-SR1
3. Start your new Eclipse
4. Open Settings/Plug-in development/API Baselines.
4.1 Set the option for missing baseline to ignore.
4.2 Set Missing execution environment descriptions to Warning.
5. Clone JGit and EGit or import existing sources if you already have them
5. In package explorer: open egit-4.3.target in the
org.eclipse.egit.target project
5.1 Click on the link "set as target platform"
You're done.

-- robin

> On Mar 25, 2014 12:42 PM, "Tomasz Zarna" < tzarna@xxxxxxxxx > wrote:
> 
> 
> >> * in case a dependency is missing go to Orbit repo (CVS) and check it
>out
> > 
>http://wiki.eclipse.org/EGit/Contributor_Guide#Option_2:_Install_from_Orbi
>t_P2_Repository
> > lists 8 projects you would need to do this for, which is I guess maybe
>ok,
> > as long as we don't add new dependencies?
> 
> Maybe I'm just lucky, but currently I have no extra dependencies from
> Orbit and see no compile errors in the workspace.
> 
> On Tue, Mar 25, 2014 at 8:30 PM, Dave Borowitz < dborowitz@xxxxxxxxxx >
> wrote:
> > 
> > 
> > 
> > On Tue, Mar 25, 2014 at 12:25 PM, Tomasz Zarna < tzarna@xxxxxxxxx >
>wrote:
> >> 
> >> Hmm, from my recent experience setting up a JGit dev workspace isn't
>that
> >> hard:
> >> * clone the repo
> >> * import all the projects into eclipse
> > 
> > 
> > * ignore all errors about specific Maven features not being supported
>(e.g.
> > maven-antrun-plugin).
> > 
> >> * activate jgit-4.4.target
> >> * in case a dependency is missing go to Orbit repo (CVS) and check it
>out
> > 
> > 
> > 
>http://wiki.eclipse.org/EGit/Contributor_Guide#Option_2:_Install_from_Orbi
>t_P2_Repository
> > lists 8 projects you would need to do this for, which is I guess maybe
>ok,
> > as long as we don't add new dependencies? If you wanted to actually
>get the
> > versions JGit expects instead of whatever the latest R-build has, you
> > would,
> > what, inspect the .p2f file for the version it's expecting?
> > 
> > I'm liking Roberto's suggestion more and more...
> > 
> >> 
> >> * done!
> >> 
> >> Running a single test (case) is as easy as creating a JUnit launch
> >> config in Eclipse.
> > 
> > 
> > Yeah, pretty the only reason I want to use an IDE is because I already
>knew
> > this part was easy.
> > 
> >> 
> >> fwiw, I'm on Luna M6
> >> 
> >> Cheers,
> >> 
> >> On Tue, Mar 25, 2014 at 7:17 PM, Dave Borowitz < dborowitz@xxxxxxxxxx
>>
> >> wrote:
> >> > The contributor guide is...disheartening.
> >> > 
> >> > "Note: Eclipse Kepler currently has a bug (see bug 409073) which
>causes
> >> > the
> >> > instructions below to fail. You can manually install the tools (e.g.
> >> > from
> >> > the marketplace)"
> >> > 
> >> > Really? No thank you. Ok, so maybe I just won't use Eclipse.
> >> > 
> >> > First things first, alias mvn='JAVA_HOME=/path/to/jdk6 mvn', because
> >> > some
> >> > java7 bug in plexus-io or something makes maven-source-plugin take
> >> > literally
> >> > hours on my laptop.
> >> > 
> >> > So mvn package at least works now, except that we have a lot of
>tests
> >> > (which
> >> > is good!) so it takes a long time.
> >> > 
> >> > Now, can I run a specific test case? Like, the one corresponding to
>the
> >> > bugfix I'm working on?
> >> > 
> >> > Google tells me this would be 'mvn test -Dtest=MyTest', but no,
> >> > maven-surefire-plugin says no tests are found. Something must be
>busted
> >> > because -Dtest is supposed to support wildcards and 'mvn test
>-Dtest=*'
> >> > gives me the same error. Perhaps 'mvn -pl org.eclipse.jgit.test test
> >> > -Dttest', but then it expects all the other modules to be installed
>in
> >> > my
> >> > local repo. Again, no thank you.
> >> > 
> >> > I have a theory that everybody who actively develops JGit is using
>an
> >> > Eclipse project they set up >1 year ago after hours of manual
>labor, and
> >> > we'd each be screwed if that project ever got lost. Which is pretty
>much
> >> > what happened to me here :)
> >> > 
> >> > https://git.eclipse.org/r/17955 can't get merged fast enough IMHO.
>(Wish
> >> > I
> >> > had more time to help.)
> >> > 
> >> > _______________________________________________
> >> > jgit-dev mailing list
> >> > jgit-dev@xxxxxxxxxxx
> >> > https://dev.eclipse.org/mailman/listinfo/jgit-dev
> >> > 
> > 
> > 
> 
> _______________________________________________
> jgit-dev mailing list
> jgit-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/jgit-dev
> 
_______________________________________________
jgit-dev mailing list
jgit-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jgit-dev