[jira] [Resolved] (SLING-4775) MockSlingSettingService shoud support getSlingId()

[ https://issues.apache.org/jira/browse/SLING-4775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-4775. Resolution: Fixed Fixed in https://svn.apache.org/r1683470 > MockSlingSettingService shoud

[jira] [Created] (SLING-4775) MockSlingSettingService shoud support getSlingId()

Robert Munteanu created SLING-4775: -- Summary: MockSlingSettingService shoud support getSlingId() Key: SLING-4775 URL: https://issues.apache.org/jira/browse/SLING-4775 Project: Sling Issue Ty

Jenkins build is still unstable: sling-contrib-1.7 #150

See

Jenkins build is still unstable: sling-trunk-1.8 #1178

See

[jira] [Resolved] (SLING-4774) JobManager does not allow finding jobs for all topics

[ https://issues.apache.org/jira/browse/SLING-4774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert resolved SLING-4774. --- Resolution: Fixed Completed: At revision: 1683445 > JobManager does not allow finding jobs fo

[jira] [Created] (SLING-4774) JobManager does not allow finding jobs for all topics

Stefan Seifert created SLING-4774: - Summary: JobManager does not allow finding jobs for all topics Key: SLING-4774 URL: https://issues.apache.org/jira/browse/SLING-4774 Project: Sling Issue T

Re: [RT] New resource query API

Am 03.06.15 um 11:40 schrieb Alexander Klimetschek: > On 02.06.2015, at 16:39, Carsten Ziegeler wrote: >> The query contains the sort information (which properties and whether >> ascending or descending), so you can get the values of the props and >> compare them. > > But then you need to > > a)

Re: [RT] New resource query API

On 02.06.2015, at 16:39, Carsten Ziegeler wrote: > The query contains the sort information (which properties and whether > ascending or descending), so you can get the values of the props and > compare them. But then you need to a) be able to understand and fully evaluate the query on the aggreg

[jira] [Reopened] (SLING-4768) Sort entries alphabetical in written model

