Re: [gentoo-soc] [GSoC] Maven integration for Gentoo ebuilds

[Kasun Gajasinghe <kasunbg@gmail.com>]

On 29 Mar 2011, at 09:37, Serkan Kaba <serkan@gentoo.org> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 29-03-2011 06:47, Kasun Gajasinghe wrote:
>> I'd like to know how the dependencies will be handled by maven based
>> ebuilds. Can you let me know the difference between dependencies
>> specified in Maven's POM file, and ebuild's dependencies? Are both
>> should be same? Since, Maven's POM contains the unique artifacts IDs
>> (with the combination of groupId, artifactId, version) which points  
>> to
>> a _binary_ jar, how should the developers who write _ebuilds_ specify
>> it? I got to know that dependencies are also ebuilds under gentoo  
>> i.e.
>> no binaries.
> POM dependencies can be too restrictive sometimes, like depending on a
> specific version. We should be depending on any version (or sometimes
> with >=,<=) as long as the package compiles and runs fine with it.

I've come across a package called JPackage which does the job of  
retrieving a jar from /usr/share/java and return it to use by maven.  
It neglects the version numbers as well.


>> I've been going through the Ralph's (nick: sera ) suggested eclass
>> [1]. It turned out to be very useful. (sera, I got your name from  
>> [1],
>> hope it's correct! :) ). Because maven offline building is the  
>> biggest
>> issue Gentoo is currently facing, As Petteri suggested, I've been
>> going through to see how other distributions handle this. I see that
>> both in sera's eclass and in Debian's MavenRepoSpec [2], that they
>> specify a variable which points to a maven local-repository location.
>> Ralph's eclass specified MAVEN_REPO_DIR="${T}/maven-repo/" while
>> Debian has REPO=/usr/share/maven-repo. Since the file-system will be
>> read-only for ebuilds, and ebuilds should be built offline, what's  
>> the
>> purpose of this?
> We then still need to add symlinks to jars during build time in there
> which is an "access violation" in sand box

Ok. Then the viable option is to have to generate the maven directory  
structure inside a folder named ${T}/maven-repo. We can do the  
symlinking through that, and we won't face any access violation since  
the writing happens in the sandbox.
Ubuntu too have proposed a similar solution. I'm away from my machine,  
I'll provide the links to it as well as for the JPackage soon if it  
you all may want to check it out!

Thanks,
Kasun

>
> - --
> Sincerely,
> Serkan KABA
> Gentoo Developer
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.17 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAk2RWvIACgkQRh6X64ivZaLfkgCfVF99iZaa6Pa+dTlC4cjuLvZd
> ILkAn34OooCvrNy6uu9yEg4bua/q7X6G
> =staW
> -----END PGP SIGNATURE-----
>