Re: Use oak:Resource nodetype instead of nt:resource while creating file node structure (SLING-6090)

Chetan Mehrotra wrote > On Mon, Oct 3, 2016 at 9:37 PM, Carsten Ziegeler wrote: >> For example, if you drop a file through webdav, I assume it's still >> nt:Resource. > > Had a look at the Webdav stuff and story here looks interesting. The > default implementation in

Re: Build failed in Jenkins: sling-extensions-hapi-client-1.8 #1

Please ignore the hapi failures for know, I specified an incorrect SVN root. Robert On Mon, 2016-10-03 at 17:15 +, Apache Jenkins Server wrote: > See /> > > -- > [...truncated 48

Re: Use oak:Resource nodetype instead of nt:resource while creating file node structure (SLING-6090)

On Mon, Oct 3, 2016 at 9:37 PM, Carsten Ziegeler wrote: > For example, if you drop a file through webdav, I assume it's still > nt:Resource. Had a look at the Webdav stuff and story here looks interesting. The default implementation in Jackrabbit uses nt:unstructured for

[jira] [Reopened] (SLING-5848) Define service user and ACLs for Scripting

[ https://issues.apache.org/jira/browse/SLING-5848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz reopened SLING-5848: - Needs also be done for Karaf. > Define service user and ACLs for Scripting >

[jira] [Assigned] (SLING-5848) Define service user and ACLs for Scripting

[ https://issues.apache.org/jira/browse/SLING-5848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz reassigned SLING-5848: --- Assignee: Oliver Lietz (was: Radu Cotescu) > Define service user and ACLs for Scripting >

[jira] [Commented] (SLING-5645) Provide a Jobs API and implementation suitable for widely distributed job processing.

[ https://issues.apache.org/jira/browse/SLING-5645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15542771#comment-15542771 ] Ian Boston commented on SLING-5645: --- All changes that were requested have been made except moving the

Re: Use oak:Resource nodetype instead of nt:resource while creating file node structure (SLING-6090)

But again, if you're not using the post servlet, you're not benefiting For example, if you drop a file through webdav, I assume it's still nt:Resource. Carsten Chetan Mehrotra wrote > Logic to create a file structure is very much baked in the code so not > possible to influence that currently

[jira] [Resolved] (SLING-5848) Define service user and ACLs for Scripting

[ https://issues.apache.org/jira/browse/SLING-5848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu resolved SLING-5848. - Resolution: Fixed Defined service user + ACLs in

[jira] [Commented] (SLING-5645) Provide a Jobs API and implementation suitable for widely distributed job processing.

[ https://issues.apache.org/jira/browse/SLING-5645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15542667#comment-15542667 ] Ian Boston commented on SLING-5645: --- Ignore that, just looked its only used inside the JMS

[jira] [Commented] (SLING-5645) Provide a Jobs API and implementation suitable for widely distributed job processing.

[ https://issues.apache.org/jira/browse/SLING-5645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15542656#comment-15542656 ] Ian Boston commented on SLING-5645: --- IIUC Embedding is an OSGi anti pattern. Could you explain why it

[jira] [Updated] (SLING-5848) Define service user and ACLs for Scripting

[ https://issues.apache.org/jira/browse/SLING-5848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu updated SLING-5848: Component/s: Launchpad > Define service user and ACLs for Scripting >

[jira] [Updated] (SLING-5848) Define service user and ACLs for Scripting

[ https://issues.apache.org/jira/browse/SLING-5848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu updated SLING-5848: Fix Version/s: Launchpad Builder 9 > Define service user and ACLs for Scripting >

[jira] [Assigned] (SLING-5848) Define service user and ACLs for Scripting

[ https://issues.apache.org/jira/browse/SLING-5848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu reassigned SLING-5848: --- Assignee: Radu Cotescu > Define service user and ACLs for Scripting >

Re: Launchpad stable and launchpad unstable

On Wed, 2016-09-28 at 22:06 +, Stefan Seifert wrote: > discussed at the Sling Committer Round Table @ adaptTo() 2016 > > currently we have only one launchpad in trunk, which contains a > mixture of release dependencies and snapshot dependencies. this makes > it difficult to release new

Re: moving sling to git

On Wed, 2016-09-28 at 22:34 +, Stefan Seifert wrote: > - contact infra >   - before we take further steps we should ask infra for it's opinion I started a discussion with infra ( discussion not yet archived, but should be available at [1] later). I was pointed to https://reporeq.apache.org/ 

Re: SLING-5848 - Define service user and ACLs for Scripting

On Monday 03 October 2016 12:48:14 Radu Cotescu wrote: > Hi, Hi Radu, > I'd like to start working on SLING-5848 [1] (since it blocks SLING-5236 > [2]). Can we agree on two things before I commit any code? > > 1. the service user should be called sling-scripting > 2. the service user will only

[jira] [Updated] (SLING-5848) Define service user and ACLs for Scripting

[ https://issues.apache.org/jira/browse/SLING-5848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz updated SLING-5848: Description: Scripting implementations require a (service) ResourceResolver with very limited read

SLING-5848 - Define service user and ACLs for Scripting

Hi, I'd like to start working on SLING-5848 [1] (since it blocks SLING-5236 [2]). Can we agree on two things before I commit any code? 1. the service user should be called sling-scripting 2. the service user will only have jcr:read permissions for /apps, /libs (the default search paths) Thanks,

[jira] [Updated] (SLING-6001) ProcessorManagerImpl should move to new ResourceChangeListener API

[ https://issues.apache.org/jira/browse/SLING-6001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rachit Kumar updated SLING-6001: Attachment: patch.txt [~cziegeler] Please review the patch for the issue. > ProcessorManagerImpl

[jira] [Updated] (SLING-6002) ScriptCacheImpl should move to new ResourceChangeListener API

[ https://issues.apache.org/jira/browse/SLING-6002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rachit Kumar updated SLING-6002: Attachment: Patch.txt [~cziegeler] Please review the patch for the issue. > ScriptCacheImpl

[jira] [Commented] (SLING-6001) ProcessorManagerImpl should move to new ResourceChangeListener API

[ https://issues.apache.org/jira/browse/SLING-6001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15542309#comment-15542309 ] Rachit Kumar commented on SLING-6001: - Working on it. > ProcessorManagerImpl should move to new

[jira] [Commented] (SLING-6002) ScriptCacheImpl should move to new ResourceChangeListener API

[ https://issues.apache.org/jira/browse/SLING-6002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15542310#comment-15542310 ] Rachit Kumar commented on SLING-6002: - Working on it. > ScriptCacheImpl should move to new

Re: Use oak:Resource nodetype instead of nt:resource while creating file node structure (SLING-6090)

Logic to create a file structure is very much baked in the code so not possible to influence that currently i.e. specify a different node for jcr:content node of nt:file. So would need some change in Sling Though IMHO I would change the default logic to use a non referenceable node and avoid

Re: Use oak:Resource nodetype instead of nt:resource while creating file node structure (SLING-6090)

Chetan Mehrotra wrote > > That being said then same argument can be applied to change being done > in Sling level where for same POST request now results in different > nodetypes being used. If that is a big concern then we can make use of > this new nodetype based on some request param. So a

Re: Integration tests near to modules

On Mon, Oct 3, 2016 at 12:48 PM Robert Munteanu wrote: > On Wed, 2016-09-28 at 22:06 +, Stefan Seifert wrote: > > a goal would be to move most of module-specific integration tests > > "near to the module" or just in the module project itself, using one > > oft the

Re: svn commit: r1763153 - /sling/trunk/contrib/extensions/tracer/src/main/java/org/apache/sling/tracer/internal/LogTracer.java

On Mon, Oct 3, 2016 at 5:13 PM, Robert Munteanu wrote: > AFAIR it analyses the bytecode > and the imports are simply not there. Okie. I thought that inlining of constant is implementation detail of javac and may or may not work in all cases. However reading [1] confirms that

Re: svn commit: r1763153 - /sling/trunk/contrib/extensions/tracer/src/main/java/org/apache/sling/tracer/internal/LogTracer.java

On Mon, 2016-10-03 at 17:12 +0530, Chetan Mehrotra wrote: > On Mon, Oct 3, 2016 at 4:57 PM, Robert Munteanu > wrote: > > AFAIK constants will be inlined by javac, so by referencing them > > bnd > > will not add imports to the packages. > > > Did not knew that bnd avoids

Re: svn commit: r1763153 - /sling/trunk/contrib/extensions/tracer/src/main/java/org/apache/sling/tracer/internal/LogTracer.java

On Mon, Oct 3, 2016 at 4:57 PM, Robert Munteanu wrote: > AFAIK constants will be inlined by javac, so by referencing them bnd > will not add imports to the packages. Did not knew that bnd avoids adding import in such cases. Changed the code to use the constants then. Thanks

Re: svn commit: r1763153 - /sling/trunk/contrib/extensions/tracer/src/main/java/org/apache/sling/tracer/internal/LogTracer.java

Hi Chetan, On Mon, 2016-10-03 at 10:59 +, chet...@apache.org wrote: > +    //Do not use constant name to keep dependency as optional > +    > //filterProps.put(HttpWhiteboardConstants.HTTP_WHITEBOARD_FILTER_PATT > ERN, "/"); > +    >

[jira] [Comment Edited] (SLING-5645) Provide a Jobs API and implementation suitable for widely distributed job processing.

[ https://issues.apache.org/jira/browse/SLING-5645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15541648#comment-15541648 ] Chetan Mehrotra edited comment on SLING-5645 at 10/3/16 11:16 AM: -- We

[jira] [Comment Edited] (SLING-5645) Provide a Jobs API and implementation suitable for widely distributed job processing.

[ https://issues.apache.org/jira/browse/SLING-5645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15541648#comment-15541648 ] Chetan Mehrotra edited comment on SLING-5645 at 10/3/16 11:11 AM: -- We

[jira] [Resolved] (SLING-6089) Log Tracer does not work with system having new HTTP whiteboard implementation

[ https://issues.apache.org/jira/browse/SLING-6089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chetan Mehrotra resolved SLING-6089. Resolution: Fixed Fixed with 1763153. The filter is now registered with both old and new

[jira] [Commented] (SLING-6089) Log Tracer does not work with system having new HTTP whiteboard implementation

[ https://issues.apache.org/jira/browse/SLING-6089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15542133#comment-15542133 ] Chetan Mehrotra commented on SLING-6089: Another aspect - Even with warning any bundle using the

Re: Integration tests near to modules

On Wed, 2016-09-28 at 22:06 +, Stefan Seifert wrote: > a goal would be to move most of module-specific integration tests > "near to the module" or just in the module project itself, using one > oft the numerous available integration test tool support available in > sling today. this is already

Re: Resource packaging/content packaging in Sling

On Sat, 2016-10-01 at 13:43 +0200, Konrad Windszus wrote: > What about an HTTP API to list, download, upload/install and build > packages? I guess the installer factory would only cover the > upload/install part of it. I think this is a good idea, but should probably tackled in a follow-up task,

Re: Sling Launchpad and Sling Karaf features

On Wed, 2016-09-28 at 21:37 +, Stefan Seifert wrote: > the launchpad should be split up in separates features/provisioning > fragments to make it possible to easily build a "minimal launchpad" > or "minimal launchpad + X" by selection only some but not all > features. +1, this would be very

Re: sling attic / cleanup

On Sat, 2016-10-01 at 09:25 +0200, Oliver Lietz wrote: > On Saturday 01 October 2016 01:54:17 Robert Munteanu wrote: > > On Fri, 2016-09-30 at 12:55 +, Stefan Seifert wrote: > > > i assume in samples/ there are also some candidates. > > > Hi Robert, > > > I think it would be a good time to

Re: Use oak:Resource nodetype instead of nt:resource while creating file node structure (SLING-6090)

On Mon, Oct 3, 2016 at 3:43 PM, Carsten Ziegeler wrote: > why can't do Oak the right thing? Compatibility constraints :). Had this discussion earlier also but given compatibility constraints its not possible to change the defaults. If a nodetype says its

Re: Preparing Launchpad 9 Release

On Mon, 2016-10-03 at 11:57 +0200, Carsten Ziegeler wrote: > Chetan Mehrotra wrote > > Currently we are including 1.5.x version of Oak in Sling which are > > considered unstable. Not sure on best way to deal with that. > > > > One way out could be to align release of launchpad in Sling with > >

Re: Use oak:Resource nodetype instead of nt:resource while creating file node structure (SLING-6090)

Chetan Mehrotra wrote > On Mon, Oct 3, 2016 at 3:30 PM, Carsten Ziegeler wrote: >> And then all scripts or code dealing with nt:resource fails as the node >> or resource type is now oak:resource ? > > Yes if the code checks if nodetype of jcr:content node under nt:file > is

[jira] [Commented] (SLING-6089) Log Tracer does not work with system having new HTTP whiteboard implementation

[ https://issues.apache.org/jira/browse/SLING-6089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15542055#comment-15542055 ] Carsten Ziegeler commented on SLING-6089: - Yes, it's the same, you can also use the regex

[jira] [Commented] (SLING-6090) Avoid using nt:resource while creating file nodes via SlingPostServlet

[ https://issues.apache.org/jira/browse/SLING-6090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15542041#comment-15542041 ] Chetan Mehrotra commented on SLING-6090: Can you elaborate bit more here i.e. what kind of switch

Re: Use oak:Resource nodetype instead of nt:resource while creating file node structure (SLING-6090)

On Mon, Oct 3, 2016 at 3:30 PM, Carsten Ziegeler wrote: > And then all scripts or code dealing with nt:resource fails as the node > or resource type is now oak:resource ? Yes if the code checks if nodetype of jcr:content node under nt:file is of type nt:resource. So far my

Re: Use oak:Resource nodetype instead of nt:resource while creating file node structure (SLING-6090)

Chetan Mehrotra wrote > On Mon, Oct 3, 2016 at 2:43 PM, Julian Sedding wrote: >> Actually, the Sling POST Servlet bundle has a dependency on the JCR >> API, as does SlingFileUploadHandler. > > Aah missed seeing that. Makes decision simpler then. Would try to come > up with

[jira] [Commented] (SLING-6089) Log Tracer does not work with system having new HTTP whiteboard implementation

[ https://issues.apache.org/jira/browse/SLING-6089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15542033#comment-15542033 ] Chetan Mehrotra commented on SLING-6089: I want this to be usable on older AEM setups which I

[jira] [Commented] (SLING-6090) Avoid using nt:resource while creating file nodes via SlingPostServlet

[ https://issues.apache.org/jira/browse/SLING-6090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15542031#comment-15542031 ] Carsten Ziegeler commented on SLING-6090: - What about a switch in Oak? > Avoid using nt:resource

Re: Preparing Launchpad 9 Release

Chetan Mehrotra wrote > Currently we are including 1.5.x version of Oak in Sling which are > considered unstable. Not sure on best way to deal with that. > > One way out could be to align release of launchpad in Sling with major > version release of Oak which typically happens once in year around

[jira] [Commented] (SLING-6089) Log Tracer does not work with system having new HTTP whiteboard implementation

[ https://issues.apache.org/jira/browse/SLING-6089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15542023#comment-15542023 ] Carsten Ziegeler commented on SLING-6089: - [~chetanm] I think the best option is to use both

[jira] [Commented] (SLING-6090) Avoid using nt:resource while creating file nodes via SlingPostServlet

[ https://issues.apache.org/jira/browse/SLING-6090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15542017#comment-15542017 ] Chetan Mehrotra commented on SLING-6090: We can avoid direct Oak dependency by going for either #2

Re: Use oak:Resource nodetype instead of nt:resource while creating file node structure (SLING-6090)

On Mon, Oct 3, 2016 at 2:43 PM, Julian Sedding wrote: > Actually, the Sling POST Servlet bundle has a dependency on the JCR > API, as does SlingFileUploadHandler. Aah missed seeing that. Makes decision simpler then. Would try to come up with the patch then Chetan Mehrotra

[jira] [Commented] (SLING-6090) Avoid using nt:resource while creating file nodes via SlingPostServlet

[ https://issues.apache.org/jira/browse/SLING-6090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15542000#comment-15542000 ] Carsten Ziegeler commented on SLING-6090: - This is really a little bit annoying - this would mean

Re: Use oak:Resource nodetype instead of nt:resource while creating file node structure (SLING-6090)

Actually, the Sling POST Servlet bundle has a dependency on the JCR API, as does SlingFileUploadHandler. In that case #2 seems the best way forward. Use oak:Resource if available, otherwise fall back to nt:resource. Regards Julian On Mon, Oct 3, 2016 at 10:49 AM, Chetan Mehrotra

[jira] [Created] (SLING-6092) Create OSGi-only development feature

Robert Munteanu created SLING-6092: -- Summary: Create OSGi-only development feature Key: SLING-6092 URL: https://issues.apache.org/jira/browse/SLING-6092 Project: Sling Issue Type:

Re: Use oak:Resource nodetype instead of nt:resource while creating file node structure (SLING-6090)

On Mon, Oct 3, 2016 at 2:01 PM, Oliver Lietz wrote: > I'm aware of that thread and therefore suggest to drive the spec towards > version 3. Providing tools for upgrading from 2 to 3 would allow to break > backwards compatibility and evolve. I believe this is orthogonal to

[jira] [Closed] (SLING-6045) Improve java package and GAV for oak restrictions

[ https://issues.apache.org/jira/browse/SLING-6045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-6045. -- > Improve java package and GAV for oak restrictions >

[jira] [Closed] (SLING-6042) Use sling:resourceTypesWithDescendants instead of sling:resourceTypesWithChildren

[ https://issues.apache.org/jira/browse/SLING-6042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-6042. -- > Use sling:resourceTypesWithDescendants instead of > sling:resourceTypesWithChildren >

[jira] [Closed] (SLING-5768) Introduce sling:resourceTypes as extension to Oak permission system

[ https://issues.apache.org/jira/browse/SLING-5768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-5768. -- > Introduce sling:resourceTypes as extension to Oak permission system >

Re: Preparing Launchpad 9 Release

On Friday 30 September 2016 14:40:11 Carsten Ziegeler wrote: > Looking at the snapshot references from our launchpad project, I think > there are only a few things to be done. (List is below) > > I think it should be doable to release all these things in the near > future and then get launchpad 9

Re: Use oak:Resource nodetype instead of nt:resource while creating file node structure (SLING-6090)

On Mon, Oct 3, 2016 at 2:06 PM, Julian Sedding wrote: > In an ideal world I would decouple the logic of what constitutes a > file, i.e. create an API/convention in Sling, that is JCR agnostic and > move the JCR-specific implementation to the JCR ResourceProvider > bundle. In

Re: Use oak:Resource nodetype instead of nt:resource while creating file node structure (SLING-6090)

Hi Chetan I think point #2 (cannot check for oak:Resource nodetype because Sling POST Servlet has no JCR dependency) indicates that we have an abstraction leak. I.e. the POST servlet needs to know the correct JCR node-structure despite the fact that it "officially" has no JCR dependency. In an

[RESULT][VOTE] Release Apache Sling Oak Restrictions version 1.0.0

Hi, The vote has passed with the following result: +1 (binding): Karl Pauls, Daniel Klco, Robert Munteanu +1 (non-binding): Georg Henzler I will copy this release to the Sling dist directory and promote the artifacts to the central Maven repository. Thanks, Robert

Re: [VOTE] Release Apache Sling Oak Restrictions version 1.0.0

On Tue, 2016-09-27 at 22:32 +0200, Robert Munteanu wrote: > Please vote to approve this release: +1 Robert signature.asc Description: This is a digitally signed message part

Re: pipes release 0.0.10

Hi, not that i can see, thanks. Nicolas > On Oct 2, 2016, at 2:32 PM, Oliver Lietz wrote: > > On Friday 30 September 2016 07:48:24 Nicolas Peltier wrote: >> Hi, >> >> +1 this would be clearer indeed > > Done. Anything else? Otherwise I would try to do the release

Re: Use oak:Resource nodetype instead of nt:resource while creating file node structure (SLING-6090)

On Monday 03 October 2016 13:43:44 Chetan Mehrotra wrote: > Hi Oliver, Hi Chetan, > Defaults for nt:resource was changed in JCR 2.0 and it was made > unreferenceable. See [1] for some background. However JR2 and then Oak > continued to use the older definition for compatibility purpose and >

Re: Use oak:Resource nodetype instead of nt:resource while creating file node structure (SLING-6090)

Hi Oliver, Defaults for nt:resource was changed in JCR 2.0 and it was made unreferenceable. See [1] for some background. However JR2 and then Oak continued to use the older definition for compatibility purpose and hence the need for defining a custom nodetype Chetan Mehrotra [1]

Re: Use oak:Resource nodetype instead of nt:resource while creating file node structure (SLING-6090)

On Monday 03 October 2016 10:53:40 Chetan Mehrotra wrote: > Hi Team, Hi Chetan, > Have a look at SLING-6090 where its suggested to avoid using > nt:resource. It also mentions few possible solutions. > > Kindly have a look and provide your feedback on which solution to implement rather than

[jira] [Comment Edited] (SLING-5645) Provide a Jobs API and implementation suitable for widely distributed job processing.

[ https://issues.apache.org/jira/browse/SLING-5645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15541648#comment-15541648 ] Chetan Mehrotra edited comment on SLING-5645 at 10/3/16 6:56 AM: - We have

[jira] [Commented] (SLING-5645) Provide a Jobs API and implementation suitable for widely distributed job processing.

[ https://issues.apache.org/jira/browse/SLING-5645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15541702#comment-15541702 ] Chetan Mehrotra commented on SLING-5645: In that case it would be better to embed it > Provide a

Re: Release the Sling MOM Bundles (SLING-5645)

Hi, AFAIK there isn't anything that absolutely needs to be done. I notice some cleanup was suggested in Jira which is fine. I made some comments. Happy to do the release if you want. Best Regards Ian On 3 October 2016 at 07:13, Chetan Mehrotra wrote: > Hi, > > We

[jira] [Commented] (SLING-5645) Provide a Jobs API and implementation suitable for widely distributed job processing.

[ https://issues.apache.org/jira/browse/SLING-5645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15541688#comment-15541688 ] Ian Boston commented on SLING-5645: --- GSon is being used for performance reasons. Probably not a good

[jira] [Assigned] (SLING-6088) Distribution ITs fail on Jenkins

[ https://issues.apache.org/jira/browse/SLING-6088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommaso Teofili reassigned SLING-6088: -- Assignee: Tommaso Teofili > Distribution ITs fail on Jenkins >

Re: Preparing Launchpad 9 Release

Currently we are including 1.5.x version of Oak in Sling which are considered unstable. Not sure on best way to deal with that. One way out could be to align release of launchpad in Sling with major version release of Oak which typically happens once in year around Feb-March. This would allow us

[jira] [Commented] (SLING-5645) Provide a Jobs API and implementation suitable for widely distributed job processing.

[ https://issues.apache.org/jira/browse/SLING-5645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15541648#comment-15541648 ] Chetan Mehrotra commented on SLING-5645: We have used this feature in poc for adaptTo [1] and have

Release the Sling MOM Bundles (SLING-5645)

Hi, We have used the snapshot version of Sling MOM Feature (ActiveMQ based Job management) in our poc for adaptTo [1] and have found it very useful. To enable wider usage I think we should now provide an official release of these bundles. What would be required to have the first release done?

[jira] [Resolved] (SLING-6091) Make dependency on jackrabbit-jcr-rmi as optional in jcr base

[ https://issues.apache.org/jira/browse/SLING-6091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chetan Mehrotra resolved SLING-6091. Resolution: Fixed Marked the dependency as optional in 1763118 > Make dependency on

[jira] [Updated] (SLING-6091) Make dependency on jackrabbit-jcr-rmi as optional in jcr base

[ https://issues.apache.org/jira/browse/SLING-6091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chetan Mehrotra updated SLING-6091: --- Priority: Minor (was: Major) > Make dependency on jackrabbit-jcr-rmi as optional in jcr base

[jira] [Created] (SLING-6091) Make dependency on jackrabbit-jcr-rmi as optional in jcr base

Chetan Mehrotra created SLING-6091: -- Summary: Make dependency on jackrabbit-jcr-rmi as optional in jcr base Key: SLING-6091 URL: https://issues.apache.org/jira/browse/SLING-6091 Project: Sling