Re: [egit-dev] Calling Tycho / Maven Ninjas

[Matthias Sohn <matthias.sohn@xxxxxxxxxxxxxx>]

2010/1/22 Shawn O. Pearce <spearce@xxxxxxxxxxx>

Chris Aniszczyk <zx@xxxxxxxxxxxxxxxxx> wrote:
> The only problem I left to see is the need to have two sites for
> installation. This is easily solved in p2 with composite repositories
> but I don't think we have that option. I think we should just bundle
> JGit with EGit when producing the update site (p2 repo). Anyone
> against this (I believe Matthias had this intention earlier)? EGit has
> to be dead easy to install.

Agreed, bundle JGit feature and plugins in the EGit P2 repository.

I'll look into that.

 

> I'm also bothered with the org.eclipse.jgit bundle being generated
> with out a replaced .qualifier

WTF.  I think this is happening because Robin backed out the use
of the bundle plugin in Maven.  So the MANIFEST.MF is being used
essentially as-is by the JAR task.

We need to modify our Maven build process to edit the MANIFEST.MF
files then.

Any hints how this editing could be done ? I looked around a while but
didn't find any matching Maven trick yet.
 

> Also, anyone against these URLs for updates?
>
> p2 repo - http://www.eclipse.org/jgit/updates
> mvn repo - http://www.eclipse.org/jgit/updates/mvn

For the JGit Maven repository I would probably prefer
http://www.eclipse.org/jgit/maven

I would prefer this one
 

Or at least spell it out:
http://www.eclipse.org/jgit/updates/maven

 

--
Matthias