maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hervé BOUTEMY <herve.bout...@free.fr>
Subject Re: svn commit: r843406 - in /websites/production/maven/content/surefire-archives/surefire-2.13: ./ maven-failsafe-plugin/ maven-failsafe-plugin/css/ maven-failsafe-plugin/images/ maven-failsafe-plugin/images/logos/ maven-failsafe-plugin/images/profiles/ m...
Date Sun, 20 Jan 2013 04:21:14 GMT
just for the record: I updated Maven 3.1-SNAPSHOT site, there were little 
modifications in the code since last update (1 new package private class)

and here is the result:

[INFO] Publish files: 2 addition(s), 9373 update(s), 0 delete(s)
...
[INFO] Checked in 757 file(s) to revision: 847301
[INFO] 
------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache Maven ...................................... SUCCESS 
[25:18.042s]


25 minutes: not ideal, but bearable

as expected, the new package private class caused 2 new files (jxr and 
aggregated jxr, no javadoc)

as I see the commit log, 2 causes of content change without change in source = 
the vast majority of 757 modifications:

1. the "Last Published" date: IMHO, this info is useful, so we have to live 
with it

2. timestamp in Modello generated content: I opened a Jira issue [1]


So if we change our documentation release process to update a fixed "-latest" 
place and svn copy on release, svnpubsub should be bearable IMHO

Regards,

Hervé



[1] http://jira.codehaus.org/browse/MODELLO-265



Le lundi 7 janvier 2013 17:39:14 Brett Porter a écrit :
> -Copyright &#169; 2001-2012 <a href="http://www.apache.org/">The Apache
> Software Foundation</a>. All Rights Reserved. +Copyright &#169; 2001-2013
> <a href="http://www.apache.org/">The Apache Software Foundation</a>. All
> Rights Reserved.
> 
> 
> Looks like a once a year hit :)
> 
> - Brett
> 
> On 07/01/2013, at 5:25 PM, Hervé BOUTEMY <herve.boutemy@free.fr> wrote:
> > ok, thanks for the tips: will be useful to improve our configurations
> > 
> > FYI, I published latest Maven core 3.1-SNAPSHOT site as an update from
> > 2012-12-16 state:
> > [INFO] Updating the pub tree from
> > scm:svn:https://svn.apache.org/repos/infra/websites/production/maven/conte
> > nt/ref/3.1- SNAPSHOT ...
> > ...
> > [INFO] Updating content...
> > [INFO] Publish files: 94 addition(s), 9295 update(s), 9 delete(s)
> > ...
> > [INFO] Checked in 8608 file(s) to revision: 845276
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] BUILD SUCCESS
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] Total time: 4:19:44.415s
> > [INFO] Finished at: Mon Jan 07 04:25:02 CET 2013
> > [INFO] Final Memory: 16M/284M
> > [INFO]
> > ------------------------------------------------------------------------
> > 
> > More than 4 hours: still not really good.
> > 
> > I'll hunt the unuseful modifications checked-in: help welcome.
> > 
> > Regards,
> > 
> > Hervé
> > 
> > Le dimanche 6 janvier 2013 00:54:12 Brett Porter a écrit :
> >> On 05/01/2013, at 10:57 PM, Hervé BOUTEMY <herve.boutemy@free.fr> wrote:
> >>> ok, that was my first attempts back in july, not based on performance
> >>> expectations but simply logic
> >>> but the release procedure wasn't easy to automate in Maven: I don't see
> >>> in
> >>> Continuum instrusction where the "svn cp xxx/latest to
> >>> xxx/<release-version>" is done. Is it in a Unix shell script?
> >> 
> >> Pretty much, exec-maven-plugin:
> >> http://svn.apache.org/viewvc/continuum/trunk/continuum-docs/pom.xml?r1=14
> >> 27
> >> 648&r2=1427649&
> >> 
> >> scm:tag didn't support what was needed - but this could be added to the
> >> scm-publish plugin as an option.
> >> 
> >>> At that time, the intent was pure logic ("clean work" idea), with impact
> >>> on
> >>> the way to  import history: see
> >>> http://maven.apache.org/plugins/maven-scm-
> >>> publish-plugin/examples/importing-maven-site.html
> >>> But when Olivier came in to help me, we chose to drop this part and make
> >>> simple ("brute force"?) content import and drop this "latest" idea which
> >>> was hard to explain
> >>> 
> >>> It seems we need to get back to this latest idea since it is really a
> >>> strong performance requirement (and efficiency: yes, between 2 maven
> >>> release, not much content has changed in the 131 MB)
> >> 
> >>> I had a look at Continuum and I didn't find some thing we do in maven:
> >> Continuum's site structure is a bit confused, but it has 3 parts: a
> >> single
> >> site set of versioned documentation, a single main top-level site, and
> >> then
> >> a multi-module generated documentation set.
> >> 
> >>> - multi-modules sites
> >>> - content generation from sources (javadoc, jxr, plugin documentation)
> >>> Did I miss something?
> >> 
> >> Both of these are in the top level POM:
> >> http://svn.apache.org/viewvc/continuum/trunk/pom.xml?revision=1428315&vie
> >> w=m arkup
> >> 
> >> It was reduced to project-info-reports and javadoc:aggregate +
> >> jxr:aggregate (+tests)
> >> 
> >> The multi-module site uses the "site site:stage scm-publish:publish-scm"
> >> technique, while continuum-docs and the main site just use site-deploy.
> >> 
> >> - Brett
> >> 
> >> --
> >> Brett Porter
> >> brett@apache.org
> >> http://brettporter.wordpress.com/
> >> http://au.linkedin.com/in/brettporter
> >> http://twitter.com/brettporter
> >> 
> >> 
> >> 
> >> 
> >> 
> >> 
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: dev-help@maven.apache.org
> > 
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> 
> --
> Brett Porter
> brett@apache.org
> http://brettporter.wordpress.com/
> http://au.linkedin.com/in/brettporter
> http://twitter.com/brettporter
> 
> 
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Mime
View raw message