1 |
On 03/29/2011 06:47 AM, Kasun Gajasinghe wrote: |
2 |
> |
3 |
> I'd like to know how the dependencies will be handled by maven based |
4 |
> ebuilds. Can you let me know the difference between dependencies |
5 |
> specified in Maven's POM file, and ebuild's dependencies? Are both |
6 |
> should be same? Since, Maven's POM contains the unique artifacts IDs |
7 |
> (with the combination of groupId, artifactId, version) which points to |
8 |
> a _binary_ jar, how should the developers who write _ebuilds_ specify |
9 |
> it? I got to know that dependencies are also ebuilds under gentoo i.e. |
10 |
> no binaries. |
11 |
> |
12 |
|
13 |
I am not sure how POM files categorize dependencies but in general there |
14 |
should be some kind of a mapping between the two. |
15 |
|
16 |
> I've been going through the Ralph's (nick: sera ) suggested eclass |
17 |
> [1]. It turned out to be very useful. (sera, I got your name from [1], |
18 |
> hope it's correct! :) ). Because maven offline building is the biggest |
19 |
> issue Gentoo is currently facing, As Petteri suggested, I've been |
20 |
> going through to see how other distributions handle this. I see that |
21 |
> both in sera's eclass and in Debian's MavenRepoSpec [2], that they |
22 |
> specify a variable which points to a maven local-repository location. |
23 |
> Ralph's eclass specified MAVEN_REPO_DIR="${T}/maven-repo/" while |
24 |
> Debian has REPO=/usr/share/maven-repo. Since the file-system will be |
25 |
> read-only for ebuilds, and ebuilds should be built offline, what's the |
26 |
> purpose of this? |
27 |
> |
28 |
|
29 |
${T} is a temporary directory for a single ebuild so it's writable. |
30 |
|
31 |
> Further, please let me know the other issues that needs to be |
32 |
> addressed that you have in mind. It turned out that the project is |
33 |
> challenging than I thought before, and is getting exciting now! |
34 |
> |
35 |
|
36 |
Besides writing the needed infrastructure for building with Maven it |
37 |
would also be useful to convert as much as possible of our manual |
38 |
ebuilds to use that infrastructure so that the solution will also be |
39 |
field tested. I see the work happening initially in a separate overlay |
40 |
with the goal of main tree merging before the project is over. |
41 |
|
42 |
Petteri |