| 1 |
Hi, |
| 2 |
|
| 3 |
Kasun Gajasinghe wrote: |
| 4 |
|
| 5 |
just answering for the repo for now ... |
| 6 |
|
| 7 |
[snip] |
| 8 |
|
| 9 |
>> |
| 10 |
>> I am also wondering about: |
| 11 |
>> |
| 12 |
>>> -Dmaven.repo.remote=${HOME}/.m2/repository \ |
| 13 |
>>> -Dmaven.repo.local=${HOME}/.m2/repository \ |
| 14 |
>> |
| 15 |
>> Note, that the format of the meta data in a remote and a local repo |
| 16 |
>> *differs*. AFAICS you cannot have both at the same location. Why not have |
| 17 |
>> one single system-wide remote repo, that is "stuffed" with the Gentoo- |
| 18 |
>> installed libraries only? Simply add that to |
| 19 |
>> /usr/share/maven-2.2/conf/settings.xml in an always active profile named |
| 20 |
>> e.g. "gentoo-system". |
| 21 |
> |
| 22 |
> Yes, I think we should remove |
| 23 |
> -Dmaven.repo.remote=${HOME}/.m2/repository. Actually, remote repo |
| 24 |
> refers to a server which we generally via http protocal anyway, right? |
| 25 |
|
| 26 |
Any valid URL can do. Even using "file:" protocol. |
| 27 |
|
| 28 |
> User can provide the remote repo via settings.xml later on. |
| 29 |
> |
| 30 |
> what do you mean by "system-wide remote repo"? Currently we have a |
| 31 |
> system wide _local_ repo at /usr/share/maven-2/maven_home/gentoo-repo. |
| 32 |
|
| 33 |
Every user will have to use an own local repo. You cannot share a local repo |
| 34 |
between different users reliably. Additionally this is the repo the current |
| 35 |
user *writes to* even if he downloads something (this is already critical if |
| 36 |
you use M3's parallel build). Therefore you will have to establish a system- |
| 37 |
wide *remote* repo that is filled up with the Gentoo-built stuff. If that |
| 38 |
one is referred as remote repo in the settings.xml of the current Maven |
| 39 |
installation, it is always considered independently of a user's own |
| 40 |
repository declarations in his settings.xml. |
| 41 |
|
| 42 |
In the end it means that the different local repo's will always contain |
| 43 |
copies. Note, that it is for a developer a quite common task to wipe the |
| 44 |
local repo from time to time. |
| 45 |
|
| 46 |
If you set "maven.repo.remote", you overwrite Maven Central i.e. Maven's |
| 47 |
default repo, but it will not prevent other remote lookups. If you want to |
| 48 |
ensure that Maven is not using something else during ebuilds, you should use |
| 49 |
a special settings.xml anyway that declares the system-wide *remote* repo as |
| 50 |
mirror for everything ... |
| 51 |
|
| 52 |
- Jörg |
Archives