springframework-developer

[Springframework-developer] DocBook: 'method' and c'lassname' tags work for html, but not 'property'

[Colin S. <col...@ex...>]

I was just doing some more proofing on the manual, and noticed something 
weird. Most people seem to have used the <literal> tag everywhere for 
classnames, methods, and properties, but I actually tried to use 
<classname>, <method>, and <property>. All seems ok for the PDF, but I 
notice for the generated html, that <property> does not seem to have any 
effect.

Not that big a deal I guess, but people should stay away from the 
<property> tag for now. I will change all my usages to <method> instead...

Re: [Springframework-developer] DocBook: 'method' and c'lassname' tags work for html, but not 'property'

[Luke T. <ne...@fr...>]

I had a bizarre experience with the automated doc generation recently... 
The build broke (along with various other things on the server) and when 
I checked it out I found that my entire /opt paritition had been filled 
up with the single HTML documentation page - one 16 GB html file! 
Must've got stuck in a loop somewhere. Anyone noticed anything like that 
happening with docbook before?

Luke.

Colin Sampaleanu wrote:
> I was just doing some more proofing on the manual, and noticed something 
> weird. Most people seem to have used the <literal> tag everywhere for 
> classnames, methods, and properties, but I actually tried to use 
> <classname>, <method>, and <property>. All seems ok for the PDF, but I 
> notice for the generated html, that <property> does not seem to have any 
> effect.
> 
> Not that big a deal I guess, but people should stay away from the 
> <property> tag for now. I will change all my usages to <method> instead...
> 
> 
> 
> 


-- 
  Luke Taylor.                      Monkey Machine Ltd.
  PGP Key ID: 0x57E9523C            http://www.monkeymachine.ltd.uk

Re: [Springframework-developer] DocBook: 'method' and c'lassname' tags work for html, but not 'property'

[Colin S. <col...@ex...>]

Remind me not to generate docs on the production server :-)

Is it working now for you?

Luke Taylor wrote:

> I had a bizarre experience with the automated doc generation 
> recently... The build broke (along with various other things on the 
> server) and when I checked it out I found that my entire /opt 
> paritition had been filled up with the single HTML documentation page 
> - one 16 GB html file! Must've got stuck in a loop somewhere. Anyone 
> noticed anything like that happening with docbook before?
>
> Luke.
>
> Colin Sampaleanu wrote:
>
>> I was just doing some more proofing on the manual, and noticed 
>> something weird. Most people seem to have used the <literal> tag 
>> everywhere for classnames, methods, and properties, but I actually 
>> tried to use <classname>, <method>, and <property>. All seems ok for 
>> the PDF, but I notice for the generated html, that <property> does 
>> not seem to have any effect.
>>
>> Not that big a deal I guess, but people should stay away from the 
>> <property> tag for now. I will change all my usages to <method> 
>> instead...
>>
>>
>>
>>
>
>

Re: [Springframework-developer] DocBook: 'method' and c'lassname' tags work for html, but not 'property'

[<tho...@tr...>]

I made one change at one point that caused the html generation to spin in what
seemed to be an endless loop. I killed the process so I don't know if it would
have filled my disk or not.  The same docs ran fine in the pdf generator.  I
think Colin got hit by this change as well and got an out of memory error after
some time.

Thomas

Quoting Luke Taylor <ne...@fr...>:

> I had a bizarre experience with the automated doc generation recently... 
> The build broke (along with various other things on the server) and when 
> I checked it out I found that my entire /opt paritition had been filled 
> up with the single HTML documentation page - one 16 GB html file! 
> Must've got stuck in a loop somewhere. Anyone noticed anything like that 
> happening with docbook before?
> 
> Luke.
> 
> Colin Sampaleanu wrote:
> > I was just doing some more proofing on the manual, and noticed something 
> > weird. Most people seem to have used the <literal> tag everywhere for 
> > classnames, methods, and properties, but I actually tried to use 
> > <classname>, <method>, and <property>. All seems ok for the PDF, but I 
> > notice for the generated html, that <property> does not seem to have any 
> > effect.
> > 
> > Not that big a deal I guess, but people should stay away from the 
> > <property> tag for now. I will change all my usages to <method> instead...
> > 
> > 
> > 
> > 
> 
> 
> -- 
>   Luke Taylor.                      Monkey Machine Ltd.
>   PGP Key ID: 0x57E9523C            http://www.monkeymachine.ltd.uk
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux Tutorials
> Free Linux tutorial presented by Daniel Robbins, President and CEO of
> GenToo technologies. Learn everything from fundamentals to system
> administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>