I think that could make sense, especially for many that connect Tamaya to other (mostly Apache) projects like Camel or Commons Configuration.
We spoke about separating other efforts (e.g. support for Units via JSR 363 or Monetary configuration if there are business cases for it based on JSR 354) but most existing modules on that list fall more or less under Apache, so it could be good t simply put them in a separate repo and also decouple their development lifecycles (i.E. not a single Jenkins/Maven build to "build them all";-) Werner On Thu, Aug 18, 2016 at 12:39 AM, John D. Ament <[email protected]> wrote: > For the extra modules, do we want a separate git repo under ASF and if so > what to name it? I can put in the request. > > John > > On Wed, Aug 17, 2016 at 6:18 PM Anatole Tresch <[email protected]> wrote: > > > Hi all > > > > I have put together a short overview about the current > > Tamaya Module > > s, including my personal recommendation, which modules should stay in > the > > core project and which modules may be moved into a separate repo. I also > > added s small note on the most important task, which IMO have to be done > > per module. > > > > > > https://docs.google.com/spreadsheets/d/1aBGG7h7okdiW0wzCKa7VfuQY8BLH6 > q4-iIfg7FOo67A/edit?usp=sharing > > > > > > J Anatole > > >
