On Thu, 30 May 2002, Chris Widhelm wrote:

> I sent this problem with the bootstrap in last week...however, I don't think
> that anyone noticed.  So I will send it again.
> 
> This is the error I get:
> 
>       D:\maven-inst\plugins\core\build.xml:358: taskdef class
> org.apache.maven.ant.Ant cannot be found
> 
> Here is the series of targets:
> 
>       bootstrap
>               install
>                       generate-build -> creates the maven.jar file in
> ${lib.repo}
>                               make-maven-home-dir
>                                       clean-maven-home-dir -> deletes the
> maven.jar file in ${lib.repo}
> 
> It appears to be due to the fact that after the maven.jar is created in
> ${lib.repo} a few tasks later it ends up getting deleted.
> 
> I would think this was a problem and I'm not sure how everyone elses
> bootstrap is working and mine is not.

It doesn't happen in exactly that order.

Buildfile: build-bootstrap.xml

check-maven-home:

check-lib-repo:

check-properties:

clean:
   [delete] Deleting directory 
/export1/home/glenn/cvs/jakarta-turbine-maven/target
   [delete] Deleting: /export1/home/glenn/maven.repo/maven.jar

-> At this point, the maven.jar file is removed from my local repository.  
No problem.

<snip/>

phase2-compile:
    [javac] Compiling 31 source files to 
/export1/home/glenn/cvs/jakarta-turbine-maven/bootstrap/classes 
      [jar] Building jar: /export1/home/glenn/maven.repo/maven.jar

-> Now we've created a temporary jar file necessary to build the rest of 
the build-*.xml files and complete the building of the full maven.jar 
later.

 generate-build:
    [mkdir] Created dir: 
/export1/home/glenn/cvs/jakarta-turbine-maven/bootstrap/maven
[create-build-system] Generating to file 
/export1/home/glenn/cvs/jakarta-turbine-maven/bootstrap/bootstrap.report
[create-build-system] log4j:ERROR No appenders could be found for category 
(org.apache.commons.betwixt.XMLIntrospector).
[create-build-system] log4j:ERROR Please initialize the log4j system 
properly.

-> We just added betwixt, which uses commons-logging, and we don't have a 
log4j configuration file reachable by the package.  Thus the harmless but 
irritating error.

check-maven-home-dir:

clean-maven-home-dir:
   [delete] Deleting 63 files from /export1/home/glenn/maven
   [delete] Deleted 22 directories from /export1/home/glenn/maven

-> As you can see, this target does *not* remove maven.jar from 
${lib.repo}.

<big_snip/>

test: 
      [jar] Building jar: 
/export1/home/glenn/cvs/jakarta-turbine-maven/target/maven.jar

post-jar-callback-check:

post-jar-callback:

jar:

pre-install-jar-callback-check:

pre-install-jar-callback:

do-install-jar:
     [copy] Copying 1 file to /export1/home/glenn/maven.repo

-> And this is where the final copy of maven.jar gets copied to 
${lib.repo}, overwriting the existing bootstrap copy.

post-install-jar-callback-check:

post-install-jar-callback:

install-jar:

BUILD SUCCESSFUL


Glenn McAllister
SOMA Networks, Inc.




--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to