The only thing that worked for me (I tried a LOT of diff things) was to
shutdown continuum ( I used pkill - ps kill) and then go into the database
and remove the project from the table. You would need to log in to derby as
the sa user.
Anoop
On 4/17/07, Mykel Alvis [EMAIL PROTECTED] wrote:
I
I think I know what he means, as I have seen the same.
It thrashes in case of a multimodule project.
If you have
parent
-child1
-child2
It executes first for parent the goals (clean install site site:deploy),
then child1 and then child2. So if one of your childs fails, you have
half the
Yes, that's exactly what happens.
Probably I should address this question to the maven list ?
Nick Stolwijk [EMAIL PROTECTED] wrote: I think I know what he means, as I
have seen the same.
It thrashes in case of a multimodule project.
If you have
parent
-child1
-child2
It executes
Oh, I see.
How about changing your site build to run a script that does...
1. mkdir tmp-site
2. mvn clean site site:deploy
-DdistributionManagement.site.url=./tmp-site
3. if success; mv tmp-site /var/www/site
I suppose it in a Maven issue, but it's a fundamental 'feature' of how
Maven works.
hitting the build all button might clear this.
Andy
On 18 Apr 2007, at 12:52, Morgovsky, Alexander ((US - Glen Mills))
wrote:
Please help, we are at the point of uninstalling Continuum and again
installing everything. I sincerely hope you can provide a solution
for
this, as these
It does not, the old build is still in progress.
-Original Message-
From: Andrew Williams [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 18, 2007 1:43 PM
To: continuum-users@maven.apache.org
Subject: Re: How can I stop a build if I don't see the Java processes
for it?
hitting the
