On 2/13/07, Felipe Gaucho <[EMAIL PROTECTED]> wrote:
actually I redo the steps in a clean directory just to check if it was not
some mistake.. and I detect it compiles anyway.. it is just a warning
message or something.. Anyway, it is a weird stack-trace for one trying a
new technology :)..
best to include in the tutorial some alert like "you will notice a long
stack trace - it is normal, just ignore it" :)
Not everyone sees the errors with Maven that you have seen. Many Maven
errors are because access to a given Maven repository may have been
affected by network performance causing a download to timeout and
throw errors. When I see errors, I usually rerun the same command a
few times to see if it succeeds. If not, then I run the command with
-X for debug output and study the output to determine the source of
the issue. Maven often throws exceptions that don't mean much as long
as the build is successful. The important thing when using Maven is to
make sure you receive the message BUILD SUCCESSFUL.
Bruce
--
perl -e 'print unpack("u30","D0G)[EMAIL
PROTECTED]&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
Apache Geronimo - http://geronimo.apache.org/
Apache ActiveMQ - http://activemq.org/
Apache ServiceMix - http://servicemix.org/
Castor - http://castor.org/
