26 Sep
2008
26 Sep
'08
1:35 a.m.
[Ricardo Rodriguez] Your EPEC Network ICT Team wrote:
Thanks both! This step is clear for me now at least in
a MacBook Pro
box. Next station: check out the software and try to build it.
I am writing down the steps toward a developing environment in a MacBook
Pro in a XWiki page here...
http://xepecnet.environmentalchange.net/xwiki/bin/view/ICT/DevelopingEnviro…
I think there are a few problems in the environment variables, it should be:
export M2=/usr/local/apache-maven/apache-maven-2.1.0-M1/bin
(note the /bin at the end, in there is the mvn executable)
export PATH=$M2:$PATH
($M2 should be before $PATH, so that mvn is first searched in there, and
then in other directories; this ensures that THIS version of maven is
executed, and not the system-wide one)
export MAVEN_OPTS="-Xmx600m -Xms600m"
I thinx Xms is not a good idea to set to such a large value, as it will
always allocate this much memory, even if it isn't needed.
If you consider it suitable for dev.xwiki.org, let me know where could I
create it and I will move it there. Perhaps as a simple "case study", it
is not worth to move it out of EPEC Network.
Cheers,
Ricardo
Paul Libbrecht wrote:
>
> Le 24-sept.-08 à 10:26, Sergiu Dumitriu a écrit :
>
>>> There's no performance penalty in setting up a few variables! really
>>> none.
>> Not really none, a few nano seconds... Certainly much less that a
>> hundredth of a second.
> compared to a mvn startup?
>
> paul
--
Sergiu Dumitriu
http://purl.org/net/sergiu/