Remove Version and incompatible improvements? (was [FM3] Configuration API simplification)

On Tue, 2017-02-14 at 21:32 +0100, Daniel Dekany wrote: > I propose that in FM3 Configuration should only have two constructors: > >   Configuration(Version incompatibleImprovements) >   Configuration(Properties properties) > > and that it should not have a setIncompatibleImprovements(Version) >

Re: [FM3] Configuration API simplification

On Tue, Feb 14, 2017 at 3:32 PM, Daniel Dekany wrote: > I propose that in FM3 Configuration should only have two constructors: > > Configuration(Version incompatibleImprovements) > Configuration(Properties properties) Is it to make sure that users should set the version

[FM3] Configuration API simplification

I propose that in FM3 Configuration should only have two constructors: Configuration(Version incompatibleImprovements) Configuration(Properties properties) and that it should not have a setIncompatibleImprovements(Version) method. Because then it can be ensured that

Re: Gradle for FreeMarker, anyone? (Was: Maven for Freemarker)

Tuesday, February 14, 2017, 7:53:36 PM, Mauricio Nuñez wrote: > Hi, > > I have a question about this. With FM2, the ant script allows differents > combinations. I think this is not needed for FM3. Or we need to be aware > about specifics combinations of dependencies? This is related to drop >

Re: Gradle for FreeMarker, anyone? (Was: Maven for Freemarker)

Hi, I have a question about this. With FM2, the ant script allows differents combinations. I think this is not needed for FM3. Or we need to be aware about specifics combinations of dependencies? This is related to drop support to older dependencies in FM3. Regards, Mauricio 2017-02-14 15:39

Re: Gradle for FreeMarker, anyone? (Was: Maven for Freemarker)

Yeah that would be my bad :) We've been doing heart surgery in the OFBiz project that got me delayed a bit. Anyway, to share what I've worked on so far, I realized most of the complexity in the script is in the "compile" target. There is _lots_ of shuffling files around and a good amount of

Re: New committer: Woonsan Ko

Hi folks, Thank you so much for your warm welcomes! It is a great opportunity for me to collaborate with a great open source software project in a great community. I'd like to do my best together with you to grow it. Sincerely yours, Woonsan Ko On Tue, Feb 14, 2017 at 3:59 AM, Michael Brohl

Re: Gradle for FreeMarker, anyone? (Was: Maven for Freemarker)

Any update regarding the Gadle-isation? Monday, January 2, 2017, 9:36:03 AM, Taher Alkhateeb wrote: > Hi Daniel, > > Okay things are much more clear thank you! > > With respect to the repository, I guess there are two uses of the word > repository. On one hand it is what you meant (a place to

Re: New committer: Woonsan Ko

Welcome Woonsan! Jacopo On Sun, Feb 12, 2017 at 7:42 PM, Daniel Dekany wrote: > The Project Management Committee (PMC) for Apache FreeMarker > (incubating) has invited Woonsan Ko to become a committer and we are > pleased to announce that he has accepted. > > Woonsan Ko

Re: New committer: Woonsan Ko

Congrats On Feb 14, 2017 11:13 AM, "Jacques Le Roux" wrote: > Welcome Woonsan! > > Jacques > > > Le 12/02/2017 à 19:42, Daniel Dekany a écrit : > >> The Project Management Committee (PMC) for Apache FreeMarker >> (incubating) has invited Woonsan Ko to become a

Re: New committer: Woonsan Ko

Welcome Woonsan! Jacques Le 12/02/2017 à 19:42, Daniel Dekany a écrit : The Project Management Committee (PMC) for Apache FreeMarker (incubating) has invited Woonsan Ko to become a committer and we are pleased to announce that he has accepted. Woonsan Ko has been an active FreeMarker user