You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Incze Lajos <in...@mail.matav.hu> on 2003/05/16 00:31:21 UTC
Maven bootstrap and repositories
No change at me after the patch.
===============================
1.
[incze@senorg tmp]$ cd /o/import
[incze@senorg import]$ cvs -d :pserver:anoncvs@cvs.apache.org:/home/cvspublic co maven
[...]
2.
[incze@senorg tmp]$ cd /tmp
[incze@senorg tmp]$ cp -a /o/import/maven .
[incze@senorg tmp]$ cd maven
[incze@senorg maven]$ echo $MAVEN_HOME
/home/s/maven
[incze@senorg maven]$ ls $MAVEN_HOME/repository
aelfred/ commons-messenger/ mm.mysql/
ant/ commons-net/ msv/
ant-contrib/ commons-util/ nekohtml/
antlr/ dom4j/ ojb/
[...]
3.
[incze@senorg maven]$ ant -f build-bootstrap.xml
Buildfile: build-bootstrap.xml
check-maven-home:
check-maven-home-local-1:
check-maven-home-local-2:
check-maven-repo-local:
check-properties:
env:
[echo] maven.home = /home/s/maven
[echo] maven.home.local = /home/incze/.maven
[echo] maven.repo.local = /home/incze/.maven/repository
[echo]
[echo] +----------------------------------------------------------
[echo] | WARNING WARNING WARNING WARNING WARNING WARNING WARNING
[echo] |
[echo] | Maven bootstrap now creates a repository in
[echo] | ${user.home}/.maven/repository
[echo] | if you do not have the maven.repo.local property set
[echo] | before bootstrapping.
[echo] |
[echo] | Maven bootstrap also expands plugins to
[echo] | ${user.home}/.maven/plugins
[echo] | if you do not have the MAVEN_HOME_LOCAL environment
[echo] | variable or
[echo] | maven.home.local property set before bootstrapping.
[echo] |
[echo] | This feature is to accomodate the new ability of Maven
[echo] | to work from a read only install to MAVEN_HOME.
[echo] |
[echo] | WARNING WARNING WARNING WARNING WARNING WARNING WARNING
[echo] +----------------------------------------------------------
bootstrap-compile:
[mkdir] Created dir: /home/s/tmp/maven/bootstrap/bootstrap-classes
[javac] Compiling 4 source files to /home/s/tmp/maven/bootstrap/bootstrap-classes
bootstrap:
[echo]
[echo] +------------------------------------------------------------------+
[echo] | |
[echo] | L O A D I N G B O O T S T R A P T A S K D E F |
[echo] | |
[echo] +------------------------------------------------------------------+
[echo]
[echo] +------------------------------------------------------------------+
[echo] | |
[echo] | R U N N I N G B O O T S T R A P T A S K |
[echo] | |
[echo] +------------------------------------------------------------------+
[bootstrap] ................................................................................................................................................................................................................................................................................................................................
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< SNIP <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
So, it is working the same way as was reported before. It is my understanding
from the today discussion that if I have a MAVEN_HOME set, which points to
a good installed maven, then the bootstrap should use the existing repository
and I don't have to set any further environment variables, and
maven.home.local should default to maven.home.
Am I misunderstanding this?
incze
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven bootstrap and repositories
Posted by Incze Lajos <in...@mail.matav.hu>.
> > So, it is working the same way as was reported before. It is my understanding
> > from the today discussion that if I have a MAVEN_HOME set, which points to
> > a good installed maven, then the bootstrap should use the existing repository
> > and I don't have to set any further environment variables, and
> > maven.home.local should default to maven.home.
> >
>
> As In the warning message, if you do not have the maven.repo.local set,
> then by default the bootstrap makes a new repository in
> ${user.home}/.maven/repository
>
> If you want to use a different repo, say from your goodly installed
> maven, the you would have to set
>
> maven.repo.local=/home/s/maven/repository
>
> Regardless if the build fails without error handling then that should be
> improved, in which case please provide me with such error you are seeing.
>
> -Peter
>
> > Am I misunderstanding this?
> >
> > incze
So, I really misunderstood the discussion. I thought that ther was
an agreement,that if maven.home.local is not set then it defaults
to maven.home. If somebody wants 'something completely different'
she has to set it for herself. It's just economical. If we have
MAVEN_HOME, then it's highly plausible, that the repository is there
under. It seems to be the exception, that it would be placed
somewhere else.
incze
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven bootstrap and repositories
Posted by Brett Porter <bp...@f2network.com.au>.
> Regardless if the build fails without error handling then that should be
> improved, in which case please provide me with such error you are seeing.
>
I was getting SocketExceptions trying to bootstrap last night, even just
checking for the timestamp. I've got a quicky patch attached to
MAVEN-434 - certainly not a long term solution, just does 3 retries and
states which dependency it is trying to download.
Cheers,
Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven bootstrap and repositories
Posted by Peter Lynch <pe...@mindspring.com>.
Incze Lajos wrote:
> No change at me after the patch.
> ===============================
>
> 1.
> [incze@senorg tmp]$ cd /o/import
> [incze@senorg import]$ cvs -d :pserver:anoncvs@cvs.apache.org:/home/cvspublic co maven
> [...]
>
> 2.
> [incze@senorg tmp]$ cd /tmp
> [incze@senorg tmp]$ cp -a /o/import/maven .
> [incze@senorg tmp]$ cd maven
> [incze@senorg maven]$ echo $MAVEN_HOME
> /home/s/maven
> [incze@senorg maven]$ ls $MAVEN_HOME/repository
> aelfred/ commons-messenger/ mm.mysql/
> ant/ commons-net/ msv/
> ant-contrib/ commons-util/ nekohtml/
> antlr/ dom4j/ ojb/
> [...]
>
> 3.
> [incze@senorg maven]$ ant -f build-bootstrap.xml
> Buildfile: build-bootstrap.xml
>
> check-maven-home:
>
> check-maven-home-local-1:
>
> check-maven-home-local-2:
>
> check-maven-repo-local:
>
> check-properties:
>
> env:
> [echo] maven.home = /home/s/maven
> [echo] maven.home.local = /home/incze/.maven
> [echo] maven.repo.local = /home/incze/.maven/repository
> [echo]
> [echo] +----------------------------------------------------------
> [echo] | WARNING WARNING WARNING WARNING WARNING WARNING WARNING
> [echo] |
> [echo] | Maven bootstrap now creates a repository in
> [echo] | ${user.home}/.maven/repository
> [echo] | if you do not have the maven.repo.local property set
> [echo] | before bootstrapping.
> [echo] |
> [echo] | Maven bootstrap also expands plugins to
> [echo] | ${user.home}/.maven/plugins
> [echo] | if you do not have the MAVEN_HOME_LOCAL environment
> [echo] | variable or
> [echo] | maven.home.local property set before bootstrapping.
> [echo] |
> [echo] | This feature is to accomodate the new ability of Maven
> [echo] | to work from a read only install to MAVEN_HOME.
> [echo] |
> [echo] | WARNING WARNING WARNING WARNING WARNING WARNING WARNING
> [echo] +----------------------------------------------------------
>
> bootstrap-compile:
> [mkdir] Created dir: /home/s/tmp/maven/bootstrap/bootstrap-classes
> [javac] Compiling 4 source files to /home/s/tmp/maven/bootstrap/bootstrap-classes
>
> bootstrap:
> [echo]
> [echo] +------------------------------------------------------------------+
> [echo] | |
> [echo] | L O A D I N G B O O T S T R A P T A S K D E F |
> [echo] | |
> [echo] +------------------------------------------------------------------+
> [echo]
> [echo] +------------------------------------------------------------------+
> [echo] | |
> [echo] | R U N N I N G B O O T S T R A P T A S K |
> [echo] | |
> [echo] +------------------------------------------------------------------+
> [bootstrap] ................................................................................................................................................................................................................................................................................................................................
>
Where is your build failure message?
> <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< SNIP <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
>
> So, it is working the same way as was reported before. It is my understanding
> from the today discussion that if I have a MAVEN_HOME set, which points to
> a good installed maven, then the bootstrap should use the existing repository
> and I don't have to set any further environment variables, and
> maven.home.local should default to maven.home.
>
As In the warning message, if you do not have the maven.repo.local set,
then by default the bootstrap makes a new repository in
${user.home}/.maven/repository
If you want to use a different repo, say from your goodly installed
maven, the you would have to set
maven.repo.local=/home/s/maven/repository
Regardless if the build fails without error handling then that should be
improved, in which case please provide me with such error you are seeing.
-Peter
> Am I misunderstanding this?
>
> incze
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven bootstrap and repositories
Posted by Incze Lajos <in...@mail.matav.hu>.
On Fri, May 16, 2003 at 12:31:21AM +0200, Incze Lajos wrote:
> No change at me after the patch.
> ===============================
>
[...]
Even worse. The bootstrap build does not work because it needs
cglib-1.0.jar from ibiblio - but it doesn't exists. (There is an
cglib-rc2-1.0.jar there).
incze
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org