| 1 |
Jörg, |
| 2 |
|
| 3 |
Thanks for the suggestions. I was able to get over this issue at last. |
| 4 |
It's probably because I haven't given priority to maven-compat (which |
| 5 |
has the class org.apache.maven.cli.compat.CompatibleMain) over other |
| 6 |
(symlinked) packages. I've renamed it to 01_maven-compat.jar. I've |
| 7 |
tried the your suggestions as well, may be the CRLF case played a part |
| 8 |
here too! |
| 9 |
|
| 10 |
Right now, `mvn-2 clean` works _with_ a pre-setup m2 repo with |
| 11 |
necessary plugins! ;) |
| 12 |
There's this error pops up when trying 'clean' with an empty m2 repo. |
| 13 |
'mvn compile' fails whether or not the needed plugins already |
| 14 |
available. I'm trying to track down this error now. It's failing |
| 15 |
either because it does not try to download needed jars or some version |
| 16 |
mismatch (which I doubt) triggering NoSuchMethodError or because of a |
| 17 |
missing component. If you have any inputs, please let me know. |
| 18 |
|
| 19 |
The generated component |
| 20 |
org.sonatype.plexus.components.sec.dispatcher.SecDispatcher is of type |
| 21 |
'default' not 'maven'! |
| 22 |
|
| 23 |
http://pastebin.com/NMp7ULXx |
| 24 |
|
| 25 |
More comments below... |
| 26 |
|
| 27 |
On Thu, Jun 30, 2011 at 2:46 AM, Jörg Schaible <joerg.schaible@×××.de> wrote: |
| 28 |
|
| 29 |
> |
| 30 |
>> Maven is called via classworlds with the command: |
| 31 |
>> "${JAVACMD}" \ |
| 32 |
>> $MAVEN_OPTS \ |
| 33 |
>> -classpath $(java-config -p classworlds-1.1) \ |
| 34 |
>> -Dclassworlds.conf=/usr/share/maven-2/maven_home/bin/m2.conf \ #the m2. |
| 35 |
>> -Dmaven.home=/usr/share/maven-2.2 \ |
| 36 |
>> -Dmaven.repo.remote=${HOME}/.m2/repository \ |
| 37 |
>> -Dmaven.repo.local=${HOME}/.m2/repository \ |
| 38 |
>> ${CLASSWORLDS_LAUNCHER} \ |
| 39 |
>> ${@} |
| 40 |
>> |
| 41 |
>> (The full script: |
| 42 |
>> http://overlays.gentoo.org/proj/java/browser/gsoc-maven-overlay/dev- |
| 43 |
> java/maven/files/2.2.1/bin/mvn) |
| 44 |
> |
| 45 |
> Explain __MAVENHOME__ and __MAVEN_SHARE__. |
| 46 |
|
| 47 |
JAVA_MAVEN_SYSTEM_HOME="/usr/share/maven-${JAVA_MAVEN_VERSION}/maven_home" |
| 48 |
MAVEN=${PN}-${SLOT} |
| 49 |
MAVEN_SHARE="/usr/share/${MAVEN}" |
| 50 |
|
| 51 |
__MAVENHOME__ get replaced by JAVA_MAVEN_SYSTEM_HOME and other one |
| 52 |
respectively in src_unpack phase. |
| 53 |
|
| 54 |
See: |
| 55 |
http://overlays.gentoo.org/proj/java/browser/gsoc-maven-overlay/dev-java/maven/maven-2.2.1.ebuild#L152 |
| 56 |
http://overlays.gentoo.org/proj/java/browser/gsoc-maven-overlay/eclass/java-maven-2.eclass#L93 |
| 57 |
|
| 58 |
> |
| 59 |
> I am also wondering about: |
| 60 |
> |
| 61 |
>> -Dmaven.repo.remote=${HOME}/.m2/repository \ |
| 62 |
>> -Dmaven.repo.local=${HOME}/.m2/repository \ |
| 63 |
> |
| 64 |
> Note, that the format of the meta data in a remote and a local repo |
| 65 |
> *differs*. AFAICS you cannot have both at the same location. Why not have |
| 66 |
> one single system-wide remote repo, that is "stuffed" with the Gentoo- |
| 67 |
> installed libraries only? Simply add that to |
| 68 |
> /usr/share/maven-2.2/conf/settings.xml in an always active profile named |
| 69 |
> e.g. "gentoo-system". |
| 70 |
|
| 71 |
Yes, I think we should remove |
| 72 |
-Dmaven.repo.remote=${HOME}/.m2/repository. Actually, remote repo |
| 73 |
refers to a server which we generally via http protocal anyway, right? |
| 74 |
User can provide the remote repo via settings.xml later on. |
| 75 |
|
| 76 |
what do you mean by "system-wide remote repo"? Currently we have a |
| 77 |
system wide _local_ repo at /usr/share/maven-2/maven_home/gentoo-repo. |
| 78 |
|
| 79 |
|
| 80 |
Thanks, |
| 81 |
--Kasun |
| 82 |
|
| 83 |
-- |
| 84 |
~~~*******'''''''''''''*******~~~ |
| 85 |
Kasun Gajasinghe, |
| 86 |
University of Moratuwa, |
| 87 |
Sri Lanka. |
| 88 |
Blog: http://blog.kasunbg.org |
| 89 |
Twitter: http://twitter.com/kasunbg |
Archives