removing bootstrap debugging option ..

git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@763460 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Oleg Gusakov 2009-04-08 23:25:59 +00:00
parent 3bdb1951c5
commit 3a049c8b5b
1 changed files with 4 additions and 16 deletions

View File

@ -20,29 +20,17 @@ You can use additiona options on ant command line:
-Dmaven.repo.system={mercury|legacy}
-Dmaven.home=$HOME/apps/maven/apache-maven-3.0-SNAPSHOT
if you'd like to debug the bootstrap from Eclipse, issue the following command:
export ANT_OPTS='-Dmercury.log.level=info -Dmercury.dump.tree=../forest'
export ANT_OPTS=$ANT_OPTS' -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=8000'
the additional options:
-Dmercury.log.level={info|warn|error|debug} - defines mercury verbocity
-Dmercury.dump.tree=../forest - tells mercury to spit all the resolved trees into files ../forest-xxx.xml, where xxx is a timestamp
Then connect Eclipse debugging session to local port 8000
for example:
if you'd like to debug the bootstrap from Eclipse, uncomment the debugging options in the build-mercury.xml around
line 310, then use the following commands:
For the first time - run the following, it will update the local repo
export ANT_OPTS='-Dmercury.log.level=info -Dmercury.dump.tree=../forest'
export ANT_OPTS=$ANT_OPTS' -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=8000'
ant -f build-mercury.xml -Dmaven.repo.update.policy=always
ant -f build-mercury.xml -Dmaven.repo.update.policy=always -Dmaven.repo.system=mercury
then you can run
ant -f build-mercury.xml -Dmaven.repo.update.policy=never -Dmaven.repo.system=mercury
to debug the bootstrap
not to bother with repo updates