when I run the clean:clean goal, it's failing because the project dependencies are missing. They are missing because I have already run a clean goal, or have not yet run a build. I would think that clean could run without dependencies, since it's just going to delete some build by-products.

For instance, if my project has a .jar dependency, when I

maven clean

I get this:


>maven clean __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0

Attempting to download sakai2-component-sakai.2.0.0.jar.
WARNING: Failed to download sakai2-component-sakai.2.0.0.jar.
Attempting to download sakai2-comp-test-service-sakai.2.0.0.jar.
WARNING: Failed to download sakai2-comp-test-service-sakai.2.0.0.jar.
The build cannot continue because of the following unsatisfied dependencies:


sakai2-component-sakai.2.0.0.jar
sakai2-comp-test-service-sakai.2.0.0.jar

Total time: 14 seconds
Finished at: Thu Feb 17 15:37:22 EST 2005

[spring:sakai2/test/comp-test-app2] ggolden% ls
maven.xml       project.xml     src             target


Each attempt take a long time to fail. When it's one, the "target" directory is still there.


Is there an option to disable this checking I can add to my "clean" goal's definition?

Thanks.

- Glenn

Glenn R. Golden, Sakai Architect
Sr. Systems Research Programmer, University of Michigan
[EMAIL PROTECTED]


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



Reply via email to