You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@continuum.apache.org by Ionut S <si...@yahoo.com> on 2007/04/12 15:41:49 UTC
mvn site site:deploy problem
Hi,
Not sure if my problem is related to mvn or continuum, so excuse me if I'm wrong..
Anyway, we have a continuum site in place, which works fine in general. There is one abnormal behaviour that made me write to this list though: if the build fails (for any reason), the site gets trashed. This is because the command we give:
mvn clean install site site:deploy
starts to copy the files for each project, without waiting for the whole project to be built. This trashes the site and we can't see it unless we fix the build.
Is there something we can do in order to fix this issue ?
Thank you !
Ionut
---------------------------------
Never miss an email again!
Yahoo! Toolbar alerts you the instant new Mail arrives. Check it out.
Re: mvn site site:deploy problem
Posted by David Roussel <co...@diroussel.xsmail.com>.
On Wed, 18 Apr 2007 06:50:25 -0700 (PDT), "Ionut S" <si...@yahoo.com>
said:
> Ok, if I create that script how can I tell Continuum to run it ?
Re: mvn site site:deploy problem
Posted by Ionut S <si...@yahoo.com>.
Ok, if I create that script how can I tell Continuum to run it ?
As our continuum server is configured right now, I can only add a new goal, not a script..
David Roussel <co...@diroussel.xsmail.com> wrote: 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. It's as if there needs to be another level above the maven
lifecycle, for automic builds on multi module projects.
David
On Wed, 18 Apr 2007 05:44:39 -0700 (PDT), "Ionut S"
said:
> Yes, that's exactly what happens.
>
> Probably I should address this question to the maven list ?
>
>
>
> Nick Stolwijk 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 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 new site and half the old site.
>
> So it's more a mvn issue I guess. I don't know all the implications, but
> it would be nicer if the tree was walked for each goal. Thus clean
> parent, child1, child2, install parent, child1, child2, etc. Then it
> would only deploy the whole site, when the whole site can be generated.
>
> With regards,
>
> Nick S.
>
> David Roussel wrote:
> > Trashes it in what way? Which files are missing?
> >
> > My understanding is that when you do site:deploy it just copies to file
> > over, it doesn't delete from the target first. But exactly how this
> > works probably depends on how you have it configured.
> >
> > Do you get the same problem if you have:
> >
> >
> >
> > website
> > file:///C:\Program Files\Apache
> > Group\Apache2\htdocs\site
> >
> >
> >
> > What url are you currently using?
> >
> > David
> >
> > On Thu, 12 Apr 2007 06:41:49 -0700 (PDT), "Ionut S"
> > said:
> >
> >> Hi,
> >> Not sure if my problem is related to mvn or continuum, so excuse me if
> >> I'm wrong..
> >>
> >> Anyway, we have a continuum site in place, which works fine in general.
> >> There is one abnormal behaviour that made me write to this list though:
> >> if the build fails (for any reason), the site gets trashed. This is
> >> because the command we give:
> >>
> >> mvn clean install site site:deploy
> >>
> >> starts to copy the files for each project, without waiting for the whole
> >> project to be built. This trashes the site and we can't see it unless we
> >> fix the build.
> >>
> >> Is there something we can do in order to fix this issue ?
> >>
> >> Thank you !
> >> Ionut
> >>
> >>
> >> ---------------------------------
> >> Never miss an email again!
> >> Yahoo! Toolbar alerts you the instant new Mail arrives. Check it out.
> >>
> >
> >
>
>
>
>
> ---------------------------------
> Ahhh...imagining that irresistible "new car" smell?
> Check outnew cars at Yahoo! Autos.
---------------------------------
Ahhh...imagining that irresistible "new car" smell?
Check outnew cars at Yahoo! Autos.
Re: mvn site site:deploy problem
Posted by David Roussel <co...@diroussel.xsmail.com>.
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. It's as if there needs to be another level above the maven
lifecycle, for automic builds on multi module projects.
David
On Wed, 18 Apr 2007 05:44:39 -0700 (PDT), "Ionut S" <si...@yahoo.com>
said:
> Yes, that's exactly what happens.
>
> Probably I should address this question to the maven list ?
>
>
>
> Nick Stolwijk <ni...@planet.nl> 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 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 new site and half the old site.
>
> So it's more a mvn issue I guess. I don't know all the implications, but
> it would be nicer if the tree was walked for each goal. Thus clean
> parent, child1, child2, install parent, child1, child2, etc. Then it
> would only deploy the whole site, when the whole site can be generated.
>
> With regards,
>
> Nick S.
>
> David Roussel wrote:
> > Trashes it in what way? Which files are missing?
> >
> > My understanding is that when you do site:deploy it just copies to file
> > over, it doesn't delete from the target first. But exactly how this
> > works probably depends on how you have it configured.
> >
> > Do you get the same problem if you have:
> >
> >
> >
> > website
> > file:///C:\Program Files\Apache
> > Group\Apache2\htdocs\site
> >
> >
> >
> > What url are you currently using?
> >
> > David
> >
> > On Thu, 12 Apr 2007 06:41:49 -0700 (PDT), "Ionut S"
> > said:
> >
> >> Hi,
> >> Not sure if my problem is related to mvn or continuum, so excuse me if
> >> I'm wrong..
> >>
> >> Anyway, we have a continuum site in place, which works fine in general.
> >> There is one abnormal behaviour that made me write to this list though:
> >> if the build fails (for any reason), the site gets trashed. This is
> >> because the command we give:
> >>
> >> mvn clean install site site:deploy
> >>
> >> starts to copy the files for each project, without waiting for the whole
> >> project to be built. This trashes the site and we can't see it unless we
> >> fix the build.
> >>
> >> Is there something we can do in order to fix this issue ?
> >>
> >> Thank you !
> >> Ionut
> >>
> >>
> >> ---------------------------------
> >> Never miss an email again!
> >> Yahoo! Toolbar alerts you the instant new Mail arrives. Check it out.
> >>
> >
> >
>
>
>
>
> ---------------------------------
> Ahhh...imagining that irresistible "new car" smell?
> Check outnew cars at Yahoo! Autos.
Re: mvn site site:deploy problem
Posted by Ionut S <si...@yahoo.com>.
Yes, that's exactly what happens.
Probably I should address this question to the maven list ?
Nick Stolwijk <ni...@planet.nl> 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 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 new site and half the old site.
So it's more a mvn issue I guess. I don't know all the implications, but
it would be nicer if the tree was walked for each goal. Thus clean
parent, child1, child2, install parent, child1, child2, etc. Then it
would only deploy the whole site, when the whole site can be generated.
With regards,
Nick S.
David Roussel wrote:
> Trashes it in what way? Which files are missing?
>
> My understanding is that when you do site:deploy it just copies to file
> over, it doesn't delete from the target first. But exactly how this
> works probably depends on how you have it configured.
>
> Do you get the same problem if you have:
>
>
>
> website
> file:///C:\Program Files\Apache
> Group\Apache2\htdocs\site
>
>
>
> What url are you currently using?
>
> David
>
> On Thu, 12 Apr 2007 06:41:49 -0700 (PDT), "Ionut S"
> said:
>
>> Hi,
>> Not sure if my problem is related to mvn or continuum, so excuse me if
>> I'm wrong..
>>
>> Anyway, we have a continuum site in place, which works fine in general.
>> There is one abnormal behaviour that made me write to this list though:
>> if the build fails (for any reason), the site gets trashed. This is
>> because the command we give:
>>
>> mvn clean install site site:deploy
>>
>> starts to copy the files for each project, without waiting for the whole
>> project to be built. This trashes the site and we can't see it unless we
>> fix the build.
>>
>> Is there something we can do in order to fix this issue ?
>>
>> Thank you !
>> Ionut
>>
>>
>> ---------------------------------
>> Never miss an email again!
>> Yahoo! Toolbar alerts you the instant new Mail arrives. Check it out.
>>
>
>
---------------------------------
Ahhh...imagining that irresistible "new car" smell?
Check outnew cars at Yahoo! Autos.
Re: mvn site site:deploy problem
Posted by Nick Stolwijk <ni...@planet.nl>.
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 new site and half the old site.
So it's more a mvn issue I guess. I don't know all the implications, but
it would be nicer if the tree was walked for each goal. Thus clean
parent, child1, child2, install parent, child1, child2, etc. Then it
would only deploy the whole site, when the whole site can be generated.
With regards,
Nick S.
David Roussel wrote:
> Trashes it in what way? Which files are missing?
>
> My understanding is that when you do site:deploy it just copies to file
> over, it doesn't delete from the target first. But exactly how this
> works probably depends on how you have it configured.
>
> Do you get the same problem if you have:
>
> <distributionManagement>
> <site>
> <id>website</id>
> <url>file:///C:\Program Files\Apache
> Group\Apache2\htdocs\site</url>
> </site>
> </distributionManagement>
>
> What url are you currently using?
>
> David
>
> On Thu, 12 Apr 2007 06:41:49 -0700 (PDT), "Ionut S" <si...@yahoo.com>
> said:
>
>> Hi,
>> Not sure if my problem is related to mvn or continuum, so excuse me if
>> I'm wrong..
>>
>> Anyway, we have a continuum site in place, which works fine in general.
>> There is one abnormal behaviour that made me write to this list though:
>> if the build fails (for any reason), the site gets trashed. This is
>> because the command we give:
>>
>> mvn clean install site site:deploy
>>
>> starts to copy the files for each project, without waiting for the whole
>> project to be built. This trashes the site and we can't see it unless we
>> fix the build.
>>
>> Is there something we can do in order to fix this issue ?
>>
>> Thank you !
>> Ionut
>>
>>
>> ---------------------------------
>> Never miss an email again!
>> Yahoo! Toolbar alerts you the instant new Mail arrives. Check it out.
>>
>
>
Re: mvn site site:deploy problem
Posted by David Roussel <co...@diroussel.xsmail.com>.
Trashes it in what way? Which files are missing?
My understanding is that when you do site:deploy it just copies to file
over, it doesn't delete from the target first. But exactly how this
works probably depends on how you have it configured.
Do you get the same problem if you have:
<distributionManagement>
<site>
<id>website</id>
<url>file:///C:\Program Files\Apache
Group\Apache2\htdocs\site</url>
</site>
</distributionManagement>
What url are you currently using?
David
On Thu, 12 Apr 2007 06:41:49 -0700 (PDT), "Ionut S" <si...@yahoo.com>
said:
> Hi,
> Not sure if my problem is related to mvn or continuum, so excuse me if
> I'm wrong..
>
> Anyway, we have a continuum site in place, which works fine in general.
> There is one abnormal behaviour that made me write to this list though:
> if the build fails (for any reason), the site gets trashed. This is
> because the command we give:
>
> mvn clean install site site:deploy
>
> starts to copy the files for each project, without waiting for the whole
> project to be built. This trashes the site and we can't see it unless we
> fix the build.
>
> Is there something we can do in order to fix this issue ?
>
> Thank you !
> Ionut
>
>
> ---------------------------------
> Never miss an email again!
> Yahoo! Toolbar alerts you the instant new Mail arrives. Check it out.