[ https://issues.apache.org/jira/browse/SLING-4768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reopened SLING-4768: - We should check whether we can also sort settings and properties within a configuration > So

Jenkins build is still unstable: sling-contrib-1.7 #149

See

Jenkins build is still unstable: sling-trunk-1.8 #1177

See

Jenkins build is still unstable: sling-contrib-1.7 #148

See

[jira] [Updated] (SLING-4773) SlingMocks always returns the value of property jcr:primaryType for Resource.getResourceType()

[ https://issues.apache.org/jira/browse/SLING-4773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-4773: --- Component/s: Testing > SlingMocks always returns the value of property jcr:primaryType for >

[jira] [Resolved] (SLING-4714) rep:policy childnodes are not packaged individually and import fails

[ https://issues.apache.org/jira/browse/SLING-4714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marius Petria resolved SLING-4714. -- Resolution: Fixed This has been fixed by preventing the jcr trigger to distribute paths under r

[jira] [Updated] (SLING-4714) rep:policy childnodes are not packaged individually and import fails

[ https://issues.apache.org/jira/browse/SLING-4714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marius Petria updated SLING-4714: - Fix Version/s: Content Distribution Core 0.1.4 > rep:policy childnodes are not packaged individual

[jira] [Updated] (SLING-4773) SlingMocks always returns the value of from property jcr:primaryType for Resource.getResourceType()

[ https://issues.apache.org/jira/browse/SLING-4773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-4773: --- Summary: SlingMocks always returns the value of from property jcr:primaryType for Resource.get

[jira] [Updated] (SLING-4773) SlingMocks always returns the value of property jcr:primaryType for Resource.getResourceType()

[ https://issues.apache.org/jira/browse/SLING-4773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-4773: --- Summary: SlingMocks always returns the value of property jcr:primaryType for Resource.getResou

Jenkins build is still unstable: sling-trunk-1.8 #1176

See

[jira] [Updated] (SLING-4773) SlingMocks always returns jcr:primaryType for Resource.getResourceType()

[ https://issues.apache.org/jira/browse/SLING-4773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-4773: --- Description: Even if a resource was created with {{sling:resourceType}} being set to some valu

[jira] [Commented] (SLING-4773) SlingMocks always returns jcr:primaryType for Resource.getResourceType()

[ https://issues.apache.org/jira/browse/SLING-4773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14570943#comment-14570943 ] Konrad Windszus commented on SLING-4773: Attached is a test which shows the wrong

[jira] [Updated] (SLING-4773) SlingMocks always returns jcr:primaryType for Resource.getResourceType()

[ https://issues.apache.org/jira/browse/SLING-4773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-4773: --- Attachment: SLING-4773-testcase-v1.diff > SlingMocks always returns jcr:primaryType for Resour

Re: Re: svn commit: r1683326 - /sling/trunk/contrib/scripting/java/pom.xml

On Wed, 2015-06-03 at 16:34 +0200, Oliver Lietz wrote: > On Wednesday 03 June 2015 17:03:55 Robert Munteanu wrote: > > Hi Olli, > > > > It would be good if you separated the formatting changes from the > > meaningful ones; for this (small) commit I have no idea what has > > changed. > > for sure

[jira] [Created] (SLING-4773) SlingMocks always returns jcr:primaryType for Resource.getResourceType()

Konrad Windszus created SLING-4773: -- Summary: SlingMocks always returns jcr:primaryType for Resource.getResourceType() Key: SLING-4773 URL: https://issues.apache.org/jira/browse/SLING-4773 Project: S

Re: Re: svn commit: r1683326 - /sling/trunk/contrib/scripting/java/pom.xml

On Wednesday 03 June 2015 17:03:55 Robert Munteanu wrote: > Hi Olli, > > It would be good if you separated the formatting changes from the > meaningful ones; for this (small) commit I have no idea what has > changed. for sure - I totally f*cked up this commit (reverted and committed again).

[jira] [Comment Edited] (SLING-4700) remove javax.inject from org.apache.sling.scripting.java

[ https://issues.apache.org/jira/browse/SLING-4700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14570809#comment-14570809 ] Oliver Lietz edited comment on SLING-4700 at 6/3/15 2:24 PM: -

Re: Moving to Java 7 ( was: Make ResourceResolver implement Closeable)

On Fri, 2015-05-29 at 18:08 +0300, Robert Munteanu wrote: > > On May 29, 2015 5:55 PM, "Daniel Klco" wrote: > > > > Considering that Oracle is already stopped public updates for both > Java 6 > > and that the Premium Support ends December 2015, it would seem to > make > > sense to standardize o

[jira] [Resolved] (SLING-4772) Retire support for setting sling.java.version to 5

[ https://issues.apache.org/jira/browse/SLING-4772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-4772. Resolution: Fixed Fixed in https://svn.apache.org/r1683341 > Retire support for setting sli

[jira] [Assigned] (SLING-4702) Support setting sling.java.version to 8

[ https://issues.apache.org/jira/browse/SLING-4702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu reassigned SLING-4702: -- Assignee: Robert Munteanu > Support setting sling.java.version to 8 > -

[jira] [Created] (SLING-4772) Retire support for setting sling.java.version to 5

Robert Munteanu created SLING-4772: -- Summary: Retire support for setting sling.java.version to 5 Key: SLING-4772 URL: https://issues.apache.org/jira/browse/SLING-4772 Project: Sling Issue Ty

Re: svn commit: r1683326 - /sling/trunk/contrib/scripting/java/pom.xml

Hi Olli, It would be good if you separated the formatting changes from the meaningful ones; for this (small) commit I have no idea what has changed. Thanks, Robert On Wed, 2015-06-03 at 13:33 +, o...@apache.org wrote: > Author: olli > Date: Wed Jun 3 13:33:57 2015 > New Revision: 1683326 >

[jira] [Assigned] (SLING-4700) remove javax.inject from org.apache.sling.scripting.java

[ https://issues.apache.org/jira/browse/SLING-4700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz reassigned SLING-4700: --- Assignee: Oliver Lietz > remove javax.inject from org.apache.sling.scripting.java > -

[jira] [Resolved] (SLING-4700) remove javax.inject from org.apache.sling.scripting.java

[ https://issues.apache.org/jira/browse/SLING-4700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz resolved SLING-4700. - Resolution: Done r1683326 > remove javax.inject from org.apache.sling.scripting.java > --

Jenkins build is still unstable: sling-contrib-1.7 #147

See

Jenkins build is back to normal : sling-trunk-1.7 #1887

See

Status of the Apache Sling Default POST Servlets bundle

hi *, I would like to release the Apache Sling Default POST Servlets bundle . I am a bit skeptic to do this due to [0] Indeed this has been reopened since it breaks some IT . May anybody shade some light :) ? regards antonio [0] https://issues.apache.org/jira/browse/SLING-4223

Jenkins build is still unstable: sling-trunk-1.8 #1175

See

[jira] [Resolved] (SLING-4161) Support Sling Validation through a new field of the Model annotation

[ https://issues.apache.org/jira/browse/SLING-4161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus resolved SLING-4161. Resolution: Fixed > Support Sling Validation through a new field of the Model annotation > -

[jira] [Updated] (SLING-4161) Support Sling Validation through a new field of the Model annotation

[ https://issues.apache.org/jira/browse/SLING-4161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-4161: --- Fix Version/s: Sling Models Validation Impl 1.0.0 > Support Sling Validation through a new fie

Jenkins build is still unstable: sling-trunk-1.8 #1174

See

[jira] [Resolved] (SLING-4767) Optional sub models are logged as warn if they cannot be adapted

[ https://issues.apache.org/jira/browse/SLING-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus resolved SLING-4767. Resolution: Fixed > Optional sub models are logged as warn if they cannot be adapted > -