Re: Jenkins build is still unstable: sling-launchpad-testing-1.8 #1439

It seems to be a problem with Sling's junit integration: see https://issues.apache.org/jira/browse/SLING-6750 Apache Jenkins Server wrote > See > > > -- Carsten Ziegeler Adobe Research Switzerland

[jira] [Created] (SLING-6750) NPE with TestContextRunListenerWrapper in WriteableResourcesTest

Carsten Ziegeler created SLING-6750: --- Summary: NPE with TestContextRunListenerWrapper in WriteableResourcesTest Key: SLING-6750 URL: https://issues.apache.org/jira/browse/SLING-6750 Project: Sling

[jira] [Resolved] (SLING-6748) Move ValuePreparer to the models API package

[ https://issues.apache.org/jira/browse/SLING-6748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson resolved SLING-6748. --- Resolution: Fixed moved in r1789419 > Move ValuePreparer to the models API package >

[jira] [Updated] (SLING-6748) Move ValuePreparer to the models API package

[ https://issues.apache.org/jira/browse/SLING-6748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-6748: -- Fix Version/s: Sling Models Impl 1.3.10 Sling Models API 1.3.4 > Move

[jira] [Assigned] (SLING-6748) Move ValuePreparer to the models API package

[ https://issues.apache.org/jira/browse/SLING-6748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson reassigned SLING-6748: - Assignee: Justin Edelson > Move ValuePreparer to the models API package >

[jira] [Created] (SLING-6749) Expose Sightly Filter Class

Michael Hodgdon created SLING-6749: -- Summary: Expose Sightly Filter Class Key: SLING-6749 URL: https://issues.apache.org/jira/browse/SLING-6749 Project: Sling Issue Type: Improvement

[jira] [Created] (SLING-6748) Move ValuePreparer to the models API package

Burkhard Pauli created SLING-6748: - Summary: Move ValuePreparer to the models API package Key: SLING-6748 URL: https://issues.apache.org/jira/browse/SLING-6748 Project: Sling Issue Type:

[jira] [Comment Edited] (SLING-6747) User Manager: Support setting nested user properties

[ https://issues.apache.org/jira/browse/SLING-6747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15947428#comment-15947428 ] Konrad Windszus edited comment on SLING-6747 at 3/29/17 4:25 PM: - The

[jira] [Commented] (SLING-6747) User Manager: Support setting nested user properties

[ https://issues.apache.org/jira/browse/SLING-6747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15947428#comment-15947428 ] Konrad Windszus commented on SLING-6747: The reason for that limitation is that

[jira] [Created] (SLING-6747) User Manager: Support setting nested user properties

Konrad Windszus created SLING-6747: -- Summary: User Manager: Support setting nested user properties Key: SLING-6747 URL: https://issues.apache.org/jira/browse/SLING-6747 Project: Sling Issue

[jira] [Resolved] (SLING-4547) JcrResourceBundle does not support multiple base names

[ https://issues.apache.org/jira/browse/SLING-4547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus resolved SLING-4547. Resolution: Fixed > JcrResourceBundle does not support multiple base names >

[jira] [Updated] (SLING-517) Improve i18n node types

[ https://issues.apache.org/jira/browse/SLING-517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-517: -- Component/s: i18n > Improve i18n node types > --- > > Key:

[jira] [Updated] (SLING-5741) discarding complete ResourceBundleCache in case of JSON dictionary

[ https://issues.apache.org/jira/browse/SLING-5741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-5741: --- Component/s: i18n > discarding complete ResourceBundleCache in case of JSON dictionary >

[jira] [Updated] (SLING-5708) discarding ResourceBundle of all locale

[ https://issues.apache.org/jira/browse/SLING-5708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-5708: --- Component/s: i18n > discarding ResourceBundle of all locale >

[jira] [Updated] (SLING-2536) JcrResourceBundle breaks the contract of getLocale

[ https://issues.apache.org/jira/browse/SLING-2536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-2536: --- Component/s: i18n > JcrResourceBundle breaks the contract of getLocale >

[jira] [Updated] (SLING-6382) JcrResourceBundle.getBaseBundleName() always returns null

[ https://issues.apache.org/jira/browse/SLING-6382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-6382: --- Component/s: i18n > JcrResourceBundle.getBaseBundleName() always returns null >

[jira] [Updated] (SLING-4944) JcrResourceBundleProvider: Potential race condition between setting the resourceResolver and using it

[ https://issues.apache.org/jira/browse/SLING-4944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-4944: --- Component/s: i18n > JcrResourceBundleProvider: Potential race condition between setting the

[jira] [Updated] (SLING-5816) Support both lower and upper case language and country code

[ https://issues.apache.org/jira/browse/SLING-5816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-5816: --- Component/s: i18n > Support both lower and upper case language and country code >

[jira] [Commented] (SLING-4547) JcrResourceBundle does not support multiple base names

[ https://issues.apache.org/jira/browse/SLING-4547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15947134#comment-15947134 ] Konrad Windszus commented on SLING-4547: Fixed in [r1789363|https://svn.apache.org/r1789363]. >

RE: [VOTE] Release Apache Sling File System Resource Provider 2.0.0, File System Resource Provider 1.3.0

>On Wednesday 29 March 2017 12:51:59 Stefan Seifert wrote: >> >> +1 (depends now on Jackrabbit, would prefer embedding >> >> org.apache.jackrabbit.util.ISO8601 like we do in other bundles, e.g. >> > >> >event) >> > >> >After having a closer look, I don't think it's worth the effort as there >>

[jira] [Updated] (SLING-4547) JcrResourceBundle does not support multiple base names

[ https://issues.apache.org/jira/browse/SLING-4547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-4547: --- Fix Version/s: i18n 2.5.10 > JcrResourceBundle does not support multiple base names >

[jira] [Updated] (SLING-4547) JcrResourceBundle does not support multiple base names

[ https://issues.apache.org/jira/browse/SLING-4547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-4547: --- Affects Version/s: i18n 2.5.8 > JcrResourceBundle does not support multiple base names >

RE: [VOTE] Release Apache Sling File System Resource Provider 2.0.0, File System Resource Provider 1.3.0

On Wednesday 29 March 2017 12:51:59 Stefan Seifert wrote: > >> +1 (depends now on Jackrabbit, would prefer embedding > >> org.apache.jackrabbit.util.ISO8601 like we do in other bundles, e.g. > > > >event) > > > >After having a closer look, I don't think it's worth the effort as there > >are >

Re: PaxExam based ITs create folders outside target

> On 29 Mar 2017, at 15:12, Oliver Lietz wrote: > > On Wednesday 29 March 2017 14:48:06 Oliver Lietz wrote: >> On Wednesday 29 March 2017 14:37:58 Konrad Windszus wrote: >>> This is still not 100% fixed. >>> The Jenkins Workspace still contains the folder >>>

[jira] [Commented] (SLING-6723) Make dependency to javax.jcr, jcr.contentloader and jcr.api optional

[ https://issues.apache.org/jira/browse/SLING-6723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15947082#comment-15947082 ] Carsten Ziegeler commented on SLING-6723: - The AbstractPostOperation is now free from those APIs

Re: PaxExam based ITs create folders outside target

On Wednesday 29 March 2017 14:48:06 Oliver Lietz wrote: > On Wednesday 29 March 2017 14:37:58 Konrad Windszus wrote: > > This is still not 100% fixed. > > The Jenkins Workspace still contains the folder > > https://builds.apache.org/job/sling-bundles-extensions-validation-core-1.8 > > / > >

[jira] [Assigned] (SLING-4547) JcrResourceBundle does not support multiple base names

[ https://issues.apache.org/jira/browse/SLING-4547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus reassigned SLING-4547: -- Assignee: Konrad Windszus > JcrResourceBundle does not support multiple base names >

[jira] [Resolved] (SLING-6746) Remove and ban maven-scr-plugin

[ https://issues.apache.org/jira/browse/SLING-6746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert resolved SLING-6746. --- Resolution: Fixed Completed: At revision: 1789357 i added this message to the ban: "Felix

[jira] [Assigned] (SLING-6746) Remove and ban maven-scr-plugin

[ https://issues.apache.org/jira/browse/SLING-6746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert reassigned SLING-6746: - Assignee: Stefan Seifert Summary: Remove and ban maven-scr-plugin (was: Additional

RE: [VOTE] Release Apache Sling File System Resource Provider 2.0.0, File System Resource Provider 1.3.0

>> +1 (depends now on Jackrabbit, would prefer embedding >> org.apache.jackrabbit.util.ISO8601 like we do in other bundles, e.g. >event) > >After having a closer look, I don't think it's worth the effort as there >are >more new dependencies (JCR, Vault, Guava). there is no dependency on guava

[jira] [Updated] (SLING-6746) Additional execution of maven-bundle-plugin:manifest is blanking out resources generated by maven-scr-plugin

[ https://issues.apache.org/jira/browse/SLING-6746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-6746: --- Fix Version/s: Parent 31 > Additional execution of maven-bundle-plugin:manifest is blanking

Re: PaxExam based ITs create folders outside target

On Wednesday 29 March 2017 14:37:58 Konrad Windszus wrote: > This is still not 100% fixed. > The Jenkins Workspace still contains the folder > https://builds.apache.org/job/sling-bundles-extensions-validation-core-1.8/ > ws/sling/repository/index/indexWriterDir/ outside of target. That folder >

[jira] [Commented] (SLING-6746) Additional execution of maven-bundle-plugin:manifest is blanking out resources generated by maven-scr-plugin

[ https://issues.apache.org/jira/browse/SLING-6746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15947047#comment-15947047 ] Carsten Ziegeler commented on SLING-6746: - We should not use the Felix SCR bnd plugin - we should

Re: [VOTE] Release Apache Sling File System Resource Provider 2.0.0, File System Resource Provider 1.3.0

On Wednesday 29 March 2017 11:04:04 Oliver Lietz wrote: > On Monday 27 March 2017 16:21:49 Stefan Seifert wrote: > > Hi, > > > > Apache Sling File System Resource Provider 2.0.0 (3 issues) > > https://issues.apache.org/jira/browse/SLING/fixforversion/12339777 > > +1 (depends now on Jackrabbit,

Re: PaxExam based ITs create folders outside target

This is still not 100% fixed. The Jenkins Workspace still contains the folder https://builds.apache.org/job/sling-bundles-extensions-validation-core-1.8/ws/sling/repository/index/indexWriterDir/ outside of target. That folder must have been created by PaxExam after I wiped out the workspace in

[jira] [Commented] (SLING-6746) Additional execution of maven-bundle-plugin:manifest is blanking out resources generated by maven-scr-plugin

[ https://issues.apache.org/jira/browse/SLING-6746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15947020#comment-15947020 ] Konrad Windszus commented on SLING-6746: Agreed, can you make the according changes in parent?

[jira] [Comment Edited] (SLING-6746) Additional execution of maven-bundle-plugin:manifest is blanking out resources generated by maven-scr-plugin

[ https://issues.apache.org/jira/browse/SLING-6746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15947012#comment-15947012 ] Stefan Seifert edited comment on SLING-6746 at 3/29/17 12:21 PM: - yes, we

[jira] [Commented] (SLING-6746) Additional execution of maven-bundle-plugin:manifest is blanking out resources generated by maven-scr-plugin

[ https://issues.apache.org/jira/browse/SLING-6746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15947012#comment-15947012 ] Stefan Seifert commented on SLING-6746: --- yes, we should remove maven-scr-plugin from parent - and it

[jira] [Commented] (SLING-6746) Additional execution of maven-bundle-plugin:manifest is blanking out resources generated by maven-scr-plugin

[ https://issues.apache.org/jira/browse/SLING-6746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15947004#comment-15947004 ] Konrad Windszus commented on SLING-6746: This was kind of unexpected. Then we should IMHO

[event] kafka-based sling.event.api implementation

Hi, The split of Sling event into an API and a Resource-based bundle will now ease other implementations than the current Resource-based one. I'll be starting to work on one such implementation that is going to be kafka based (perhaps split into a generic messaging and a specific kafka part):

[jira] [Commented] (SLING-6746) Additional execution of maven-bundle-plugin:manifest is blanking out resources generated by maven-scr-plugin

[ https://issues.apache.org/jira/browse/SLING-6746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15947000#comment-15947000 ] Stefan Seifert commented on SLING-6746: --- the solution should be to completely remove the

[jira] [Commented] (SLING-6746) Additional execution of maven-bundle-plugin:manifest is blanking out resources generated by maven-scr-plugin

[ https://issues.apache.org/jira/browse/SLING-6746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15946990#comment-15946990 ] Konrad Windszus commented on SLING-6746: [~sseif...@pro-vision.de] Can you have a look, since you

Re: Parent 30 breaks maven-scr-plugin

I found the culprit: It is https://github.com/apache/sling/commit/9b0c5e785554029de2cdf5ddc2549efe5b13e9a5 So the extra execution of maven-bundle-plugin:manifest is basically overwriting the service descriptors which are written with maven-scr-plugin with empty files. Those empty files end up

[jira] [Commented] (SLING-6723) Make dependency to javax.jcr, jcr.contentloader and jcr.api optional

[ https://issues.apache.org/jira/browse/SLING-6723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15946988#comment-15946988 ] Carsten Ziegeler commented on SLING-6723: - Absolutely, I'll make sure that these things are logged

[jira] [Created] (SLING-6746) Additional execution of maven-bundle-plugin:manifest is blanking out resources generated by maven-scr-plugin

Konrad Windszus created SLING-6746: -- Summary: Additional execution of maven-bundle-plugin:manifest is blanking out resources generated by maven-scr-plugin Key: SLING-6746 URL:

[jira] [Created] (SLING-6745) kafka-based sling.event.api implementation

Stefan Egli created SLING-6745: -- Summary: kafka-based sling.event.api implementation Key: SLING-6745 URL: https://issues.apache.org/jira/browse/SLING-6745 Project: Sling Issue Type: New Feature

Re: Dependencies in Jenkins Jobs

On Wed, 2017-03-29 at 13:44 +0200, Konrad Windszus wrote: > I think the solution is the configuration option "Block build when > upstream project is building"[0], which should be IMHO enabled on all > Jenkins Jobs for Sling.  > WDYT? > @Robert: Can you change the seed job accordingly? > Konrad

Re: Dependencies in Jenkins Jobs

I think the solution is the configuration option "Block build when upstream project is building"[0], which should be IMHO enabled on all Jenkins Jobs for Sling. WDYT? @Robert: Can you change the seed job accordingly? Konrad [0] -

Dependencies in Jenkins Jobs

I just ran into a Jenkins Build Failure in https://builds.apache.org/job/sling-bundles-extensions-validation-core-1.8/80/. Although this does have a dependency on Validation API in 1.0.0-SNAPSHOT the according API build job

[jira] [Commented] (SLING-6637) [htl] data-sly-use should not raise an exception when resource doesn't exist

[ https://issues.apache.org/jira/browse/SLING-6637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15946950#comment-15946950 ] Feike Visser commented on SLING-6637: - I raised the following improvement JIRA on this subject:

[jira] [Commented] (SLING-6727) Align accessors in API

[ https://issues.apache.org/jira/browse/SLING-6727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15946948#comment-15946948 ] Konrad Windszus commented on SLING-6727: Makes sense, fixed in

[jira] [Created] (SLING-6744) [HTL] Introduction of data-sly-resolve

Feike Visser created SLING-6744: --- Summary: [HTL] Introduction of data-sly-resolve Key: SLING-6744 URL: https://issues.apache.org/jira/browse/SLING-6744 Project: Sling Issue Type: New Feature

Re: Sling Eclipse Tooling and OSGi Bundle Content

Hi Andreas, On 28/03/17 19:38, "Andreas Schaefer Sr." wrote: >BTW as an Eclipse newbie how do I deploy an OSGi Bundle to Sling? If the project is properly setup (see [0]) the bundle gets deployed automatically on every change. You can also adjust if you want it automatically

[jira] [Resolved] (SLING-6743) Drop workspace support

[ https://issues.apache.org/jira/browse/SLING-6743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-6743. - Resolution: Fixed Removed in rev 1789321 > Drop workspace support >

[jira] [Created] (SLING-6743) Drop workspace support

Carsten Ziegeler created SLING-6743: --- Summary: Drop workspace support Key: SLING-6743 URL: https://issues.apache.org/jira/browse/SLING-6743 Project: Sling Issue Type: Improvement

Re: [event] splitting sling.event into API and Implementation bundle

On 29/03/17 09:33, "Stefan Egli" wrote: >I'll go ahead with the split and will come back when finished. I've done the main split of event into event/api and event/resource. As a next step I would suggest to release event/api so that event/resource can refer to it via a

[jira] [Commented] (SLING-6679) Replace usage of org.apache.sling.commons.json.* and org.json

[ https://issues.apache.org/jira/browse/SLING-6679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15946864#comment-15946864 ] Oliver Lietz commented on SLING-6679: - Are there any plans for modules in contrib, e.g. distribution?

[jira] [Commented] (SLING-6739) split sling.event into event.api and event.impl

[ https://issues.apache.org/jira/browse/SLING-6739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15946862#comment-15946862 ] Stefan Egli commented on SLING-6739: h6. step 6: event/api/README adjusted

[jira] [Commented] (SLING-6739) split sling.event into event.api and event.impl

[ https://issues.apache.org/jira/browse/SLING-6739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15946855#comment-15946855 ] Stefan Egli commented on SLING-6739: h6. step 5: further cleanup of the event/api/pom.xml

[jira] [Commented] (SLING-6679) Replace usage of org.apache.sling.commons.json.* and org.json

[ https://issues.apache.org/jira/browse/SLING-6679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15946834#comment-15946834 ] Robert Munteanu commented on SLING-6679: Saw the commit just now, thanks! > Replace usage of

[jira] [Commented] (SLING-6679) Replace usage of org.apache.sling.commons.json.* and org.json

[ https://issues.apache.org/jira/browse/SLING-6679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15946830#comment-15946830 ] Karl Pauls commented on SLING-6679: --- [~rombert], yeah - I removed one snaphot too many. Carsten just

[jira] [Commented] (SLING-6679) Replace usage of org.apache.sling.commons.json.* and org.json

[ https://issues.apache.org/jira/browse/SLING-6679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15946827#comment-15946827 ] Robert Munteanu commented on SLING-6679: [~karlpauls] - the launchpad does not start anymore after

[jira] [Commented] (SLING-6727) Align accessors in API

[ https://issues.apache.org/jira/browse/SLING-6727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15946826#comment-15946826 ] Oliver Lietz commented on SLING-6727: - [~kwin], it's the tense which irritates. How about

[jira] [Commented] (SLING-6739) split sling.event into event.api and event.impl

[ https://issues.apache.org/jira/browse/SLING-6739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15946810#comment-15946810 ] Stefan Egli commented on SLING-6739: h6. step 4: initial adjustment of event/resource/pom.xml, just

[jira] [Commented] (SLING-6727) Align accessors in API

[ https://issues.apache.org/jira/browse/SLING-6727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15946807#comment-15946807 ] Konrad Windszus commented on SLING-6727: I consistently use now the term validationModel (always

[jira] [Resolved] (SLING-6727) Align accessors in API

[ https://issues.apache.org/jira/browse/SLING-6727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus resolved SLING-6727. Resolution: Fixed > Align accessors in API > -- > >

[jira] [Assigned] (SLING-6727) Align accessors in API

[ https://issues.apache.org/jira/browse/SLING-6727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus reassigned SLING-6727: -- Assignee: Konrad Windszus > Align accessors in API > -- > >

[jira] [Updated] (SLING-6515) Sling Post Processor considering validation model as well

[ https://issues.apache.org/jira/browse/SLING-6515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-6515: --- Fix Version/s: (was: Sling Models Validation Impl 1.0.0) Validation

[jira] [Resolved] (SLING-6515) Sling Post Processor considering validation model as well

[ https://issues.apache.org/jira/browse/SLING-6515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus resolved SLING-6515. Resolution: Fixed Fix Version/s: Sling Models Validation Impl 1.0.0 Fixed in

Re: [RT] Configurationless Sling?

Oliver Lietz wrote > On Wednesday 29 March 2017 08:00:27 Carsten Ziegeler wrote: >> Oliver Lietz wrote >> It would be good if we have this description only once in our code base and not several times and can then generate different artifacts (if needed) out of it. >>> >>> Right, but

Re: [VOTE] Release Apache Sling File System Resource Provider 2.0.0, File System Resource Provider 1.3.0

On Monday 27 March 2017 16:21:49 Stefan Seifert wrote: > Hi, > > Apache Sling File System Resource Provider 2.0.0 (3 issues) > https://issues.apache.org/jira/browse/SLING/fixforversion/12339777 +1 (depends now on Jackrabbit, would prefer embedding org.apache.jackrabbit.util.ISO8601 like we do

Re: Parent 30 breaks maven-scr-plugin

> On 29 Mar 2017, at 10:45, Carsten Ziegeler wrote: > > Konrad Windszus wrote >> >>> On 29 Mar 2017, at 10:29, Oliver Lietz wrote: >>> >>> On Wednesday 29 March 2017 08:44:59 Konrad Windszus wrote: It seems that parent 30 breaks the usage of

Re: [VOTE] Release Apache Sling Service User Mapper 1.2.6

On Monday 27 March 2017 10:41:23 Carsten Ziegeler wrote: > Hi, > > We solved 1 issues in this release: > > https://issues.apache.org/jira/browse/SLING-6555 +1 O.

Re: [VOTE] Release Apache Sling ResourceResolver 1.5.22

On Monday 27 March 2017 07:18:26 Carsten Ziegeler wrote: > Hi, > > We solved 1 issues in this release: > > https://issues.apache.org/jira/browse/SLING-6710 +1 O.

[jira] [Comment Edited] (SLING-6739) split sling.event into event.api and event.impl

[ https://issues.apache.org/jira/browse/SLING-6739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15946737#comment-15946737 ] Stefan Egli edited comment on SLING-6739 at 3/29/17 8:49 AM: - h6. step 3:

[jira] [Commented] (SLING-6739) split sling.event into event.api and event.impl

[ https://issues.apache.org/jira/browse/SLING-6739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15946737#comment-15946737 ] Stefan Egli commented on SLING-6739: h6. step 3: initial adjustment of event/api/pom.xml, removing of

Re: Parent 30 breaks maven-scr-plugin

Konrad Windszus wrote > >> On 29 Mar 2017, at 10:29, Oliver Lietz wrote: >> >> On Wednesday 29 March 2017 08:44:59 Konrad Windszus wrote: >>> It seems that parent 30 breaks the usage of the maven-scr-plugin. With 29 it >>> works. When looking at the history of the parent

Re: [RT] Configurationless Sling?

Oliver Lietz wrote > On Tuesday 28 March 2017 15:01:47 Carsten Ziegeler wrote: >> Julian Sedding wrote >> >>> Hi Carsten >>> >>> I fully agree with the intention of your email. >>> >>> As a convention for service users, would it make sense to use the >>> bundle-symbolic-name as the user-ID (or

Re: Parent 30 breaks maven-scr-plugin

> On 29 Mar 2017, at 10:29, Oliver Lietz wrote: > > On Wednesday 29 March 2017 08:44:59 Konrad Windszus wrote: >> It seems that parent 30 breaks the usage of the maven-scr-plugin. With 29 it >> works. When looking at the history of the parent pom.xml >>

Re: Parent 30 breaks maven-scr-plugin

On Wednesday 29 March 2017 08:44:59 Konrad Windszus wrote: > It seems that parent 30 breaks the usage of the maven-scr-plugin. With 29 it > works. When looking at the history of the parent pom.xml > (https://github.com/apache/sling/commits/trunk/parent/pom.xml) I don't > really see the reason for

Re: [RT] Configurationless Sling?

On Tuesday 28 March 2017 15:01:47 Carsten Ziegeler wrote: > Julian Sedding wrote > > > Hi Carsten > > > > I fully agree with the intention of your email. > > > > As a convention for service users, would it make sense to use the > > bundle-symbolic-name as the user-ID (or principal-name)? If we

Re: [RT] Configurationless Sling?

On Wednesday 29 March 2017 08:00:27 Carsten Ziegeler wrote: > Oliver Lietz wrote > > >> It would be good if we have this description only once in our code base > >> and not several times and can then generate different artifacts (if > >> needed) out of it. > > > > Right, but I'm pretty sure I

Re: [RT] Configurationless Sling?

Karl Pauls wrote > On Wed, Mar 29, 2017 at 8:54 AM, Bertrand Delacretaz > wrote: >> On Tue, Mar 28, 2017 at 8:08 PM, Oliver Lietz wrote: >>> ...Launchpad is in fact the test bed for AEM... >> >> you mean Sling right? >> >> Launchpad with snapshots

Re: [RT] Configurationless Sling?

On Wed, Mar 29, 2017 at 8:54 AM, Bertrand Delacretaz wrote: > On Tue, Mar 28, 2017 at 8:08 PM, Oliver Lietz wrote: >> ...Launchpad is in fact the test bed for AEM... > > you mean Sling right? > > Launchpad with snapshots is required currently IMO,

[jira] [Commented] (SLING-6739) split sling.event into event.api and event.impl

[ https://issues.apache.org/jira/browse/SLING-6739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15946697#comment-15946697 ] Stefan Egli commented on SLING-6739: h6. step 1: svn renamed event to event-renamed-for-split and svn

Re: [event] splitting sling.event into API and Implementation bundle

On 28/03/17 18:28, "Carsten Ziegeler" wrote: >What about event.resource ? Its an implementation based on the resource >api > >Or event.resource.impl :) event/resource sounds good to me. I'll go ahead with the split and will come back when finished. You'll have to

Re: [RT] Configurationless Sling?

Bertrand Delacretaz wrote > On Wed, Mar 29, 2017 at 8:00 AM, Carsten Ziegeler > wrote: >> ...we decided to not use snapshot dependencies in launchpad anymore... > > Really? I know my memory is weak for those kinds of things but I don't > remember that, do you have a link

Re: Parent 30 breaks maven-scr-plugin

Konrad Windszus wrote > It seems that parent 30 breaks the usage of the maven-scr-plugin. With 29 it > works. When looking at the history of the parent pom.xml > (https://github.com/apache/sling/commits/trunk/parent/pom.xml) I don't really > see the reason for that. > If I understand correctly

Re: [RT] Configurationless Sling?

On Tue, Mar 28, 2017 at 8:08 PM, Oliver Lietz wrote: > ...Launchpad is in fact the test bed for AEM... you mean Sling right? Launchpad with snapshots is required currently IMO, to catch integration failures early by building launchpad/testing on snapshots. -Bertrand

Re: [RT] Configurationless Sling?

On Wed, Mar 29, 2017 at 8:00 AM, Carsten Ziegeler wrote: > ...we decided to not use snapshot dependencies in launchpad anymore... Really? I know my memory is weak for those kinds of things but I don't remember that, do you have a link to that decision? What I remember is

Parent 30 breaks maven-scr-plugin

It seems that parent 30 breaks the usage of the maven-scr-plugin. With 29 it works. When looking at the history of the parent pom.xml (https://github.com/apache/sling/commits/trunk/parent/pom.xml) I don't really see the reason for that. If I understand correctly reverting to parent 29 makes

Re: repository.apache.org slow?

On Tue, 2017-03-07 at 18:36 +0200, Robert Munteanu wrote: > Hi, > > Is repository.apache.org slow for anyone else? I am waiting 5+ > minutes > for the staging script to download the starged artifacts. Also the > web > UI feels slow. > > Robert Seems to be an intermittent issue when

[jira] [Updated] (SLING-6741) Migrate to R6 annotations, clean up dependencies

[ https://issues.apache.org/jira/browse/SLING-6741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-6741: Summary: Migrate to R6 annotations, clean up dependencies (was: i18n build fails with

[jira] [Resolved] (SLING-6741) Migrate to R6 annotations, clean up dependencies

[ https://issues.apache.org/jira/browse/SLING-6741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-6741. - Resolution: Fixed Fixed by switching to R6 annotations, back to parent pom 30 > Migrate

[jira] [Assigned] (SLING-6741) Migrate to R6 annotations, clean up dependencies

[ https://issues.apache.org/jira/browse/SLING-6741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-6741: --- Assignee: Carsten Ziegeler > Migrate to R6 annotations, clean up dependencies >

[jira] [Updated] (SLING-6741) i18n build fails with "ServiceLookup gave up" during tests

[ https://issues.apache.org/jira/browse/SLING-6741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-6741: Fix Version/s: i18n 2.5.10 > i18n build fails with "ServiceLookup gave up" during tests >

[jira] [Resolved] (SLING-6742) Servlets post is broken with parent 30

[ https://issues.apache.org/jira/browse/SLING-6742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-6742. - Resolution: Won't Fix I switched to R6 annotations as part of SLING-6721 > Servlets post

Re: [RT] Configurationless Sling?

Oliver Lietz wrote >> It would be good if we have this description only once in our code base >> and not several times and can then generate different artifacts (if >> needed) out of it. > > Right, but I'm pretty sure I raised my concerns generating Karaf Features and > Configurations (and