Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [dash-dev] maven.eclipse.org

2013/1/31 Andrew Ross <andrew.ross@xxxxxxxxxxx>
On 01/31/2013 11:41 AM, Matthias Sohn wrote:
2013/1/31 Thanh Ha <thanh.ha@xxxxxxxxxxx>
Hi Everyone,

Per Bug 394792 I'm looking at moving maven.eclipse.org to become a managed service at Eclipse. I plan on tackling this issue soon and was wondering if taking this server down would affect any projects?

the EGit project is downloading the eclipse-signing-maven-plugin from maven.eclipse.org. So if you take down this system
signing of our builds on Hudson would fail, this could be solved if you can serve this plugin from a different place.

--
Matthias  

Thanks Matthias, "CBI stuff" is first on the list. We'll get it served from the new instance and swap some of the builds using it to test.

Speaking of EGit, I'm wondering... is there any value in EGit pulling JGit from Nexus rather than ../JGit?

I think this could help to integrate a couple of system calls we implemented using JNI [1-3]
which could help to speedup JGit by making some low level file system calls accessible from
Java. So far we didn't integrate that due to the unsolved problem how to integrate the results of
these native makes into JGit's maven build. Nexus could be used to store results of the native
makes and the JGit Tycho-based packaging build could consume them from there.

Until Tycho and Maven builds can be mixed in the same reactor JGit will still need 2 runs of Maven:
- first Maven build to create the libraries exposed as Maven artifacts (containing OSGi manifests) since most
  JGit consumers are non-OSGi, releases of these are published via Sonatype OSS to Maven central
- packaging build using Tycho to create the JGit features and p2 repository
- the Tycho based EGit build then consumes JGit via its p2 repository. Using the Nexus unzip plugin [4]
my Tycho colleagues have implemented the JGit p2 repository could be published in Nexus so that the
EGit Hudson build wouldn't need to reference the JGit p2 repository on Hudson any longer.

[1] https://git.eclipse.org/r/#/c/1815/ "Provide native lstat() via JNI"
[2] https://git.eclipse.org/r/#/c/2126/ "Provide native readdir() via JNI"
[3] https://git.eclipse.org/r/#/c/2125/ "Provide native symlink() via JNI"

--
Matthias

Back to the top