>
> While I agree that commons-collection-2.0 has been in cvs for 5 months, it
> was not previously needed to run xdoclet in jboss or the other
> (commercial)
> project I experienced these problems in. In both cases I has to add
> commons-collection to the build classpath. The xdoclet versions
lto:[EMAIL PROTECTED]]On Behalf Of Marcin
> Gryszkalis
> Sent: 20. november 2002 07:48
> To: [EMAIL PROTECTED]
> Subject: Re: [Xdoclet-devel] Big problems with 1.2 cvs version.
>
>
> > The problem with fqcn occurred with a fresh checkout today of jboss head
> > (cvs
The problem with fqcn occurred with a fresh checkout today of jboss head
(cvs co jboss-head) while building the server module. The problems occur
in several files, but only when the entire fileset is processed at once.
If files are processed one at a time the interface seems to be generated
corre
On 2002.11.19 20:56:33 -0500 Aslak Hellesøy wrote:
>
>
> > -Original Message-
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On Behalf Of David
> > Jencks
> > Sent: 20. november 2002 02:25
> > To: xdoclet-devel
> > Subject: [
I'm finding a bunch of very broken behavior in the 1.2 cvs version:
--Package level classes in the same file as a public class break xjavadoc
parsing (I wrote a sample to break the build to demonstrate this, but no
one has looked into it, except to remove the sample)
--Classes are not always impo