Nathan, I had a similar problem where I aborted the initial maven build and it left my $HOME/.maven/plugins in an inconsistent state. The abort timing was such that it created the directory, but not yet created the files within (or possibly some, but not all files). What this did was to cause maven to run and fail silently without any indication of the problem.
What I did to fix it was to: . remove $HOME/.maven/plugins directory . rerun my maven build -- without aborting it! It all sync'd up okay and was fine afterwards. Also, run maven -g to ensure that all expected goals are getting displayed, as that was a clue to my inconsistent state. Apparently maven dynamically generates this list of goals from the .plugins itself. I don't know if this is the answer to your problem, but it may help to identify the environmental differences between your users. G'luck! -dave > -----Original Message----- > From: Nathan Coast [mailto:[EMAIL PROTECTED] > Sent: Sunday, February 29, 2004 8:34 PM > To: Maven Users > Subject: problem with artifact install > > > Hi, > > One of our developers is trying to run ejb:install but the > ejb isn't getting to > the repo. Strange thing is that it works for all other > developers with no > problem. We're using a shared repo. I placed an echo within > the ejb:install > goal so it is definitely being executed. We're getting the > build successful > message but no error, even with -X. Any ideas how to debug this? > > Cheers > Nathan > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
