Please stop removing the "headers" from the reply body (for example,
I've retained the "On 6/22/08, Torsten Curdt <[EMAIL PROTECTED]>
wrote:" text below). Removing those makes conversations quite hard to
follow, especially the longer ones.

On 6/22/08, Torsten Curdt <[EMAIL PROTECTED]> wrote:
> >
> > >
> > > > Added note that those classes are not part of the public API
> > > >
> > > >
> > > <snip/>
> > >
> > > I'm not sure how we'd consider breakage though (does that mean we'll
> > > be lax with changes to these classes?).
> > >
> > > I mention this because there are a couple of classes in [scxml] as
> > > well that fit this bill and we could add similar warnings there. But
> > > these warnings clearly have no merit when it comes to clirr or
> > > jardiff, so we must be assuming that everyone reads Javadocs very
> > > carefully ;-)
> > >
> >
> > The maven plugin for clirr does have an "excludes" parameter.  We
> > could come up with a naming convention for non-public classes that we
> > don't want folks using (someone suggested underscores or something)
> > and set that up in the parent pom.xml file.
> >
>
>  Underscore? *shudder*
>  What about a package name called "internal"
>
<snip/>

Yup, a reserved package name makes sense ("internal" is fine, and
atleast a couple of Apache projects use it). If there aren't any
objections, we should document this and start using the convention.

-Rahul


>
>  cheers
>  --
>  Torsten
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to