The reason I defended placing those exceptions directly in the
"org.apache.velocity" package is just ease of use.
IMO, _if_ you have a framework which functionality can be typical
achieved just trough a small number of classes, you should place
those classes on the "root" of the library (being Velocity root
at "org.apache.velocity").
Following this logic, these Exceptions should be placed there
just because the correct use of the library also depends on them.
Now, noticed my "_if_" above. The reason I just described might
not be the only one. It is just something to consider.
Have fun,
Paulo Gaspar
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Daniel Rall
>
>
> "Geir Magnusson Jr." <[EMAIL PROTECTED]> writes:
>
> > Paulo Gaspar wrote:
> > >
> > > Why not placing user Exceptions and other "most used" classes
> directly on
> > > org.apache.velocity?
> >
> > I thought about that at first, but figured it would help organize a
> > bit. Not sure what the convention is around here. I just wanted to get
> > them out of the bowels...
>
> IMHO, exceptions should be placed in the same package as classes that
> use them the most. If no package looks to be a likely candidate, then
> go with an exception package.
> --
>
> Daniel Rall <[EMAIL PROTECTED]>
>
