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:;>>
> >
> >
> >
> >
>
>
> --
> Russell Jurney twitter.com/rjurney russell.jurney@gmail.com
> datasyndrome.com
>
--
Niclas Hedhman, Software Developer - New Energy for Java