As a workaround can we make a clean docs build each time? How long would 
this take? Is it less than a minute?

On 13/07/10 07:48, Jody Garnett wrote:
> Okay so hudson is down; and I think it may be a configuration issue?
>
> While we can comment docs out of the build again I would like to see this 
> fixed.
>
> Jody
>
> On 13/07/2010, at 12:05 AM, Jody Garnett wrote:
>
> So here is the deal - it looks like the build is failing when it trips up 
> trying to compile only files that have changed.
> It assumes the full doc tree (or whatever that is) is present already ...
>
> I have added the following parameters:
>
> -a (generating all the content every time)
> -E  (generating the doctree stuff every time)
>
> I hope with this change that "docs" can stay in the build.
>
> I have been migrating the Java example code out of demo/example into docs. 
> The idea is to have just the doc folder be standalone (and not have relative 
> paths into other modules). When this is finished there will be no more need 
> for demo/example and we can remove that project.
>
> Jody
>
>
>
> On 12/07/2010, at 11:27 PM, Hudson wrote:
>
> sphinx:
>      [exec] Making output directory...
>      [exec] Running Sphinx v0.6.1
>      [exec] loading pickled environment... failed: [Errno 2] No such file or 
> directory: 
> '<http://hudson.opengeo.org/hudson/job/geotools-trunk/ws/gt_trunk/docs/target/index/doctrees/environment.pickle'>
>      [exec] building [html]: targets for 1 source files that are out of date
>      [exec] updating environment: 1 added, 0 changed, 0 removed
>      [exec] reading sources... [100%] index
>
>      [exec] looking for now-outdated files... none found
>      [exec] pickling environment... done
>      [exec] checking consistency... done
>      [exec] preparing documents... done
>      [exec] writing output... [100%] index
>
>      [exec] writing additional files... genindex search
>      [exec] copying static files... done
>      [exec] dumping search index... done
>      [exec] dumping object inventory... done
>      [exec] build succeeded.
>
> sphinx:
>      [exec] Making output directory...
>      [exec] Running Sphinx v0.6.1
>      [exec] Exception occurred:
>      [exec]   File 
> "/usr/lib/python2.4/site-packages/Sphinx-0.6.1-py2.4.egg/sphinx/errors.py", 
> line 31, in __init__
>      [exec]     super(ExtensionError, self).__init__(message)
>      [exec] TypeError: super() argument 1 must be type, not classobj
>      [exec] The full traceback has been saved in /tmp/sphinx-err-89LUSy.log, 
> if you want to report the issue to the author.
>      [exec] Please also report this if it was a user error, so that a better 
> error message can be provided next time.
>      [exec] Send reports to 
> sphinx-...@googlegroups.com<mailto:sphinx-...@googlegroups.com>. Thanks!
>
>
>


-- 
Ben Caradoc-Davies <ben.caradoc-dav...@csiro.au>
Software Engineering Team Leader
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre

------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Geotools-devel mailing list
Geotools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to