> On Jun 21, 2016, at 12:58 AM, Jörg Schaible <joerg.schai...@bpm-inspire.com> > wrote: > > Hi Jochen, > > Jochen Wiedmann wrote: > >> On Tue, Jun 21, 2016 at 9:12 AM, Jörg Schaible >> <joerg.schai...@bpm-inspire.com> wrote: >> >>> That depends. If some packages of the current CM should stay as own >>> component in Commons, these packages have to be identified. >> >> Whoever would support such a lunacy? Either CM moves entirely, or not at >> all. > > If the new Commons Components have been identified, we can have a vote. Then > we'll see what the majority want. All I can say now is that we have currenty > no consensus about anything. Some of the stuff in CM is certainly common > enough to build a valid Commons component. >
Maybe. That could depend on whether there is anyone at Commons that would want to participate in the component. Another option is to follow the pattern used by httpclient. I believe they took the last version of commons httpclient and left a pointer to it in their new web site. But what followed as a TLP was completely different and wasn’t binary compatible. The community seemed to be completely fine with that. Ralph --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
