incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Niclas Hedhman <nic...@hedhman.org>
Subject Re: apache package naming convention
Date Sat, 08 Aug 2015 04:41:01 GMT
By that notion, practically all incoming projects would be in non
org.apache namespaces, and that would be a different kind of detrimental
situation.

So, my(!) general recommendation has been; for any releases that maintain
100% compatibility, keep the namespace as before. But as soon as a major
(1.x -> 2.0) release is made, that the namespace is changing with it.

Doing a search/replace for "s/import datafu/import org.apache.datafu"
across N files (and you can provide the script) is not a big deal compared
to whatever other compatibility-breaking changes that are introduced in the
major upgrade.

But as Luciano says; The sooner, the better, as fewer people are impacted.

Niclas

On Sat, Aug 8, 2015 at 6:55 AM, Russell Jurney <russell.jurney@gmail.com>
wrote:

> Leave it datafu. The normal way of doing Java namespaces is terrible bloat,
> and the change would be breaking.
>
> On Friday, August 7, 2015, Luciano Resende <luckbr1975@gmail.com> wrote:
>
> > On Fri, Aug 7, 2015 at 3:16 PM, Matthew Hayes <
> > matthew.terence.hayes@gmail.com <javascript:;>> wrote:
> >
> > > Hi all,
> > >
> > > Roman Shaposhnik suggested I open a discussion on the following topic:
> > >
> > > For Apache DataFu, all of the Java classes are declared in a datafu.*
> > > namespace.  This has been the naming convention since the DataFu
> project
> > > started in 2010.  Since DataFu became part of the Apache incubation
> > > process, the topic has come up of moving all of the classes into a
> > > org.apache.datafu.* namespace.  This was first discussed in January
> 2014
> > > (see DATAFU-7) and most recently again in the past couple weeks.  The
> > > consensus at the time last year was that it would be a huge pain for
> > users
> > > and not worth the cost.  It would break any script out there currently
> > > using DataFu.  Also Jakob Homan and Russell Journey pointed out that
> this
> > > is just a convention and not all Apache projects follow it.  Since we
> > would
> > > like DataFu to graduate sometime soon it would be good to clarify what
> > the
> > > requirements are on package naming conventions before we do a release.
> > >
> > > Thoughts?
> > >
> > > Thanks,
> > > Matt
> > >
> >
> > Current statement on Incubator website
> >
> > http://incubator.apache.org/guides/mentor.html#repackaging
> >
> > But, if DataFu will do the repackaging, better sooner (before graduation)
> > then later.
> >
> >
> > --
> > Luciano Resende
> > http://people.apache.org/~lresende
> > http://twitter.com/lresende1975
> > http://lresende.blogspot.com/
> >
>
>
> --
> Russell Jurney twitter.com/rjurney russell.jurney@gmail.com
> datasyndrome.com
>



-- 
Niclas Hedhman, Software Developer
http://zest.apache.org - New Energy for Java

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message