Exactly! but how i do it? its my problem. I don't get it. I don't see that flag. I have been trying using this arguments
-Dmaven.site.deploy.clean=true -Dmaven.site.publish.clean=true But it doesn't work. How to? Thanks On 4/11/06, John Casey <[EMAIL PROTECTED]> wrote: > > That would probably work pretty well, but I was just talking about a flag > you could set in the plugin config to say "it's OK to blow away that > directory before deploying" or else something like a site:remote-clean > that > could be bound to the phase ahead of site-deploy. > > -j > > On 4/11/06, Kenney Westerhof <[EMAIL PROTECTED]> wrote: > > > > On Tue, 11 Apr 2006, John Casey wrote: > > > > Another way would be to record what files constituted the last site > > deployment. IIRC a 'deployXXXX.zip' is uploaded and then unpacked. A > list > > of files in that zip could be recorded. Your proposal for a new > > clean flag would then take this list into account and only delete > > the files for that project. This might be safe enough? > > > > -- Kenney > > > > > Are you wondering why the deployment target location isn't removed > > before > > > re-deploying the site? That operates on the assumption that all the > > content > > > in or under that remote location is published by the current project, > or > > > that you will be fine with redeploying all of the content when you do > > this > > > site-deploy...which IMO is dangerous. > > > > > > For example, Maven itself publishes site content to multiple > locations, > > with > > > the topmost being the main site project. Modules publish their > reports, > > etc. > > > into subdirectories of the remote location referenced by the site > > > project...if we removed this top directory, we'd not only lose all of > > the > > > reports published by the modules, but all of the historical versions > of > > > these reports too. This is a lot to republish. > > > > > > Perhaps an optional clean parameter would help, but I'm not sure > whether > > the > > > underlying APIs currently support it. > > > > > > HTH, > > > > > > John > > > > > > On 4/11/06, Chucho <[EMAIL PROTECTED]> wrote: > > > > > > > > I'm using site-deploy on maven whit continuum and its work fine, but > > when > > > > I'm do it again and the folder already exits, the site can be > deploy, > > I'll > > > > use clean, but don't clean the deploy site. if a change the POM > > > > <distributionManagement> > > > > section then it would make the deploy whit out problem, but i want > the > > > > deploy overwrites the file or delete the site deploy folder and > deploy > > > > again. i have check the permissions on the folder and have write > > > > permissions. > > > > > > > > the command its: > > > > clean install site-deploy > > > > and the arguments: > > > > --batch-mode --non-recursive > > > > > > > > How can i do to make site-deploy once and again on the same folder? > > > > > > > > > > > > POM.xml > > > > > > > > <distributionManagement> > > > > <site> > > > > <id>WNserver</id> > > > > <url>file:C:\Inetpub\wwwroot\continuum\prueba2</url> > > > > </site> > > > > </distributionManagement> > > > > > > > > > > > > > > > -- > > Kenney Westerhof > > http://www.neonics.com > > GPG public key: http://www.gods.nl/~forge/kenneyw.key > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > >
