[jira] [Created] (SLING-7190) i18n translations not updated unless bundle is restarted

Shivendra Vikram Srinet created SLING-7190: -- Summary: i18n translations not updated unless bundle is restarted Key: SLING-7190 URL: https://issues.apache.org/jira/browse/SLING-7190 Project:

Re: Sling build broken for me.

On Wed, Oct 11, 2017 at 6:07 PM, Robert Munteanu wrote: > On Wed, 2017-10-11 at 16:04 +0200, Karl Pauls wrote: >> On Wed, Oct 11, 2017 at 3:46 PM, Ian Boston wrote: >> > Hi, >> > >> > On 11 October 2017 at 11:21, Robert Munteanu >> >

RE: [VOTE] Release Apache Sling Discovery Oak 1.2.22

+1

RE: [VOTE] Release Apache Sling Maven Sling Plugin 2.3.4

+1

[VOTE] Release Apache Sling Maven Sling Plugin 2.3.4

Hi, We solved 1 issues in this release: https://issues.apache.org/jira/projects/SLING/versions/12341647 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1801/ You can use this UNIX script to download the release and verify the signatures:

Re: Sling build broken for me.

On Wed, 2017-10-11 at 16:04 +0200, Karl Pauls wrote: > On Wed, Oct 11, 2017 at 3:46 PM, Ian Boston wrote: > > Hi, > > > > On 11 October 2017 at 11:21, Robert Munteanu > > wrote: > > > > > Hi Ian, > > > > > > On Wed, 2017-10-11 at 10:47 +0100, Ian Boston

[jira] [Updated] (SLING-7189) Misleading Artifact Coordinates message for ResourceResolverType.JCR_OAK

[ https://issues.apache.org/jira/browse/SLING-7189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert updated SLING-7189: -- Component/s: (was: Apache Sling Testing Rules) Testing > Misleading

[jira] [Resolved] (SLING-7189) Misleading Artifact Coordinates message for ResourceResolverType.JCR_OAK

[ https://issues.apache.org/jira/browse/SLING-7189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert resolved SLING-7189. --- Resolution: Fixed Assignee: Stefan Seifert Fix Version/s: Testing Sling Mock

[jira] [Updated] (SLING-7189) Misleading Artifact Coordinates message for ResourceResolverType.JCR_OAK

[ https://issues.apache.org/jira/browse/SLING-7189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jens Lauterbach updated SLING-7189: --- Attachment: sling-7189.patch Added patch to fix the issue. > Misleading Artifact Coordinates

Re: Sling build broken for me.

On Wed, Oct 11, 2017 at 3:46 PM, Ian Boston wrote: > Hi, > > On 11 October 2017 at 11:21, Robert Munteanu wrote: > >> Hi Ian, >> >> On Wed, 2017-10-11 at 10:47 +0100, Ian Boston wrote: >> > Hi, >> > Could be me. >> > I do mvn clean install on a clean Sling

[jira] [Updated] (SLING-7189) Misleading Artifact Coordinates message for ResourceResolverType.JCR_OAK

[ https://issues.apache.org/jira/browse/SLING-7189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jens Lauterbach updated SLING-7189: --- Priority: Trivial (was: Minor) > Misleading Artifact Coordinates message for

Re: Sling build broken for me.

Hi, On 11 October 2017 at 11:21, Robert Munteanu wrote: > Hi Ian, > > On Wed, 2017-10-11 at 10:47 +0100, Ian Boston wrote: > > Hi, > > Could be me. > > I do mvn clean install on a clean Sling checkout with a clean maven > > repo > > and I get failiures to download

[jira] [Updated] (SLING-7189) Misleading Artifact Coordinates message for ResourceResolverType.JCR_OAK

[ https://issues.apache.org/jira/browse/SLING-7189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jens Lauterbach updated SLING-7189: --- Description: When you create a {{SlingContext}} using {{ResourceResolverType.JCR_OAK}} you

[jira] [Updated] (SLING-7189) Misleading Artifact Coordinates message for ResourceResolverType.JCR_OAK

[ https://issues.apache.org/jira/browse/SLING-7189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jens Lauterbach updated SLING-7189: --- Description: When you create a {{SlingContext}} using {{ResourceResolverType.JCR_OAK}} you

[jira] [Updated] (SLING-7189) Misleading Artifact Coordinates message for ResourceResolverType.JCR_OAK

[ https://issues.apache.org/jira/browse/SLING-7189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jens Lauterbach updated SLING-7189: --- Attachment: sling-7189-code.zip Added demo code. > Misleading Artifact Coordinates message

[jira] [Updated] (SLING-7189) Misleading Artifact Coordinates message for ResourceResolverType.JCR_OAK

[ https://issues.apache.org/jira/browse/SLING-7189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jens Lauterbach updated SLING-7189: --- Description: When you create a {{SlingContext}} using {{ResourceResolverType.JCR_OAK}} you

[jira] [Updated] (SLING-7189) Misleading Artifact Coordinates message for ResourceResolverType.JCR_OAK

[ https://issues.apache.org/jira/browse/SLING-7189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jens Lauterbach updated SLING-7189: --- Description: When you create a {{SlingContext}} using {{ResourceResolverType.JCR_OAK}} you

[jira] [Created] (SLING-7189) Misleading Artifact Coordinates message for ResourceResolverType.JCR_OAK

Jens Lauterbach created SLING-7189: -- Summary: Misleading Artifact Coordinates message for ResourceResolverType.JCR_OAK Key: SLING-7189 URL: https://issues.apache.org/jira/browse/SLING-7189 Project:

[jira] [Created] (SLING-7188) Sling post servlet should be logging more in debug / trace

Nicolas Peltier created SLING-7188: -- Summary: Sling post servlet should be logging more in debug / trace Key: SLING-7188 URL: https://issues.apache.org/jira/browse/SLING-7188 Project: Sling

Re: [sling-site] branch master updated: Avoid encoding issues

Hi Julian, On Wed, Oct 11, 2017 at 1:26 PM, Julian Sedding wrote: > ...I'll try reverting this fix and set AddDefaultCharset utf-8 in > .htaccess instead IMO it's better to avoid unicode chars in code, and those templates are code so my preference is to keep \u00a9 for

Re: [sling-site] branch master updated: Avoid encoding issues

Hi Bertrand I'll try reverting this fix and set AddDefaultCharset utf-8 in .htaccess instead. I believe that will be more convenient down the road (if it works). Regards Julian On Tue, Oct 10, 2017 at 11:51 AM, wrote: > This is an automated email from the ASF

Re: Depending on Oak 1.7.x

On 11 October 2017 at 11:25, Robert Munteanu wrote: > On Wed, 2017-10-11 at 11:16 +0100, Ian Boston wrote: > > Hi, > > Switching to depend on Oak 1.7 requires upgrading oak-server to use > > 1.7 or > > later. > > There has been some incompatible changes at a bundle level and

Re: Depending on Oak 1.7.x

On Wednesday 11 October 2017 12:15:25 Konrad Windszus wrote: > Adjusting the dependency implicitly has an effect on the import-version > range being calculated by bnd for Sling bundles depending on Oak. Therefore > depending on 1.7 most probably prevents the same Sling bundle from running > with

Re: Depending on Oak 1.7.x

On Wed, 2017-10-11 at 11:16 +0100, Ian Boston wrote: > Hi, > Switching to depend on Oak 1.7 requires upgrading oak-server to use > 1.7 or > later. > There has been some incompatible changes at a bundle level and > package > level between 1.6 and 1.7 so its not as simple has changing the >

Re: Sling build broken for me.

Hi Ian, On Wed, 2017-10-11 at 10:47 +0100, Ian Boston wrote: > Hi, > Could be me. > I do mvn clean install on a clean Sling checkout with a clean maven > repo > and I get failiures to download slingfeature:9-SNAPSHOT required by > an IT > test sample. This happens before the reactor starts.

Re: [RT] Updates to the provisioning model

Hi Carsten, can you provide some insights on timing wrt Felix Snapshot dependencies. When we plugged together the demo we still had a few dependencies on unreleased artifacts for the OSGi R7 work. I would rather see this change happening yesterday than tomorrow to start working on how the model

Re: Depending on Oak 1.7.x

Hi, Switching to depend on Oak 1.7 requires upgrading oak-server to use 1.7 or later. There has been some incompatible changes at a bundle level and package level between 1.6 and 1.7 so its not as simple has changing the versions. For instance oak-api bundle didnt existi in 1.6 and NodeAggregator

Re: Depending on Oak 1.7.x

Adjusting the dependency implicitly has an effect on the import-version range being calculated by bnd for Sling bundles depending on Oak. Therefore depending on 1.7 most probably prevents the same Sling bundle from running with Oak 1.6. We had this discussion before and basically we were advised

Re: Depending on Oak 1.7.x

Having said that, the only bullet to bite when switching to Oak 1.7.x is increased maintenance effort: the affected bundles will become backwards incompatible wrt Oak 1.6.x and if they need to be patched it would not be possible to do so in trunk anymore. Cheers, Stefan On 11/10/17 12:03,

Re: Depending on Oak 1.7.x

Hi Ian, I don't see a problem with having a dependency on an unstable Oak 1.7.x in Sling. Actual deployments can still, independent of this, make a call whether or not they want to actually run on Oak 1.7.x or wait for Oak 1.8 (which is advisable). IMO having this dependency doesn't imply on

Depending on Oak 1.7.x

Hi, Oak 1.7.x is Oak unstable release branch working towards 1.8. I have a feature in SLING-7140 that is blocked by an API change in Oak present in 1.8-SNAPSHOT and available as an unmerged but tested patch to Oak 1.6.x. The Oak team are unwilling merge the patch to 1.6 and have asked that Sling

Sling build broken for me.

Hi, Could be me. I do mvn clean install on a clean Sling checkout with a clean maven repo and I get failiures to download slingfeature:9-SNAPSHOT required by an IT test sample. This happens before the reactor starts. If I fix that by using slingfeature:9 I then get 11 test failures in commons.log