Re: Updating our parent pom

I have been following supporting Thymeleaf as an additional scripting engine supported by Sling. I just wanted to understand the difference between sightly (AEM HTL) with this scripting support and what is the difference PRIMARY between these two scripting languages?. Any help is really

Re: Updating our parent pom

On Monday 18 July 2016 11:11:25 Carsten Ziegeler wrote: > > On Thursday 14 July 2016 21:43:45 Carsten Ziegeler wrote: [...] > > I've updated the parent pom as outlined above, including #11. > > It would be great if everyone can have a look before we start a release LGTM, building Scripting

Re: Updating our parent pom

> On 14 Jul 2016, at 21:43, Carsten Ziegeler wrote: > > Hi, > > looking at our parent pom, we have there some really really old > dependencies. The reasoning behind this is that we usually try to use > the minimal possible version for a dependency. However, for some

Re: Updating our parent pom

On Mon, 2016-07-18 at 11:23 +0200, Carsten Ziegeler wrote: > > > > On Mon, 2016-07-18 at 11:11 +0200, Carsten Ziegeler wrote: > > > > > > > > On Thursday 14 July 2016 21:43:45 Carsten Ziegeler wrote: > > > > > Hi, > > > > > > > > > > looking at our parent pom, we have there some really really >

Re: Updating our parent pom

>> On Thursday 14 July 2016 21:43:45 Carsten Ziegeler wrote: >>> Hi, >>> >>> looking at our parent pom, we have there some really really old >>> dependencies. The reasoning behind this is that we usually try to use >>> the minimal possible version for a dependency. However, for some things >>>

Re: Updating our parent pom

> On Mon, 2016-07-18 at 11:11 +0200, Carsten Ziegeler wrote: >>> >>> On Thursday 14 July 2016 21:43:45 Carsten Ziegeler wrote: Hi, looking at our parent pom, we have there some really really old dependencies. The reasoning behind this is that we usually try to use the

Re: Updating our parent pom

On Mon, 2016-07-18 at 11:11 +0200, Carsten Ziegeler wrote: > > > > On Thursday 14 July 2016 21:43:45 Carsten Ziegeler wrote: > > > Hi, > > > > > > looking at our parent pom, we have there some really really old > > > dependencies. The reasoning behind this is that we usually try to > > > use > >

Re: Updating our parent pom

> On Thursday 14 July 2016 21:43:45 Carsten Ziegeler wrote: >> Hi, >> >> looking at our parent pom, we have there some really really old >> dependencies. The reasoning behind this is that we usually try to use >> the minimal possible version for a dependency. However, for some things >> newer

Re: Updating our parent pom

On Fri, 2016-07-15 at 10:34 +0200, Bertrand Delacretaz wrote: > On Thu, Jul 14, 2016 at 9:43 PM, Carsten Ziegeler rg> wrote: > > ...looking at our parent pom, we have there some really really old > > dependencies > > +1 for the updates that you mentioned, as long as our

Re: Updating our parent pom

On Thursday 14 July 2016 21:43:45 Carsten Ziegeler wrote: > Hi, > > looking at our parent pom, we have there some really really old > dependencies. The reasoning behind this is that we usually try to use > the minimal possible version for a dependency. However, for some things > newer versions

Re: Updating our parent pom

> On Thu, Jul 14, 2016 at 9:43 PM, Carsten Ziegeler > wrote: >> ...looking at our parent pom, we have there some really really old >> dependencies > > +1 for the updates that you mentioned, as long as our full build with > integration tests still works after that. >

Re: Updating our parent pom

On Thu, Jul 14, 2016 at 9:43 PM, Carsten Ziegeler wrote: > ...looking at our parent pom, we have there some really really old > dependencies +1 for the updates that you mentioned, as long as our full build with integration tests still works after that. -Bertrand

Re: Updating our parent pom

Hi, >> 9. Add the bnd maven plugin 3.2.0 >> (see https://github.com/bndtools/bnd/tree/master/maven/bnd-maven-plugin) >> This plugin is newer than the maven bundle plugin and closer to bnd >> change. So we can start using this in our modules. > > we should make clear how to use bnd.bnd files. Do

Re: Updating our parent pom

On Thursday 14 July 2016 21:43:45 Carsten Ziegeler wrote: > Hi, Hi Carsten, > looking at our parent pom, we have there some really really old > dependencies. The reasoning behind this is that we usually try to use > the minimal possible version for a dependency. However, for some things > newer

RE: Updating our parent pom

+1 >-Original Message- >From: Carsten Ziegeler [mailto:cziege...@apache.org] >Sent: Thursday, July 14, 2016 9:44 PM >To: Sling Developers >Subject: Updating our parent pom > >Hi, > >looking at our parent pom, we have there some really really old >dependencies. The reasoning behind this is