If you change the package name it will force anyone who has customized it to make code changes. Their may not be anybody but I’m not a big fan of taking the chance for so little benefit.
Ralph On Sep 9, 2014, at 4:31 PM, Gary Gregory <[email protected]> wrote: > Hm... I wonder if changing the Maven artifact ID from log4j-flume-ng to > log4j-flume will cause some jar hell problem since we are not also renaming > the package. > > Gary > > On Tue, Sep 9, 2014 at 5:52 PM, Ralph Goers <[email protected]> > wrote: > Yeah - I dropped the OG version a long time ago. The only places I see > Flume-NG still used in the Flume project are on the wiki - > https://cwiki.apache.org/confluence/display/FLUME/Flume+NG, and > https://cwiki.apache.org/confluence/display/FLUME/Getting+Started. > > Ralph > > > On Sep 9, 2014, at 1:50 PM, Gary Gregory <[email protected]> wrote: > >> Can we drop the "NG" from the module name now? >> >> Gary >> >> -- >> E-Mail: [email protected] | [email protected] >> Java Persistence with Hibernate, Second Edition >> JUnit in Action, Second Edition >> Spring Batch in Action >> Blog: http://garygregory.wordpress.com >> Home: http://garygregory.com/ >> Tweet! http://twitter.com/GaryGregory > > > > > -- > E-Mail: [email protected] | [email protected] > Java Persistence with Hibernate, Second Edition > JUnit in Action, Second Edition > Spring Batch in Action > Blog: http://garygregory.wordpress.com > Home: http://garygregory.com/ > Tweet! http://twitter.com/GaryGregory
