Le 06/04/2013 14:02, Olivier Lamy a écrit : > Oh read here http://commons.staging.apache.org/site-publish.html > > Use mvn clean site-deploy which is different :-)
Oh crap ... This means I need to run the 4 hours process once again ? Isn't it a way I can simply check out the svn repository, copy the local files and commit it back myself without regenerating the whole stuff? Luc > > I will update the page > http://commons.staging.apache.org/releases/publish-site.html to link > to the other one. > > > 2013/4/6 Luc Maisonobe <luc.maison...@free.fr>: >> >> Hi Olivier, >> >> Le 06/04/2013 13:50, Olivier Lamy a écrit : >>> mvn clean site-deploy must work for single module build. >>> Do you have any issues using that ? >> >> Yes. Here is what I got from running the command from the RC5 workspace >> I still had lying around (I did it from this workspace because >> generating the sites takes 4 hours, and in this workspace the site was >> already generated, it simply needed to be forwarded to our repository): >> >> (lehrin) luc% mvn site:deploy >> [INFO] Scanning for projects... >> [INFO] >> >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] Building Commons Math 3.2 >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] >> [INFO] --- maven-site-plugin:3.2:deploy (default-cli) @ commons-math3 --- >> [INFO] maven.site.deploy.skip = true: Skipping site deployment >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] BUILD SUCCESS >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] Total time: 6.179s >> [INFO] Finished at: Sat Apr 06 11:48:47 CEST 2013 >> [INFO] Final Memory: 8M/90M >> [INFO] >> ------------------------------------------------------------------------ >> >> Looking into parent pom version 28, I saw this: >> >> <plugin> >> <groupId>org.apache.maven.plugins</groupId> >> <artifactId>maven-site-plugin</artifactId> >> <version>${commons.site-plugin.version}</version> >> <configuration> >> <!-- don't deploy site with maven-site-plugin --> >> <skipDeploy>true</skipDeploy> >> </configuration> >> </plugin> >> <plugin> >> >> So I guessed we should not use mavn site:deploy anymore. >> >> Luc >> >> >>> >>> >>> >>> 2013/4/6 Luc Maisonobe <l...@spaceroots.org>: >>>> Hi, >>>> >>>> I am in the process of releasing the 3.2 version. >>>> The source and binaries archives are online, the maven artifacts have >>>> been published, and now I want to update the site. >>>> >>>> I have a stupid question to ask: where is our subversion repository for >>>> the [math] site ? >>>> >>>> The page <http://commons.staging.apache.org/releases/release.html> >>>> refers to <http://commons.staging.apache.org/releases/publish-site.html> >>>> for site publication, but this page seems outdated. It still references >>>> maven deploy which does not work anymore. >>>> >>>> best regards, >>>> Luc >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >>>> For additional commands, e-mail: dev-h...@commons.apache.org >>>> >>> >>> >>> >>> -- >>> Olivier Lamy >>> Ecetera: http://ecetera.com.au >>> http://twitter.com/olamy | http://linkedin.com/in/olamy >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >>> For additional commands, e-mail: dev-h...@commons.apache.org >>> >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> > > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
