Bug#308913: my mistake : (

[Wolfgang Baer]

reassign 308913 gjdoc
merge 308913 306371
tags 308913 fixed-upstream
stop

ms419@freezone.co.uk wrote:
>> No - it was not fixed with gjdoc 0.74 - it was fixed two days after
>> the release so atm only in cvs. BTW, if you have a look at gjdoc bugs,
>> you can see that the bug is not yet closed!
> 
> 
> Oops - my mistake - I was sure that Sable & gjdoc 0.7.4-1 successfully 
> built Lucene javadocs, while Kaffe failed - so I assumed that Kaffe must 
> use an older version of gjdoc than 
> /usr/share/java/gnu-classpath-tools-gjdoc.jar
> 
> However, on double checking I discover that both Kaffe & Sable succeed 
> with /usr/share/java/gnu-classpath-tools-gjdoc.jar built from cvs, while 
> both fail with gjdoc 0.7.4-1
> 
> Sorry - please excuse my mistake!

No problem Jack - that happens !
> 
>> Given the information above - this seems to be the same bug as 306371
>> of gjdoc. Do you agree? If yes I will reassign this bug to gjdoc and
>> merge it with the other one.

Well gjdoc 0.7.5 released today - so with the next upload this
bug and 306371 should be fixed.

 From upstream changelog:

* Unavailable external documentation sets are handled gracefully now.
   Thanks to Jack Bates for reporting this.


Wolfgang