Hi Stephen, I do agree, that this would be the time to change the project's name, also having in mind that version 2 could be the one, that receives a popularity boost. But (regardless of my personal opinion on that) ...
.. I suspect renaming the project would take at least two weeks, if not more. We could do it yes, but I fear, we simply have more urgent matters to address for the foreseeable future (this year). Cheers, Andi On 2019/03/29 07:54:05, Stephen Cameron <steve.cameron...@gmail.com> wrote: > I'm not doing much programming these days, but did have a thought today > about name change, for what's it's worth, 'Apache Sisi'. Maybe 'yes yes' in > Spanish? > > Major change maybe good time to bump the old name? > > On Friday, March 29, 2019, Martin Grigorov <mgrigo...@apache.org> wrote: > > > Hi, > > > > On Thu, Mar 28, 2019 at 3:43 PM Rade, Joerg / Kuehne + Nagel / HAM GI-DP < > > joerg.r...@kuehne-nagel.com> wrote: > > > > > Hi Andi, > > > > > > my 2c: > > > > > > The move to Spring (Boot?) will very likely popularize the framework and > > > therefore is the right thing to do. > > > > > > I never really had an issue with JDO and found it's debugging output > > > helpful. I hope Hibernate can keep up with that. > > > > > > CMIIW: Spring's CDI relies on the ComponentScan (CS) at start up time and > > > does not allow for easy changes at runtime. > > > > > > > What kind of changes do you mean ? > > Spring will use component scan only if you tell it to do it. You can > > bootstrap the application from a @Configuration class(es) without using any > > stereotype annotations like @Component, @Service, etc. > > > > > > > But this is probably not an issue for existing applications, nor do most > > > web applications require such a feature. > > > > > > Years ago I saw CS entering a second round, ending with multiple > > instances > > > of Singletons - ROTFL. > > > Admittedly this was as well due to the size of the project (~ 1.5M LOC) > > > and excessive use of applicationContext.xml's - but hey: a basic > > constraint > > > was not enforced. > > > > > > I don't care too much about how the eventing mechanism of the framework > > is > > > implemented (same degree of ignorance as with persistence) as long as the > > > features are available ;-) > > > > > > After all: Apache projects are meritocratic societies - so go ahead and > > > keep up the good work! > > > > > > Thx -j > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Kühne + Nagel (AG & Co.) KG > > > Rechtsform: Kommanditgesellschaft, Bremen HRA 21928, USt-IdNr.: DE > > > 812773878. > > > Geschäftsleitung Kühne + Nagel (AG & Co.) KG: Holger Ketz (Vors. ), Tom > > > Ban, Martin Brinkmann, Matthias Knicky, Nicholas Minde, Johannes > > Trimborn, > > > Lars Wedel, Matthias Weiner. > > > Persönlich haftende Gesellschafterin: Kühne & Nagel A.G., Rechtsform: > > > Aktiengesellschaft nach luxemburgischem Recht, HR-Nr.: B 18745, > > > Geschäftsführendes Verwaltungsratsmitglied: Karl Gernandt. > > > Geschäftsleitung Region Europa: Dr. Hansjörg Rodi (Vors.), Mart Ambur, > > Tom > > > Ban, Dominic Edmonds, Thierry Held, Uwe Hött, Richard Huhn, Jan-Hendrik > > > Köstergarten, Heiko Schuhmacher. > > > > > > Wir arbeiten ausschließlich auf Grundlage der Allgemeinen Deutschen > > > Spediteurbedingungen 2017 (ADSp 2017). Hinweis: Die ADSp 2017 weichen in > > > Ziffer 23 hinsichtlich des Haftungshöchstbetrages für Güterschäden (§ 431 > > > HGB) vom Gesetz ab, indem sie die Haftung bei multimodalen Transporten > > > unter Einschluss einer Seebeförderung und bei unbekanntem Schadenort auf > > 2 > > > SZR/kg und im Übrigen die Regelhaftung von 8,33 SZR/kg zusätzlich auf > > 1,25 > > > Millionen Euro je Schadenfall sowie 2,5 Millionen Euro je > > Schadenereignis, > > > mindestens aber 2 SZR/kg, beschränken. Die ADSp sind auf unserer Webseite > > > als Download erhältlich. Auf Anfrage senden wir Ihnen diese auch gerne > > zu. > > > > > >
