[jira] [Closed] (SLING-5885) ResourceResolverFactory might not get correctly re-registered if configuration is changed

[Carsten Ziegeler (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-5885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carsten Ziegeler closed SLING-5885.
---

> ResourceResolverFactory might not get correctly re-registered if 
> configuration is changed
> -
>
> Key: SLING-5885
> URL: https://issues.apache.org/jira/browse/SLING-5885
> Project: Sling
>  Issue Type: Bug
>  Components: ResourceResolver
>Affects Versions: Resource Resolver 1.4.12, Resource Resolver 1.4.14
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: Resource Resolver 1.4.16
>
>
> If the resource resolver factory gets reregistered, the old instance is not 
> correctly removed which then in turn is used by components. But it will 
> return null for the resource resolver factory service as it is deactivated. 
> Therefore the system becomes useless



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SLING-5890) Documentation for the new sling oak restrictions from SLING-5768

[Georg Henzler (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-5890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15392676#comment-15392676
 ] 

Georg Henzler commented on SLING-5890:
--

Updated attachment with some fixed typos and fixed code blocks (I couldn't test 
it, my markdown viewer showed old and new nicely, but I had a look at other 
working examples)

> Documentation for the new sling oak restrictions from SLING-5768
> 
>
> Key: SLING-5890
> URL: https://issues.apache.org/jira/browse/SLING-5890
> Project: Sling
>  Issue Type: Task
>  Components: Extensions
>Reporter: Georg Henzler
>Assignee: Robert Munteanu
> Attachments: sling-oak-restrictions.mdtext
>
>
> Attached the markdown file for the documentation of SLING-5768, I suppose the 
> best location for it is 
> sling/site/trunk/content/documentation/bundles/sling-oak-restrictions.mdtext 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-5890) Documentation for the new sling oak restrictions from SLING-5768

[Georg Henzler (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-5890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Georg Henzler updated SLING-5890:
-
Attachment: sling-oak-restrictions.mdtext

> Documentation for the new sling oak restrictions from SLING-5768
> 
>
> Key: SLING-5890
> URL: https://issues.apache.org/jira/browse/SLING-5890
> Project: Sling
>  Issue Type: Task
>  Components: Extensions
>Reporter: Georg Henzler
>Assignee: Robert Munteanu
> Attachments: sling-oak-restrictions.mdtext
>
>
> Attached the markdown file for the documentation of SLING-5768, I suppose the 
> best location for it is 
> sling/site/trunk/content/documentation/bundles/sling-oak-restrictions.mdtext 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-5890) Documentation for the new sling oak restrictions from SLING-5768

[Georg Henzler (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-5890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Georg Henzler updated SLING-5890:
-
Attachment: (was: sling-oak-restrictions.mdtext)

> Documentation for the new sling oak restrictions from SLING-5768
> 
>
> Key: SLING-5890
> URL: https://issues.apache.org/jira/browse/SLING-5890
> Project: Sling
>  Issue Type: Task
>  Components: Extensions
>Reporter: Georg Henzler
>Assignee: Robert Munteanu
> Attachments: sling-oak-restrictions.mdtext
>
>
> Attached the markdown file for the documentation of SLING-5768, I suppose the 
> best location for it is 
> sling/site/trunk/content/documentation/bundles/sling-oak-restrictions.mdtext 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SLING-5886) Sling Configuration - Initial Contribution

[Carsten Ziegeler (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-5886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15392651#comment-15392651
 ] 

Carsten Ziegeler commented on SLING-5886:
-

I'm fine with just returning a ValueMap and not a named value map or adding the 
name as a special property to the value map. 
Yes, looking at "get" and "getList" its not clear what they do and I totally 
agree with not using "resolve" (I came to the same conclusion after my 
prototype). 

I've thought a little bit about the methods for custom annotation classes - 
while I see that the default mapping is the class name and there could be some 
annotation on that class, this basically means that you can only have one 
configuration of that type. However, e.g. if you think about server 
configurations (url, user, password) you might have several of them all using 
the same custom annotation class. So I have the feeling that we should have a 
variant where you pass in the class and the name.

> Sling Configuration - Initial Contribution
> --
>
> Key: SLING-5886
> URL: https://issues.apache.org/jira/browse/SLING-5886
> Project: Sling
>  Issue Type: New Feature
>  Components: Extensions
>Reporter: Stefan Seifert
>Assignee: Stefan Seifert
>
> as discussed in the mailing list (see [my post from april 
> 2016|http://apache-sling.73963.n3.nabble.com/RT-Use-cases-for-content-specific-configurations-in-Sling-amp-Contribution-td4060813.html])
>  i want to contribute the wcm.io Configuration parts that are not 
> AEM-specific.
> the current features of wcm.io Configuration are described here: 
> http://wcm.io/config/
> the main goal is to support "context-specific" configuration, that means 
> configuration that is different for different content paths (e.g. sites, 
> tenants).
> during the contribution some changes and refactorings are required/planned, 
> e.g.:
> * remove some dependencies to wcm.io build environment, Guava and others
> * remove the "application" distinction currently part of wcm.io Configuration 
> in favor or a more path-based distinction
> * refactor the user-faced configuration API to further simplify it and 
> support OSGi R6-style annotation classed for typed configuration access



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SLING-5886) Sling Configuration - Initial Contribution

[Stefan Seifert (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-5886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15392614#comment-15392614
 ] 

Stefan Seifert commented on SLING-5886:
---

{quote}I like the name ConfigurationResourceResolver and I think it makes sense 
to keep the interfaces separate.{quote}
moved it to a separate sub-package.
{quote}
The CR is has methods to return a value map, I think we should only return 
read-only configurations and make this clear in the javadocs. In my prototype I 
have the NamedValueMap (extends ValueMap) in order to have a way to return the 
config name. Another option would be to include the name in the value map as a 
predefined key.
{quote}
do we really need this? if the configuration annotation class is returned it 
does not contain a "name" method either. name in the valuemap as predefined key 
is not nice either.
{quote}
I personally don't like the method names "get" and "getList" as by just looking 
at these names it's not clear what they do, but if I'm the only one we can go 
with these.
{quote}
do you not like the names "get" and "getList", or just that there is no suffix 
what they get?
i've renamed the method that return a valuemap to include a valuemap in it's 
name. i do not wanted to use "resolve..." as method name as in you prototype, 
because when looking at the ResourceResolver the getResource method is the 
primary method to go, whereas the "resolve" method is a very special method 
applications rarely should use.
i've not (yet) renamed the get/getList methods that return a custom annotation 
class because ... it returns custom annotation class.

> Sling Configuration - Initial Contribution
> --
>
> Key: SLING-5886
> URL: https://issues.apache.org/jira/browse/SLING-5886
> Project: Sling
>  Issue Type: New Feature
>  Components: Extensions
>Reporter: Stefan Seifert
>Assignee: Stefan Seifert
>
> as discussed in the mailing list (see [my post from april 
> 2016|http://apache-sling.73963.n3.nabble.com/RT-Use-cases-for-content-specific-configurations-in-Sling-amp-Contribution-td4060813.html])
>  i want to contribute the wcm.io Configuration parts that are not 
> AEM-specific.
> the current features of wcm.io Configuration are described here: 
> http://wcm.io/config/
> the main goal is to support "context-specific" configuration, that means 
> configuration that is different for different content paths (e.g. sites, 
> tenants).
> during the contribution some changes and refactorings are required/planned, 
> e.g.:
> * remove some dependencies to wcm.io build environment, Guava and others
> * remove the "application" distinction currently part of wcm.io Configuration 
> in favor or a more path-based distinction
> * refactor the user-faced configuration API to further simplify it and 
> support OSGi R6-style annotation classed for typed configuration access



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[VOTE RESULT] Release Apache Sling Resource Resolver 1.4.16

[Carsten Ziegeler]

THe vote passes with three binding +1 votes

Thanks

 Carsten

-- 
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org

Re: [karaf] References to artifacts under vote

[Oliver Lietz]

On Monday 25 July 2016 17:05:29 Robert Munteanu wrote:
> Hi,

Hi Robert,

> I tried to build the karaf reactor, but it seems to reference releases
> to artifacts under vote. Is there a particular reason for doing that? 

sure – I'm *very* short in time and trying to get the remaining issues fixed 
before doing a first release.

Before giving +1 for a release I build from tag, add the artifact to Sling 
Karaf and do a full build cycle with integration tests, try to have a look at 
sources and diff against the previous tag and finally check signatures.

I've done a few releases myself in the last weeks to remove remaining 
snapshots from Sling's Karaf Features. Oak Server is the only blocker left – 
next on my list.

Instead of removing releases under vote again from Sling's Karaf Features I've 
done one commit with three upcoming releases yesterday (and one with a test 
dependency) – because I cannot stash. And only Resource Resolver 1.4.16 is not 
yet on Maven Central (and the testing fragment bundle), right?

> The downside is that it's not buildable out-of-the box except with very
> specific setups - you either add all staging repositories or mvn
> install the missing artifacts from their SVN tags.

Quoting our own announcement: "Building from verified sources is recommended, 
but convenience binaries are also available via Maven"
Really, there is no downside. That was just very bad timing. Sling Karaf is 
most of the time in a very convenient state for users in contrast to Sling 
Launchpad. And no harm for our CI builds, I've not added it back to any 
builder after moving.

Regards,
O.

> Thanks,
> 
> Robert

Re: [VOTE] Release Apache Sling Launchpad Testing Fragment Bundle 2.0.10

[Carsten Ziegeler]

+1

 

-- 
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org

Re: LoginAdministrative whitelisting patch ready for review

[Carsten Ziegeler]

> Hi,
> 
> On Fri, Jul 22, 2016 at 5:13 PM, Carsten Ziegeler  
> wrote:
>>> https://issues.apache.org/jira/browse/SLING-5135 ...
>> What about provisioning the whitelist with the usual Sling core bundles
>> that are used in an installation, so you can run a "simple" Sling
>> without any configuration?...
> 
> The problem with such a hardcoded default configuration is the need to
> release the bundle if we need to change that config.

Well, sure - but as we don't want to introduce new loginAdministrative
calls, it's unlikely to happen. And it's still an OSGi configuration, so
you can override.

I seriously think, Sling should run without any OSGi configuration, at
least the basics. We can discuss what the basics are, but from the list
belowe jcr.oak.server and jcr.base sound pretty basic to me.

Regards
Carsten

> 
> Right now the below whitelist [1] is needed for most of the launchpad
> integration tests to pass.
> 
> While some bundles like oak.server are obviously ok, others might need
> deeper investigation which I wasn't planning to do right now, so I'd
> prefer starting with an empy config. Unless someone can look at those
> bundles to reduce the list.
> 
> -Bertrand
> 
> [1]
> "org.apache.sling.extensions.webconsolesecurityprovider",
> "org.apache.sling.jcr.base"
> "org.apache.sling.jcr.contentloader",
> "org.apache.sling.jcr.davex",
> "org.apache.sling.jcr.jackrabbit.usermanager",
> "org.apache.sling.jcr.webconsole",
> "org.apache.sling.jcr.webdav",
> "org.apache.sling.servlets.post",
> "org.apache.sling.jcr.oak.server",
> "org.apache.sling.installer.provider.jcr",
> "org.apache.sling.jcr.resource"]
> 


 

-- 
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org

[jira] [Commented] (SLING-5870) Switch event ITs to use Oak

[Carsten Ziegeler (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-5870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15392543#comment-15392543
 ] 

Carsten Ziegeler commented on SLING-5870:
-

This looks similar to the tries I did some time ago and I never got past this 
point

> Switch event ITs to use Oak
> ---
>
> Key: SLING-5870
> URL: https://issues.apache.org/jira/browse/SLING-5870
> Project: Sling
>  Issue Type: Improvement
>  Components: Extensions
>Reporter: Robert Munteanu
> Fix For: Event 4.1.0
>
> Attachments: 0001-SLING-5870-Switch-event-ITs-to-use-Oak.patch, 
> 0001-SLING-5870-Switch-event-ITs-to-use-Oak.patch, 
> 0002-SLING-5870-Switch-event-ITs-to-use-Oak.patch, 
> 0002-SLING-5870-Switch-event-ITs-to-use-Oak.patch, 
> 0003-SLING-5870-Switch-event-ITs-to-use-Oak.patch, 
> 0004-SLING-5870-Switch-event-ITs-to-use-Oak.patch, 
> SLING-5870.testing-paxexam.patch, SLING-5870.zip, test.log
>
>
> The Event ITs sometimes fail on Jenkins, and the errors seem to indicate 
> inconsistencies in the repository, e.g.
> {code}19.07.2016 09:57:31.489 *WARN* [Apache Sling JCR Resource Event Queue 
> Processor] org.apache.sling.jcr.resource.internal.JcrResourceListener 
> processOsgiEventQueue: Unexpected problem processing event 
> {path=/var/eventing/jobs/assigned/f96f5677-4d3b-454d-9dc1-c2ee9270b35c/sling.chaos.round.4/2016/7/19/9/53/f96f5677-4d3b-454d-9dc1-c2ee9270b35c_2931,
>  resourceChangedAttributes=[Ljava.lang.String;@51e6a8e1, 
> resourceAddedAttributes=[Ljava.lang.String;@1447afb0, userid=admin}
> org.apache.sling.api.SlingException: Problem retrieving node based resource 
> /var/eventing/jobs/assigned/f96f5677-4d3b-454d-9dc1-c2ee9270b35c/sling.chaos.round.4/2016/7/19/9/53/f96f5677-4d3b-454d-9dc1-c2ee9270b35c_2931
>   at 
> org.apache.sling.jcr.resource.internal.helper.jcr.JcrResourceProvider.getResource(JcrResourceProvider.java:156)
>   at 
> org.apache.sling.jcr.resource.internal.helper.jcr.JcrResourceProvider.getResource(JcrResourceProvider.java:143)
>   at 
> org.apache.sling.resourceresolver.impl.tree.ResourceProviderFactoryHandler.getResource(ResourceProviderFactoryHandler.java:113)
>   at 
> org.apache.sling.resourceresolver.impl.tree.ResourceProviderEntry.getResourceFromProviders(ResourceProviderEntry.java:401)
>   at 
> org.apache.sling.resourceresolver.impl.tree.ResourceProviderEntry.getInternalResource(ResourceProviderEntry.java:356)
>   at 
> org.apache.sling.resourceresolver.impl.tree.ResourceProviderEntry.getResource(ResourceProviderEntry.java:138)
>   at 
> org.apache.sling.resourceresolver.impl.ResourceResolverImpl.getAbsoluteResourceInternal(ResourceResolverImpl.java:988)
>   at 
> org.apache.sling.resourceresolver.impl.ResourceResolverImpl.getResourceInternal(ResourceResolverImpl.java:635)
>   at 
> org.apache.sling.resourceresolver.impl.ResourceResolverImpl.getResource(ResourceResolverImpl.java:590)
>   at 
> org.apache.sling.jcr.resource.internal.JcrResourceListener.processOsgiEventQueue(JcrResourceListener.java:340)
>   at 
> org.apache.sling.jcr.resource.internal.JcrResourceListener$1.run(JcrResourceListener.java:107)
>   at java.lang.Thread.run(Thread.java:744)
> Caused by: javax.jcr.PathNotFoundException: 
> /var/eventing/jobs/assigned/f96f5677-4d3b-454d-9dc1-c2ee9270b35c/sling.chaos.round.4/2016/7/19/9/53/f96f5677-4d3b-454d-9dc1-c2ee9270b35c_2931
>   at org.apache.jackrabbit.core.ItemManager.getItem(ItemManager.java:552)
>   at 
> org.apache.jackrabbit.core.session.SessionItemOperation$4.perform(SessionItemOperation.java:97)
>   at 
> org.apache.jackrabbit.core.session.SessionItemOperation$4.perform(SessionItemOperation.java:93)
>   at 
> org.apache.jackrabbit.core.session.SessionItemOperation.perform(SessionItemOperation.java:187)
>   at 
> org.apache.jackrabbit.core.session.SessionState.perform(SessionState.java:216)
>   at org.apache.jackrabbit.core.SessionImpl.perform(SessionImpl.java:361)
>   at org.apache.jackrabbit.core.SessionImpl.getItem(SessionImpl.java:786)
>   at 
> org.apache.sling.jcr.resource.internal.helper.jcr.JcrResourceProvider.createResource(JcrResourceProvider.java:211)
>   at 
> org.apache.sling.jcr.resource.internal.helper.jcr.JcrResourceProvider.getResource(JcrResourceProvider.java:154)
>   ... 11 common frames omitted{code}
> Moving to Oak might help with these issues, and it's anyway a good idea since 
> the default Launchpad only includes Sling ATM.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-5809) Provide Sling's Karaf Features as Options for Pax Exam

[Oliver Lietz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-5809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz updated SLING-5809:

Summary: Provide Sling's Karaf Features as Options for Pax Exam  (was: 
Provide Sling's Launchpad Karaf Features as Options for Pax Exam)

> Provide Sling's Karaf Features as Options for Pax Exam
> --
>
> Key: SLING-5809
> URL: https://issues.apache.org/jira/browse/SLING-5809
> Project: Sling
>  Issue Type: New Feature
>  Components: Testing
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Testing Pax Exam 0.0.2
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SLING-5901) Build fails with OOME (Maven Source Plugin 3.0.0)

[Oliver Lietz (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-5901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15392474#comment-15392474
 ] 

Oliver Lietz commented on SLING-5901:
-

[~rombert], [~cziegeler]: the module was added a month ago and didn't break the 
build before, we should come up quickly with a fix and Parent 28

> Build fails with OOME (Maven Source Plugin 3.0.0)
> -
>
> Key: SLING-5901
> URL: https://issues.apache.org/jira/browse/SLING-5901
> Project: Sling
>  Issue Type: Bug
>Affects Versions: Parent 27
>Reporter: Oliver Lietz
>Priority: Blocker
>
> {noformat}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-source-plugin:3.0.0:jar (attach-sources) on 
> project org.apache.sling.testing.paxexam: Error creating source archive: 
> Problem creating jar: Execution exception: Java heap space -> [Help 1]
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR] 
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR] 
> [ERROR] After correcting the problems, you can resume the build with the 
> command
> [ERROR]   mvn  -rf :org.apache.sling.testing.paxexam
> {noformat}
> See MSOURCES-94 for details.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (SLING-5901) Build fails with OOME (Maven Source Plugin 3.0.0)

[Oliver Lietz (JIRA)]

Oliver Lietz created SLING-5901:
---

 Summary: Build fails with OOME (Maven Source Plugin 3.0.0)
 Key: SLING-5901
 URL: https://issues.apache.org/jira/browse/SLING-5901
 Project: Sling
  Issue Type: Bug
Affects Versions: Parent 27
Reporter: Oliver Lietz
Priority: Blocker


{noformat}
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-source-plugin:3.0.0:jar (attach-sources) on 
project org.apache.sling.testing.paxexam: Error creating source archive: 
Problem creating jar: Execution exception: Java heap space -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :org.apache.sling.testing.paxexam
{noformat}

See MSOURCES-94 for details.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SLING-5898) Point to the alternative repository if specified on the command-line

[Oliver Lietz (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-5898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15392410#comment-15392410
 ] 

Oliver Lietz commented on SLING-5898:
-

I see [PAXEXAM-543|https://ops4j1.jira.com/browse/PAXEXAM-543] is unresolved, 
but is this really still an issue with latest Pax Exam and Pax URL releases?

> Point to the alternative repository if specified on the command-line
> 
>
> Key: SLING-5898
> URL: https://issues.apache.org/jira/browse/SLING-5898
> Project: Sling
>  Issue Type: Improvement
>  Components: Testing
>Reporter: Robert Munteanu
> Fix For: Testing Pax Exam 0.0.2
>
>
> This is basically SLING-2847 and SLING-2848 applied to the new module. 
> This will help with the situation where we have SNAPSHOT dependencies which 
> by design aren't resolved from the reactor by Pax-Exam.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-5818) make sling pipe writer a persistent configuration

[Nicolas Peltier (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-5818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nicolas Peltier updated SLING-5818:
---
Attachment: SLING-5818.patch

attaching patch that brings in "OutputWriter" interface, 
- PlumberServlet systematically uses it for outputing pipe execution results, 
with default writer outputing size & paths,
- CustomWriter can be defined by adding a "writer" subnode to the resource, 
properties being dubbed in the output (with instantiation of the values),
- CustomJsonWriter is a variation of CustomWriter, that comes from a JSON 
Object passed as a request parameter

> make sling pipe writer a persistent configuration
> -
>
> Key: SLING-5818
> URL: https://issues.apache.org/jira/browse/SLING-5818
> Project: Sling
>  Issue Type: Improvement
>  Components: Extensions
>Reporter: Nicolas Peltier
> Attachments: SLING-5818.patch
>
>
> right now, the only way to configure the output of a pipe is to add a json as 
> parameter of the pipe request. Sometimes the output is as important/complex 
> as the pipe itself, and should be persisted.
> This could be also the opportunity to rewrite how writer is managed in a far 
> from ideal if/else block. 
> servlet/plumber should *always* take a writer in account, and call it each 
> time,
> default being path writer, writer should still be overridable through a 
> request parameter



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SLING-5863) Make the sightly-maven-plugin m2e compatible

[Robert Munteanu (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-5863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15392102#comment-15392102
 ] 

Robert Munteanu commented on SLING-5863:


[~radu.cotescu] - do you think there's anything left to be done here?

> Make the sightly-maven-plugin m2e compatible
> 
>
> Key: SLING-5863
> URL: https://issues.apache.org/jira/browse/SLING-5863
> Project: Sling
>  Issue Type: Improvement
>  Components: Maven Plugins and Archetypes
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
> Fix For: Sightly Maven Plugin 1.0.0
>
> Attachments: 
> 0001-SLING-5863-Make-the-sightly-maven-plugin-m2e-compati.patch
>
>
> Maven plug-ins can easily be made compatible with m2e for transparent 
> integration with Eclipse.
> We should add this to the sightly-maven-plugin and make the compilation 
> results available in Eclipse.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Build failed in Jenkins: sling-trunk-1.8 #3614

[Oliver Lietz]

On Monday 25 July 2016 17:27:42 Robert Munteanu wrote:
> On Mon, 2016-07-25 at 15:26 +0200, Oliver Lietz wrote:
> > On Monday 25 July 2016 15:21:11 Konrad Windszus wrote:
> > > The issue seems to be https://issues.apache.org/jira/browse/MSOURCE
> > > S-94
> > > . It is probably
> > > worth
> > > upgrading maven-source-plugin to 3.0.1. Not sure from where we are
> > > inheriting version 3.0.0 though... Konrad
> > 
> > Yes, see SLING-920. It is from parent org.apache:apache:18.
> > 
> > O.
> 
> I've removed that module from the reactor in https://svn.apache.org/r17
> 54018 until we have a solution which allows the build to succeed.

I don't think that it's the module (3 classes, nothing special) itself but 
that it's last in the build.

O.

> Robert

[jira] [Commented] (SLING-5892) Add smoke tests to the Launchpad

[Robert Munteanu (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-5892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15392016#comment-15392016
 ] 

Robert Munteanu commented on SLING-5892:


Applied in https://svn.apache.org/r1754023 with additional contribution from 
[~bdelacretaz], thanks!

Note that I found some changes in 
{{launchpad/builder/src/main/provisioning/sling.txt}} which look unintentional 
so I've skipped those.

> Add smoke tests to the Launchpad
> 
>
> Key: SLING-5892
> URL: https://issues.apache.org/jira/browse/SLING-5892
> Project: Sling
>  Issue Type: Improvement
>  Components: Launchpad
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
> Fix For: Launchpad Builder 9
>
> Attachments: 0001-SLING-5892-Add-smoke-tests-to-the-Launchpad.patch, 
> 0002-SLING-5892-Add-smoke-tests-to-the-Launchpad.patch
>
>
> The launchpad could benefit from a set of small, quick checks to assert that 
> the build is complete
> - all bundles start
> - the JCR repository starts up
> This would allow the build to fail much earlier and would make root cause 
> analysis simpler, instead of waiting for the 
> {{org.apache.sling.launchpad.testing}} to run and fail a couple of hundreds 
> of tests.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (SLING-5892) Add smoke tests to the Launchpad

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-5892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu resolved SLING-5892.

Resolution: Fixed

> Add smoke tests to the Launchpad
> 
>
> Key: SLING-5892
> URL: https://issues.apache.org/jira/browse/SLING-5892
> Project: Sling
>  Issue Type: Improvement
>  Components: Launchpad
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
> Fix For: Launchpad Builder 9
>
> Attachments: 0001-SLING-5892-Add-smoke-tests-to-the-Launchpad.patch, 
> 0002-SLING-5892-Add-smoke-tests-to-the-Launchpad.patch
>
>
> The launchpad could benefit from a set of small, quick checks to assert that 
> the build is complete
> - all bundles start
> - the JCR repository starts up
> This would allow the build to fail much earlier and would make root cause 
> analysis simpler, instead of waiting for the 
> {{org.apache.sling.launchpad.testing}} to run and fail a couple of hundreds 
> of tests.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (SLING-5900) Improve create agents API handling agents with duplicate IDs

[Ana Vinatoru (JIRA)]

Ana Vinatoru created SLING-5900:
---

 Summary: Improve create agents API handling agents with duplicate 
IDs
 Key: SLING-5900
 URL: https://issues.apache.org/jira/browse/SLING-5900
 Project: Sling
  Issue Type: Bug
  Components: Distribution
Affects Versions: Content Distribution Core 0.1.18
Reporter: Ana Vinatoru
 Fix For: Content Distribution 0.2.0


The distribution agent creation API has the wrong results in the following 
scenarios:

* Scenario 1:
** create agent with id Bob and type Forward
** create agent with id Bob and type Reverse
** the first agent is now replaced by the second one. I think this should be an 
error case (i.e. if there's already an agent with the same ID and a different 
type, the API should return an error).

* Scenario 2
** create agent with id Bob and type Forward
** create agent with id Bob and type Forward
** the properties of the first agent are overwritten by what we inputted at 
step 2

I am using the API from a create / update UI context, so one solution would be 
to add an ":operation" parameter to distinguish between the two cases.

So a "create" on an existing agent resource should fail, regardless of agent 
type, but an "update" should work. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (SLING-5900) Improve create agents API handling of duplicate IDs

[Timothee Maret (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-5900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Timothee Maret reassigned SLING-5900:
-

Assignee: Timothee Maret

> Improve create agents API handling of duplicate IDs
> ---
>
> Key: SLING-5900
> URL: https://issues.apache.org/jira/browse/SLING-5900
> Project: Sling
>  Issue Type: Bug
>  Components: Distribution
>Affects Versions: Content Distribution Core 0.1.18
>Reporter: Ana Vinatoru
>Assignee: Timothee Maret
> Fix For: Content Distribution 0.2.0
>
>
> The distribution agent creation API has the wrong results in the following 
> scenarios:
> * Scenario 1:
> ** create agent with id Bob and type Forward
> ** create agent with id Bob and type Reverse
> ** the first agent is now replaced by the second one. I think this should be 
> an error case (i.e. if there's already an agent with the same ID and a 
> different type, the API should return an error).
> * Scenario 2
> ** create agent with id Bob and type Forward
> ** create agent with id Bob and type Forward
> ** the properties of the first agent are overwritten by what we inputted at 
> step 2
> I am using the API from a create / update UI context, so one solution would 
> be to add an ":operation" parameter to distinguish between the two cases.
> So a "create" on an existing agent resource should fail, regardless of agent 
> type, but an "update" should work. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-5900) Improve create agents API handling of duplicate IDs

[Ana Vinatoru (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-5900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ana Vinatoru updated SLING-5900:

Summary: Improve create agents API handling of duplicate IDs  (was: Improve 
create agents API handling agents with duplicate IDs)

> Improve create agents API handling of duplicate IDs
> ---
>
> Key: SLING-5900
> URL: https://issues.apache.org/jira/browse/SLING-5900
> Project: Sling
>  Issue Type: Bug
>  Components: Distribution
>Affects Versions: Content Distribution Core 0.1.18
>Reporter: Ana Vinatoru
> Fix For: Content Distribution 0.2.0
>
>
> The distribution agent creation API has the wrong results in the following 
> scenarios:
> * Scenario 1:
> ** create agent with id Bob and type Forward
> ** create agent with id Bob and type Reverse
> ** the first agent is now replaced by the second one. I think this should be 
> an error case (i.e. if there's already an agent with the same ID and a 
> different type, the API should return an error).
> * Scenario 2
> ** create agent with id Bob and type Forward
> ** create agent with id Bob and type Forward
> ** the properties of the first agent are overwritten by what we inputted at 
> step 2
> I am using the API from a create / update UI context, so one solution would 
> be to add an ":operation" parameter to distinguish between the two cases.
> So a "create" on an existing agent resource should fail, regardless of agent 
> type, but an "update" should work. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-5891) Make oak restrictions compatible to oak > 1.2

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-5891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu updated SLING-5891:
---
Fix Version/s: Oak Restrictions 1.0.0

> Make oak restrictions compatible to oak > 1.2
> -
>
> Key: SLING-5891
> URL: https://issues.apache.org/jira/browse/SLING-5891
> Project: Sling
>  Issue Type: Improvement
>  Components: Extensions
>Reporter: Georg Henzler
>Assignee: Robert Munteanu
> Fix For: Oak Restrictions 1.0.0
>
>
> The initial version was tested with oak-core v1.2.7, however some users might 
> want to use it with more recent versions (especially 1.4.x). 
> The problematic packages are {{org.apache.jackrabbit.oak.api}} and 
> {{org.apache.jackrabbit.oak.util}}. Usually it is not a good idea to tweak 
> package imports manually, but I think for this particular case there is no 
> other solution to provide compatibility across oak versions. The 
> functionality that is actually used from those two packages is also very 
> basic (Tree, Type, PropertyState and TreeUtil), therefore providing a version 
> range for them is not problematic IMHO.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Build failed in Jenkins: sling-trunk-1.8 #3614

[Robert Munteanu]

On Mon, 2016-07-25 at 15:26 +0200, Oliver Lietz wrote:
> On Monday 25 July 2016 15:21:11 Konrad Windszus wrote:
> > The issue seems to be https://issues.apache.org/jira/browse/MSOURCE
> > S-94
> > . It is probably
> > worth
> > upgrading maven-source-plugin to 3.0.1. Not sure from where we are
> > inheriting version 3.0.0 though... Konrad
> 
> Yes, see SLING-920. It is from parent org.apache:apache:18.
> 
> O.

I've removed that module from the reactor in https://svn.apache.org/r17
54018 until we have a solution which allows the build to succeed.

Robert

[jira] [Resolved] (SLING-5891) Make oak restrictions compatible to oak > 1.2

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-5891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu resolved SLING-5891.

Resolution: Fixed

Patch applied in https://svn.apache.org/r1754017, thanks for the submission!

> Make oak restrictions compatible to oak > 1.2
> -
>
> Key: SLING-5891
> URL: https://issues.apache.org/jira/browse/SLING-5891
> Project: Sling
>  Issue Type: Improvement
>  Components: Extensions
>Reporter: Georg Henzler
>Assignee: Robert Munteanu
> Fix For: Oak Restrictions 1.0.0
>
>
> The initial version was tested with oak-core v1.2.7, however some users might 
> want to use it with more recent versions (especially 1.4.x). 
> The problematic packages are {{org.apache.jackrabbit.oak.api}} and 
> {{org.apache.jackrabbit.oak.util}}. Usually it is not a good idea to tweak 
> package imports manually, but I think for this particular case there is no 
> other solution to provide compatibility across oak versions. The 
> functionality that is actually used from those two packages is also very 
> basic (Tree, Type, PropertyState and TreeUtil), therefore providing a version 
> range for them is not problematic IMHO.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (SLING-5899) "Guages" Typo in Sling metrics console

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-5899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu resolved SLING-5899.

Resolution: Fixed

Fixed in https://svn.apache.org/r1754008 , thanks for spotting this!

> "Guages" Typo in Sling metrics console 
> ---
>
> Key: SLING-5899
> URL: https://issues.apache.org/jira/browse/SLING-5899
> Project: Sling
>  Issue Type: Bug
>  Components: Commons
>Affects Versions: Commons Metrics 1.0.0
>Reporter: Ana Vinatoru
>Assignee: Robert Munteanu
>Priority: Trivial
> Fix For: Commons Metrics 1.0.2
>
>
> There is a small typo in the /system/console/slingmetrics console - "Guages" 
> instead of "Gauges".



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SLING-5890) Documentation for the new sling oak restrictions from SLING-5768

[Robert Munteanu (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-5890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15391973#comment-15391973
 ] 

Robert Munteanu commented on SLING-5890:


Thanks for the patch! I've applied it in https://svn.apache.org/r1754011 and 
it's visible at 
http://sling.apache.org/documentation/bundles/sling-oak-restrictions.html . 

There are some formatting errors related to code listings, could you take a 
look and fix them?

> Documentation for the new sling oak restrictions from SLING-5768
> 
>
> Key: SLING-5890
> URL: https://issues.apache.org/jira/browse/SLING-5890
> Project: Sling
>  Issue Type: Task
>  Components: Extensions
>Reporter: Georg Henzler
>Assignee: Robert Munteanu
> Attachments: sling-oak-restrictions.mdtext
>
>
> Attached the markdown file for the documentation of SLING-5768, I suppose the 
> best location for it is 
> sling/site/trunk/content/documentation/bundles/sling-oak-restrictions.mdtext 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-5837) Allow ResourceChangeListeners to define glob patterns for resource matching

[Radu Cotescu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-5837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu closed SLING-5837.
---

> Allow ResourceChangeListeners to define glob patterns for resource matching
> ---
>
> Key: SLING-5837
> URL: https://issues.apache.org/jira/browse/SLING-5837
> Project: Sling
>  Issue Type: Improvement
>  Components: API
>Affects Versions: API 2.12.0
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
> Fix For: API 2.14.0
>
> Attachments: SLING-5837.patch
>
>
> While the previous way to interact with Resource change events through 
> registering {{EventHandler}} sevices allowed defining glob patterns for 
> matching the watched paths, the current state of the 
> {{org.apache.sling.api.resource.observation.ResourceChangeListener}} only 
> allows subscribing to events for concrete paths.
> In order to allow for the same filtering flexibility, 
> {{ResourceChangeListener}} should also accept glob patterns for its 
> {{resource.paths}} configuration property.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-5899) "Guages" Typo in Sling metrics console

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-5899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu updated SLING-5899:
---
Fix Version/s: Commons Metrics 1.0.2

> "Guages" Typo in Sling metrics console 
> ---
>
> Key: SLING-5899
> URL: https://issues.apache.org/jira/browse/SLING-5899
> Project: Sling
>  Issue Type: Bug
>  Components: Commons
>Affects Versions: Commons Metrics 1.0.0
>Reporter: Ana Vinatoru
>Assignee: Robert Munteanu
>Priority: Trivial
> Fix For: Commons Metrics 1.0.2
>
>
> There is a small typo in the /system/console/slingmetrics console - "Guages" 
> instead of "Gauges".



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (SLING-5899) "Guages" Typo in Sling metrics console

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-5899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu reassigned SLING-5899:
--

Assignee: Robert Munteanu

> "Guages" Typo in Sling metrics console 
> ---
>
> Key: SLING-5899
> URL: https://issues.apache.org/jira/browse/SLING-5899
> Project: Sling
>  Issue Type: Bug
>  Components: Commons
>Affects Versions: Commons Metrics 1.0.0
>Reporter: Ana Vinatoru
>Assignee: Robert Munteanu
>Priority: Trivial
> Fix For: Commons Metrics 1.0.2
>
>
> There is a small typo in the /system/console/slingmetrics console - "Guages" 
> instead of "Gauges".



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[karaf] References to artifacts under vote

[Robert Munteanu]

Hi,

I tried to build the karaf reactor, but it seems to reference releases
to artifacts under vote. Is there a particular reason for doing that? 

The downside is that it's not buildable out-of-the box except with very
specific setups - you either add all staging repositories or mvn
install the missing artifacts from their SVN tags.

Thanks,

Robert

Re: [RESULT][VOTE] Release Apache Sling API 2.14.0

[Oliver Lietz]

On Monday 25 July 2016 13:02:21 Radu Cotescu wrote:
> Hi,
> 
> The vote passed with 3 +1 from Stefan Seifert, Carsten Ziegeler and Oliver
> Lietz. I'll start promoting the release ASAP.

And Radu himself ;)

O.

> Thanks,
> Radu

Re: Build failed in Jenkins: sling-trunk-1.8 #3614

[Oliver Lietz]

On Monday 25 July 2016 15:21:11 Konrad Windszus wrote:
> The issue seems to be https://issues.apache.org/jira/browse/MSOURCES-94
> . It is probably worth
> upgrading maven-source-plugin to 3.0.1. Not sure from where we are
> inheriting version 3.0.0 though... Konrad

Yes, see SLING-920. It is from parent org.apache:apache:18.

O.

[...]

Re: Build failed in Jenkins: sling-trunk-1.8 #3614

[Konrad Windszus]

The issue seems to be https://issues.apache.org/jira/browse/MSOURCES-94 
.
It is probably worth upgrading maven-source-plugin to 3.0.1. Not sure from 
where we are inheriting version 3.0.0 though...
Konrad

> On 25 Jul 2016, at 14:38, Apache Jenkins Server  
> wrote:
> 
> See 
> 
> Changes:
> 
> [olli] SLING-3821 Run launchpad integration tests against Sling on Karaf
> 
> use dynamic HTTP port
> 
> --
> [...truncated 121347 lines...]
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled[INFO] 
> 
> [INFO] Reactor Summary:
> [INFO] 
> [INFO] Apache Sling JAR Resource Bundle ... SUCCESS [  5.247 
> s]
> [INFO] Apache Sling (Parent) .. SUCCESS [ 10.258 
> s]
> [INFO] Apache Sling Tooling Support Install ... SUCCESS [ 11.137 
> s]
> [INFO] Apache Sling Provisioning Model  SUCCESS [ 21.109 
> s]
> [INFO] Apache Sling Tooling Support Source  SUCCESS [  5.028 
> s]
> [INFO] Apache Sling Testing Utilities . SUCCESS [ 31.754 
> s]
> [INFO] Apache Sling API ... SUCCESS [ 16.236 
> s]
> [INFO] Apache Sling Resource Resolver . SUCCESS [ 17.167 
> s]
> [INFO] Apache Sling System Bundle Extension: Java Transaction API SUCCESS [  
> 5.300 s]
> [INFO] Apache Sling System Bundle Extension: XML APIs . SUCCESS [  2.424 
> s]
> [INFO] Apache Sling System Bundle Extension: Activation API SUCCESS [  2.624 
> s]
> [INFO] Apache Sling System Bundle Extension: WS APIs .. SUCCESS [  4.249 
> s]
> [INFO] Apache Sling Dynamic Class Loader Support .. SUCCESS [ 16.022 
> s]
> [INFO] Apache Sling Commons FileSystem ClassLoader  SUCCESS [  7.095 
> s]
> [INFO] Apache Sling Commons Java Compiler . SUCCESS [ 10.128 
> s]
> [INFO] Apache Sling JSON Library .. SUCCESS [ 10.619 
> s]
> [INFO] Apache Sling SLF4J Implementation (Logback)  SUCCESS [ 49.102 
> s]
> [INFO] Apache Sling OSGi LogService Implementation  SUCCESS [  4.393 
> s]
> [INFO] Apache Sling MIME type mapping support . SUCCESS [  5.100 
> s]
> [INFO] Apache Sling Content Detection Support . SUCCESS [01:06 
> min]
> [INFO] Apache Sling Commons OSGi support .. SUCCESS [ 12.901 
> s]
> [INFO] Apache Sling

[RESULT][VOTE] Release Apache Sling API 2.14.0

[Radu Cotescu]

Hi,

The vote passed with 3 +1 from Stefan Seifert, Carsten Ziegeler and Oliver
Lietz. I'll start promoting the release ASAP.

Thanks,
Radu

[jira] [Created] (SLING-5899) "Guages" Typo in Sling metrics console

[Ana Vinatoru (JIRA)]

Ana Vinatoru created SLING-5899:
---

 Summary: "Guages" Typo in Sling metrics console 
 Key: SLING-5899
 URL: https://issues.apache.org/jira/browse/SLING-5899
 Project: Sling
  Issue Type: Bug
  Components: Commons
Affects Versions: Commons Metrics 1.0.0
Reporter: Ana Vinatoru
Priority: Trivial


There is a small typo in the /system/console/slingmetrics console - "Guages" 
instead of "Gauges".



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SLING-5897) Fail the test by default if there are unresolved bundles

[Oliver Lietz (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-5897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15391817#comment-15391817
 ] 

Oliver Lietz commented on SLING-5897:
-

[r1753983|https://svn.apache.org/r1753983]

> Fail the test by default if there are unresolved bundles
> 
>
> Key: SLING-5897
> URL: https://issues.apache.org/jira/browse/SLING-5897
> Project: Sling
>  Issue Type: Improvement
>  Components: Testing
>Reporter: Robert Munteanu
>Assignee: Oliver Lietz
> Fix For: Testing Pax Exam 0.0.2
>
>
> TestOptions.baseConfiguration should by default ensure that the test fails 
> for unresolved bundles:
> {code:java}systemProperty("pax.exam.osgi.unresolved.fail").value("true"){code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (SLING-5897) Fail the test by default if there are unresolved bundles

[Oliver Lietz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-5897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz reassigned SLING-5897:
---

Assignee: Oliver Lietz

> Fail the test by default if there are unresolved bundles
> 
>
> Key: SLING-5897
> URL: https://issues.apache.org/jira/browse/SLING-5897
> Project: Sling
>  Issue Type: Improvement
>  Components: Testing
>Reporter: Robert Munteanu
>Assignee: Oliver Lietz
> Fix For: Testing Pax Exam 0.0.2
>
>
> TestOptions.baseConfiguration should by default ensure that the test fails 
> for unresolved bundles:
> {code:java}systemProperty("pax.exam.osgi.unresolved.fail").value("true"){code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-5870) Switch event ITs to use Oak

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-5870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu updated SLING-5870:
---
Attachment: SLING-5870.zip
0004-SLING-5870-Switch-event-ITs-to-use-Oak.patch
0003-SLING-5870-Switch-event-ITs-to-use-Oak.patch
0002-SLING-5870-Switch-event-ITs-to-use-Oak.patch
0001-SLING-5870-Switch-event-ITs-to-use-Oak.patch

Refreshed to patch set + added a zip file with all patches.

Still does not work unfortunately. By adding the webconsole.plugins.ds bundle I 
was able to verify that the repository is up and components are started.

The JobConsumerManager class, which IIUC is the class used to detect component 
registrations is also properly configured.

I'm out of ideas at this point so I'm going to unassign myself from this task. 
If someone else wants to work on it, feel free.


> Switch event ITs to use Oak
> ---
>
> Key: SLING-5870
> URL: https://issues.apache.org/jira/browse/SLING-5870
> Project: Sling
>  Issue Type: Improvement
>  Components: Extensions
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
> Fix For: Event 4.1.0
>
> Attachments: 0001-SLING-5870-Switch-event-ITs-to-use-Oak.patch, 
> 0001-SLING-5870-Switch-event-ITs-to-use-Oak.patch, 
> 0002-SLING-5870-Switch-event-ITs-to-use-Oak.patch, 
> 0002-SLING-5870-Switch-event-ITs-to-use-Oak.patch, 
> 0003-SLING-5870-Switch-event-ITs-to-use-Oak.patch, 
> 0004-SLING-5870-Switch-event-ITs-to-use-Oak.patch, 
> SLING-5870.testing-paxexam.patch, SLING-5870.zip, test.log
>
>
> The Event ITs sometimes fail on Jenkins, and the errors seem to indicate 
> inconsistencies in the repository, e.g.
> {code}19.07.2016 09:57:31.489 *WARN* [Apache Sling JCR Resource Event Queue 
> Processor] org.apache.sling.jcr.resource.internal.JcrResourceListener 
> processOsgiEventQueue: Unexpected problem processing event 
> {path=/var/eventing/jobs/assigned/f96f5677-4d3b-454d-9dc1-c2ee9270b35c/sling.chaos.round.4/2016/7/19/9/53/f96f5677-4d3b-454d-9dc1-c2ee9270b35c_2931,
>  resourceChangedAttributes=[Ljava.lang.String;@51e6a8e1, 
> resourceAddedAttributes=[Ljava.lang.String;@1447afb0, userid=admin}
> org.apache.sling.api.SlingException: Problem retrieving node based resource 
> /var/eventing/jobs/assigned/f96f5677-4d3b-454d-9dc1-c2ee9270b35c/sling.chaos.round.4/2016/7/19/9/53/f96f5677-4d3b-454d-9dc1-c2ee9270b35c_2931
>   at 
> org.apache.sling.jcr.resource.internal.helper.jcr.JcrResourceProvider.getResource(JcrResourceProvider.java:156)
>   at 
> org.apache.sling.jcr.resource.internal.helper.jcr.JcrResourceProvider.getResource(JcrResourceProvider.java:143)
>   at 
> org.apache.sling.resourceresolver.impl.tree.ResourceProviderFactoryHandler.getResource(ResourceProviderFactoryHandler.java:113)
>   at 
> org.apache.sling.resourceresolver.impl.tree.ResourceProviderEntry.getResourceFromProviders(ResourceProviderEntry.java:401)
>   at 
> org.apache.sling.resourceresolver.impl.tree.ResourceProviderEntry.getInternalResource(ResourceProviderEntry.java:356)
>   at 
> org.apache.sling.resourceresolver.impl.tree.ResourceProviderEntry.getResource(ResourceProviderEntry.java:138)
>   at 
> org.apache.sling.resourceresolver.impl.ResourceResolverImpl.getAbsoluteResourceInternal(ResourceResolverImpl.java:988)
>   at 
> org.apache.sling.resourceresolver.impl.ResourceResolverImpl.getResourceInternal(ResourceResolverImpl.java:635)
>   at 
> org.apache.sling.resourceresolver.impl.ResourceResolverImpl.getResource(ResourceResolverImpl.java:590)
>   at 
> org.apache.sling.jcr.resource.internal.JcrResourceListener.processOsgiEventQueue(JcrResourceListener.java:340)
>   at 
> org.apache.sling.jcr.resource.internal.JcrResourceListener$1.run(JcrResourceListener.java:107)
>   at java.lang.Thread.run(Thread.java:744)
> Caused by: javax.jcr.PathNotFoundException: 
> /var/eventing/jobs/assigned/f96f5677-4d3b-454d-9dc1-c2ee9270b35c/sling.chaos.round.4/2016/7/19/9/53/f96f5677-4d3b-454d-9dc1-c2ee9270b35c_2931
>   at org.apache.jackrabbit.core.ItemManager.getItem(ItemManager.java:552)
>   at 
> org.apache.jackrabbit.core.session.SessionItemOperation$4.perform(SessionItemOperation.java:97)
>   at 
> org.apache.jackrabbit.core.session.SessionItemOperation$4.perform(SessionItemOperation.java:93)
>   at 
> org.apache.jackrabbit.core.session.SessionItemOperation.perform(SessionItemOperation.java:187)
>   at 
> org.apache.jackrabbit.core.session.SessionState.perform(SessionState.java:216)
>   at org.apache.jackrabbit.core.SessionImpl.perform(SessionImpl.java:361)
>   at org.apache.jackrabbit.core.SessionImpl.getItem(SessionImpl.java:786)
>   at 
> org.apache.sling.jcr.resource.internal.helper.jcr.JcrResourceProvider.createResource(JcrResour

[jira] [Updated] (SLING-5870) Switch event ITs to use Oak

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-5870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu updated SLING-5870:
---
Assignee: (was: Robert Munteanu)

> Switch event ITs to use Oak
> ---
>
> Key: SLING-5870
> URL: https://issues.apache.org/jira/browse/SLING-5870
> Project: Sling
>  Issue Type: Improvement
>  Components: Extensions
>Reporter: Robert Munteanu
> Fix For: Event 4.1.0
>
> Attachments: 0001-SLING-5870-Switch-event-ITs-to-use-Oak.patch, 
> 0001-SLING-5870-Switch-event-ITs-to-use-Oak.patch, 
> 0002-SLING-5870-Switch-event-ITs-to-use-Oak.patch, 
> 0002-SLING-5870-Switch-event-ITs-to-use-Oak.patch, 
> 0003-SLING-5870-Switch-event-ITs-to-use-Oak.patch, 
> 0004-SLING-5870-Switch-event-ITs-to-use-Oak.patch, 
> SLING-5870.testing-paxexam.patch, SLING-5870.zip, test.log
>
>
> The Event ITs sometimes fail on Jenkins, and the errors seem to indicate 
> inconsistencies in the repository, e.g.
> {code}19.07.2016 09:57:31.489 *WARN* [Apache Sling JCR Resource Event Queue 
> Processor] org.apache.sling.jcr.resource.internal.JcrResourceListener 
> processOsgiEventQueue: Unexpected problem processing event 
> {path=/var/eventing/jobs/assigned/f96f5677-4d3b-454d-9dc1-c2ee9270b35c/sling.chaos.round.4/2016/7/19/9/53/f96f5677-4d3b-454d-9dc1-c2ee9270b35c_2931,
>  resourceChangedAttributes=[Ljava.lang.String;@51e6a8e1, 
> resourceAddedAttributes=[Ljava.lang.String;@1447afb0, userid=admin}
> org.apache.sling.api.SlingException: Problem retrieving node based resource 
> /var/eventing/jobs/assigned/f96f5677-4d3b-454d-9dc1-c2ee9270b35c/sling.chaos.round.4/2016/7/19/9/53/f96f5677-4d3b-454d-9dc1-c2ee9270b35c_2931
>   at 
> org.apache.sling.jcr.resource.internal.helper.jcr.JcrResourceProvider.getResource(JcrResourceProvider.java:156)
>   at 
> org.apache.sling.jcr.resource.internal.helper.jcr.JcrResourceProvider.getResource(JcrResourceProvider.java:143)
>   at 
> org.apache.sling.resourceresolver.impl.tree.ResourceProviderFactoryHandler.getResource(ResourceProviderFactoryHandler.java:113)
>   at 
> org.apache.sling.resourceresolver.impl.tree.ResourceProviderEntry.getResourceFromProviders(ResourceProviderEntry.java:401)
>   at 
> org.apache.sling.resourceresolver.impl.tree.ResourceProviderEntry.getInternalResource(ResourceProviderEntry.java:356)
>   at 
> org.apache.sling.resourceresolver.impl.tree.ResourceProviderEntry.getResource(ResourceProviderEntry.java:138)
>   at 
> org.apache.sling.resourceresolver.impl.ResourceResolverImpl.getAbsoluteResourceInternal(ResourceResolverImpl.java:988)
>   at 
> org.apache.sling.resourceresolver.impl.ResourceResolverImpl.getResourceInternal(ResourceResolverImpl.java:635)
>   at 
> org.apache.sling.resourceresolver.impl.ResourceResolverImpl.getResource(ResourceResolverImpl.java:590)
>   at 
> org.apache.sling.jcr.resource.internal.JcrResourceListener.processOsgiEventQueue(JcrResourceListener.java:340)
>   at 
> org.apache.sling.jcr.resource.internal.JcrResourceListener$1.run(JcrResourceListener.java:107)
>   at java.lang.Thread.run(Thread.java:744)
> Caused by: javax.jcr.PathNotFoundException: 
> /var/eventing/jobs/assigned/f96f5677-4d3b-454d-9dc1-c2ee9270b35c/sling.chaos.round.4/2016/7/19/9/53/f96f5677-4d3b-454d-9dc1-c2ee9270b35c_2931
>   at org.apache.jackrabbit.core.ItemManager.getItem(ItemManager.java:552)
>   at 
> org.apache.jackrabbit.core.session.SessionItemOperation$4.perform(SessionItemOperation.java:97)
>   at 
> org.apache.jackrabbit.core.session.SessionItemOperation$4.perform(SessionItemOperation.java:93)
>   at 
> org.apache.jackrabbit.core.session.SessionItemOperation.perform(SessionItemOperation.java:187)
>   at 
> org.apache.jackrabbit.core.session.SessionState.perform(SessionState.java:216)
>   at org.apache.jackrabbit.core.SessionImpl.perform(SessionImpl.java:361)
>   at org.apache.jackrabbit.core.SessionImpl.getItem(SessionImpl.java:786)
>   at 
> org.apache.sling.jcr.resource.internal.helper.jcr.JcrResourceProvider.createResource(JcrResourceProvider.java:211)
>   at 
> org.apache.sling.jcr.resource.internal.helper.jcr.JcrResourceProvider.getResource(JcrResourceProvider.java:154)
>   ... 11 common frames omitted{code}
> Moving to Oak might help with these issues, and it's anyway a good idea since 
> the default Launchpad only includes Sling ATM.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SLING-3821) Run launchpad integration tests against Sling on Karaf

[Oliver Lietz (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-3821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15391777#comment-15391777
 ] 

Oliver Lietz commented on SLING-3821:
-

Test result for {{org.apache.sling.launchpad.integration-tests}} {{1.0.2}}:

||Tests||Errors||Failures||Skipped||
|557|8|2|2|

Test result when excluding:

* -{{FiltersTest}}- (Felix HTTP only)
* -{{WarSelectorServletTest}}- (WAR support)
* -{{EmbeddedModelTest}}- (Lauchpad only)
* {{SlingWebDavServletTest}}
* {{WebdavDeleteTest}}
* {{AuthenticationResponseCodeTest}}
* {{UpdateUserTest}}
* {{JspForwardTest}}
* {{RepoinitPathTest}}
* {{SystemUsersTest}}

||Tests||Errors||Failures||Skipped||
|528|0|0|2|

> Run launchpad integration tests against Sling on Karaf
> --
>
> Key: SLING-3821
> URL: https://issues.apache.org/jira/browse/SLING-3821
> Project: Sling
>  Issue Type: Test
>  Components: Launchpad
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: New module Sling Testing PaxExam

[Robert Munteanu]

On Fri, 2016-07-22 at 19:53 +0200, Oliver Lietz wrote:
> On Thursday 21 July 2016 19:06:37 Robert Munteanu wrote:
> > On Thu, 2016-07-21 at 13:59 +0200, Oliver Lietz wrote:
> > > On Wednesday 20 July 2016 17:24:15 Robert Munteanu wrote:
> [...]
> > > That can be done always by editing SlingVersionResolver.java
> > > directly.
> > > Using feature.xml should ensure (tests in bootstrap) that all
> > > bundles
> > > are 
> > > compatible (form a runnable Sling instance) and updates don't
> > > have to
> > > be done 
> > > twice.
> > 
> > Right, I think that's the toughest part - making sure the bundle
> > versions
> > are in sync.
> > 
> > Also, a couple of suggestions related to further reducing the
> > boilerplate.
> > 
> > 1. Simpler HTTP port detection
> > 
> > If no http port is specified we can just pick a random one and log
> > it, or
> > otherwise we have
> > 
> >    withHttpPort(int port);
> > 
> > method which takes a specified HTTP port.
> > 
> > 2. Automatic management of the working directory
> > 
> > In the event ITs we manually manage:
> > 
> > - the working directory
> > - sling.home
> > - repository.home ( or alternatively the OSGi configs for the
> > segment node
> > store and the lucene index provider )
> > 
> > Could we also move these inside the module? I don't think we even
> > need a
> > config option here, just auto-manage them.
> > 
> > If you agree, I'll file enhancement requests.
> 
> See my latest commits in Testing PaxExam (SLING-5893 and SLING-5894)
> and 
> Scripting Thymeleaf. There is now test support (similar to what I've
> done for 
> Launchpad Karaf ITs) and a default configuration. I've tried to find
> the 
> perfect balance between automation and adaptability.
> 
> Let me know if it works for you.

Looks good, thank you! If I get one more nitpick :-) it would be asking
to include the oak-segment bundle declaration in the method that
configures it ( slingLaunchpadOakTarConfiguration ). If I invoke that
method it's clear that I want the oak-segment bundle included as well.

I've also filed a couple of enhancement requests based on what I have
seen in other modules - basically boilerplate we copy/paste between
@Configuration methods.

Other than that, it's not 100% clear to me why, but it seems that there
isn't a 'good' Servlet API bundle included in the current SlingOptions
class. There is the geronimo specs Jar, but IIUC it's for version 3.0
only and we use 3.1 already in some place.

I've solved this by adding 

  mavenBundle().groupId("org.apache.felix").artifactId("org.apache.feli
x.http.servlet-api").version("1.1.2")

to the build.

Thanks,

Robert

[jira] [Created] (SLING-5898) Point to the alternative repository if specified on the command-line

[Robert Munteanu (JIRA)]

Robert Munteanu created SLING-5898:
--

 Summary: Point to the alternative repository if specified on the 
command-line
 Key: SLING-5898
 URL: https://issues.apache.org/jira/browse/SLING-5898
 Project: Sling
  Issue Type: Improvement
  Components: Testing
Reporter: Robert Munteanu
 Fix For: Testing Pax Exam 0.0.2


This is basically SLING-2847 and SLING-2848 applied to the new module. 

This will help with the situation where we have SNAPSHOT dependencies which by 
design aren't resolved from the reactor by Pax-Exam.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (SLING-5897) Fail the test by default if there are unresolved bundles

[Robert Munteanu (JIRA)]

Robert Munteanu created SLING-5897:
--

 Summary: Fail the test by default if there are unresolved bundles
 Key: SLING-5897
 URL: https://issues.apache.org/jira/browse/SLING-5897
 Project: Sling
  Issue Type: Improvement
  Components: Testing
Reporter: Robert Munteanu
 Fix For: Testing Pax Exam 0.0.2


TestOptions.baseConfiguration should by default ensure that the test fails for 
unresolved bundles:

{code:java}systemProperty("pax.exam.osgi.unresolved.fail").value("true"){code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (SLING-5896) Include org.apache.felix.webconsole.plugins.ds in SlingOptions.webconsole

[Robert Munteanu (JIRA)]

Robert Munteanu created SLING-5896:
--

 Summary: Include org.apache.felix.webconsole.plugins.ds in 
SlingOptions.webconsole
 Key: SLING-5896
 URL: https://issues.apache.org/jira/browse/SLING-5896
 Project: Sling
  Issue Type: Improvement
  Components: Testing
Reporter: Robert Munteanu
 Fix For: Testing Pax Exam 0.0.2


When debugging a proper pax-exam setup the DS webconsole helps a lot. It would 
be good to include it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: LoginAdministrative whitelisting patch ready for review

[Bertrand Delacretaz]

Hi,

On Fri, Jul 22, 2016 at 5:13 PM, Carsten Ziegeler  wrote:
>> https://issues.apache.org/jira/browse/SLING-5135 ...
> What about provisioning the whitelist with the usual Sling core bundles
> that are used in an installation, so you can run a "simple" Sling
> without any configuration?...

The problem with such a hardcoded default configuration is the need to
release the bundle if we need to change that config.

Right now the below whitelist [1] is needed for most of the launchpad
integration tests to pass.

While some bundles like oak.server are obviously ok, others might need
deeper investigation which I wasn't planning to do right now, so I'd
prefer starting with an empy config. Unless someone can look at those
bundles to reduce the list.

-Bertrand

[1]
"org.apache.sling.extensions.webconsolesecurityprovider",
"org.apache.sling.jcr.base"
"org.apache.sling.jcr.contentloader",
"org.apache.sling.jcr.davex",
"org.apache.sling.jcr.jackrabbit.usermanager",
"org.apache.sling.jcr.webconsole",
"org.apache.sling.jcr.webdav",
"org.apache.sling.servlets.post",
"org.apache.sling.jcr.oak.server",
"org.apache.sling.installer.provider.jcr",
"org.apache.sling.jcr.resource"]

[jira] [Commented] (SLING-5866) DefaultGetServlet obtains input stream for binary even if request is a HEAD

[Bertrand Delacretaz (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-5866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15391561#comment-15391561
 ] 

Bertrand Delacretaz commented on SLING-5866:


https://github.com/apache/sling/pull/156 looks mostly ok but I don't see any 
test code in it. 

Did you verify (and how) that your new code is executed by our current test 
suite and doesn't introduce any regressions?
Otherwise we need unit or integration test code, feel free to ask our our dev 
list if you need help in writing that.

Apart from that and unless that complicates think I'd like the 
{{HeadServletResponse}} class to be in its own java file, and that might also 
make it easier to test.

> DefaultGetServlet obtains input stream for binary even if request is a HEAD
> ---
>
> Key: SLING-5866
> URL: https://issues.apache.org/jira/browse/SLING-5866
> Project: Sling
>  Issue Type: Improvement
>  Components: Servlets
>Affects Versions: Servlets Get 2.1.14
>Reporter: Ankit Agarwal
>
> As per current implementation any HEAD request will be handled by 
> defaultHeadServlet which majorly does two changes
> 1.) coverts response output stream to be null so that there should be no 
> message body in response
> 2.)  coverts HEAD request to GET request. 
> Now this request is dispatched and served by defaultGetServlet.
> With this approach, we get the desired output but response is delayed as it 
> reads the complete binary data of a resource. and also it increases data 
> transfer which is not needed.
> So IMO this approach should be improved.
> thanks,



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [VOTE] Release Apache Sling Launchpad Testing Fragment Bundle 2.0.10

[Robert Munteanu]

On Mon, 2016-07-25 at 09:51 +0200, Bertrand Delacretaz wrote:
> Please vote to approve this release:

+1

Robert

signature.asc
Description: This is a digitally signed message part

[jira] [Updated] (SLING-5892) Add smoke tests to the Launchpad

[Bertrand Delacretaz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-5892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bertrand Delacretaz updated SLING-5892:
---
Attachment: 0002-SLING-5892-Add-smoke-tests-to-the-Launchpad.patch

Looks good to me, thanks for this!

Here's patch 0002 which just additionally verifies that there are at least 125 
bundles present.

> Add smoke tests to the Launchpad
> 
>
> Key: SLING-5892
> URL: https://issues.apache.org/jira/browse/SLING-5892
> Project: Sling
>  Issue Type: Improvement
>  Components: Launchpad
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
> Fix For: Launchpad Builder 9
>
> Attachments: 0001-SLING-5892-Add-smoke-tests-to-the-Launchpad.patch, 
> 0002-SLING-5892-Add-smoke-tests-to-the-Launchpad.patch
>
>
> The launchpad could benefit from a set of small, quick checks to assert that 
> the build is complete
> - all bundles start
> - the JCR repository starts up
> This would allow the build to fail much earlier and would make root cause 
> analysis simpler, instead of waiting for the 
> {{org.apache.sling.launchpad.testing}} to run and fail a couple of hundreds 
> of tests.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SLING-920) Sling Jenkins setup

[Oliver Lietz (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15391510#comment-15391510
 ] 

Oliver Lietz commented on SLING-920:


Oh yes, looks like a problem with {{plexus-archiver}} which is fixed by 
{{maven-source-plugin}} {{3.0.1}}: MSOURCES-94

> Sling Jenkins setup
> ---
>
> Key: SLING-920
> URL: https://issues.apache.org/jira/browse/SLING-920
> Project: Sling
>  Issue Type: Task
>  Components: Testing
>Reporter: Bertrand Delacretaz
>
> Use this issue to record changes to the Jenkins setup at 
> https://builds.apache.org/view/S-Z/view/Sling/



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

RE: [VOTE] Release Apache Sling Launchpad Testing Fragment Bundle 2.0.10

[Stefan Seifert]

+1

[jira] [Updated] (SLING-3017) Improve Karaf integration tests

[Oliver Lietz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-3017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz updated SLING-3017:

Component/s: (was: Launchpad)
 Karaf

> Improve Karaf integration tests
> ---
>
> Key: SLING-3017
> URL: https://issues.apache.org/jira/browse/SLING-3017
> Project: Sling
>  Issue Type: Improvement
>  Components: Karaf
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
>Priority: Minor
> Fix For: Karaf Integration Tests 0.2.0
>
> Attachments: SLING-3017.patch
>
>
> - separate testing support and test into own packages and jars
> - use Maven Failsafe Plugin for tests
> - update Pax Exam to 4.8.0
> - enable test (remove Ignore annotation)
> - increase timeouts to 30 ms
> - test features



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-5700) Update Pax Exam to 4.9.1

[Oliver Lietz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-5700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz updated SLING-5700:

Component/s: Karaf

> Update Pax Exam to 4.9.1
> 
>
> Key: SLING-5700
> URL: https://issues.apache.org/jira/browse/SLING-5700
> Project: Sling
>  Issue Type: Task
>  Components: Karaf, Launchpad, Scripting, Testing
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
>Priority: Minor
> Fix For: Karaf Integration Tests 0.2.0, Commons Messaging Mail 
> 1.0.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-4411) Provide Oak features

[Oliver Lietz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-4411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz updated SLING-4411:

Component/s: (was: Launchpad)
 Karaf

> Provide Oak features
> 
>
> Key: SLING-4411
> URL: https://issues.apache.org/jira/browse/SLING-4411
> Project: Sling
>  Issue Type: New Feature
>  Components: Karaf
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Karaf Features 0.2.0
>
>
> provide features for Oak as we have now for Jackrabbit:
> * {{oak-sling}}
> * {{sling-jcr-oak}}
> * {{sling-launchpad-oak}}
> * {{sling-launchpad-oak-tar}}
> * {{sling-launchpad-oak-mongo}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-4571) provide XSS feature

[Oliver Lietz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-4571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz updated SLING-4571:

Component/s: (was: Launchpad)
 Karaf

> provide XSS feature
> ---
>
> Key: SLING-4571
> URL: https://issues.apache.org/jira/browse/SLING-4571
> Project: Sling
>  Issue Type: New Feature
>  Components: Karaf
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Karaf Features 0.2.0
>
>
> {{sling-extension-xss}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-4569) provide Health Check feature

[Oliver Lietz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-4569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz updated SLING-4569:

Component/s: (was: Launchpad)
 Karaf

> provide Health Check feature
> 
>
> Key: SLING-4569
> URL: https://issues.apache.org/jira/browse/SLING-4569
> Project: Sling
>  Issue Type: New Feature
>  Components: Karaf
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Karaf Features 0.2.0
>
>
> {{sling-extension-healthcheck}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-4570) provide Distribution feature

[Oliver Lietz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-4570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz updated SLING-4570:

Component/s: (was: Launchpad)
 Karaf

> provide Distribution feature
> 
>
> Key: SLING-4570
> URL: https://issues.apache.org/jira/browse/SLING-4570
> Project: Sling
>  Issue Type: New Feature
>  Components: Karaf
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Karaf Features 0.2.0
>
>
> {{sling-extension-distribution}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-4412) Upgrade Karaf to 4.0

[Oliver Lietz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-4412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz updated SLING-4412:

Component/s: (was: Launchpad)
 Karaf

> Upgrade Karaf to 4.0
> 
>
> Key: SLING-4412
> URL: https://issues.apache.org/jira/browse/SLING-4412
> Project: Sling
>  Issue Type: Improvement
>  Components: Karaf
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Karaf Features 0.2.0, Karaf Integration Tests 0.2.0
>
> Attachments: SLING-4412.WIP.patch, 
> bring_down_by_installing_feature-karaf.log
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-4572) provide JCR Compiler feature

[Oliver Lietz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-4572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz updated SLING-4572:

Component/s: (was: Launchpad)
 Karaf

> provide JCR Compiler feature
> 
>
> Key: SLING-4572
> URL: https://issues.apache.org/jira/browse/SLING-4572
> Project: Sling
>  Issue Type: New Feature
>  Components: Karaf
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Karaf Features 0.2.0
>
>
> {{sling-jcr-compiler}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-4573) provide Scripting Sightly feature

[Oliver Lietz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-4573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz updated SLING-4573:

Component/s: (was: Launchpad)
 Karaf

> provide Scripting Sightly feature
> -
>
> Key: SLING-4573
> URL: https://issues.apache.org/jira/browse/SLING-4573
> Project: Sling
>  Issue Type: New Feature
>  Components: Karaf
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Karaf Features 0.2.0
>
>
> {{sling-scripting-sightly}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-4574) update Jackrabbit and Oak

[Oliver Lietz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-4574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz updated SLING-4574:

Component/s: (was: Launchpad)
 Karaf

> update Jackrabbit and Oak
> -
>
> Key: SLING-4574
> URL: https://issues.apache.org/jira/browse/SLING-4574
> Project: Sling
>  Issue Type: Improvement
>  Components: Karaf
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Karaf Features 0.2.0
>
>
> Jackrabbit {{2.10.0}} and Oak {{1.0.12}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-3027) Improve Karaf Features

[Oliver Lietz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz updated SLING-3027:

Component/s: (was: Launchpad)
 Karaf

> Improve Karaf Features
> --
>
> Key: SLING-3027
> URL: https://issues.apache.org/jira/browse/SLING-3027
> Project: Sling
>  Issue Type: Improvement
>  Components: Karaf
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
>Priority: Minor
> Fix For: Karaf Features 0.2.0
>
>
> - break down sling-karaf feature into more fine-grained features for better 
> reusability
> - add descriptions -and versions-
> - add more features
> - update integration tests
> - update Pax Exam to latest
> - update Karaf to 4.x
> - update Maven Failsafe Plugin to 2.17
> - -add workaround for KARAF-1972-
> - update README
> - cleanup



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-4636) provide Security feature

[Oliver Lietz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-4636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz updated SLING-4636:

Component/s: (was: Launchpad)
 Karaf

> provide Security feature
> 
>
> Key: SLING-4636
> URL: https://issues.apache.org/jira/browse/SLING-4636
> Project: Sling
>  Issue Type: New Feature
>  Components: Karaf
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
>Priority: Minor
> Fix For: Karaf Features 0.2.0, Karaf Integration Tests 0.2.0
>
>
> {{sling-extension-security}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-4637) provide Validation feature

[Oliver Lietz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-4637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz updated SLING-4637:

Component/s: (was: Launchpad)
 Karaf

> provide Validation feature
> --
>
> Key: SLING-4637
> URL: https://issues.apache.org/jira/browse/SLING-4637
> Project: Sling
>  Issue Type: New Feature
>  Components: Karaf
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Karaf Features 0.2.0, Karaf Integration Tests 0.2.0
>
>
> {{sling-extension-validation}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-4648) Provide Sling Commons features

[Oliver Lietz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-4648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz updated SLING-4648:

Component/s: (was: Launchpad)
 Karaf

> Provide Sling Commons features
> --
>
> Key: SLING-4648
> URL: https://issues.apache.org/jira/browse/SLING-4648
> Project: Sling
>  Issue Type: New Feature
>  Components: Karaf
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Karaf Features 0.2.0, Karaf Integration Tests 0.2.0
>
>
> http://mail-archives.apache.org/mod_mbox/karaf-user/201504.mbox/%3cCAAHmKFzs9_fyDS9=stg_ewtse5bi3sjxt9ltuqa0wmbhqui...@mail.gmail.com%3e
> {{sling-commons-scheduler}}
> {{sling-commons-threads}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-4576) drop individual feature versions and use project version instead

[Oliver Lietz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-4576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz updated SLING-4576:

Component/s: (was: Launchpad)
 Karaf

> drop individual feature versions and use project version instead
> 
>
> Key: SLING-4576
> URL: https://issues.apache.org/jira/browse/SLING-4576
> Project: Sling
>  Issue Type: Task
>  Components: Karaf
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Karaf Features 0.2.0
>
>
> individual feature versions are not useful at all, stick to Karaf's pattern 
> and use project version



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-4911) Upgrade to Oak 1.3.3

[Oliver Lietz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-4911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz updated SLING-4911:

Component/s: Karaf

> Upgrade to Oak 1.3.3
> 
>
> Key: SLING-4911
> URL: https://issues.apache.org/jira/browse/SLING-4911
> Project: Sling
>  Issue Type: Improvement
>  Components: Karaf, Launchpad, Oak
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: JCR Oak Server 1.0.0, Karaf Features 0.2.0, Launchpad 
> Builder 8
>
>
> * {{bundles/jcr/it-jackrabbit-oak/pom.xml}}
> * {{bundles/jcr/oak-server/pom.xml}}
> * {{launchpad/builder/src/main/provisioning/oak.txt}}
> * 
> {{contrib/launchpad/karaf/org.apache.sling.launchpad.karaf-features/src/main/feature/feature.xml}}
> SLING-4873



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-4873) Upgrade to Oak 1.3.2

[Oliver Lietz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-4873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz updated SLING-4873:

Component/s: Karaf

> Upgrade to Oak 1.3.2
> 
>
> Key: SLING-4873
> URL: https://issues.apache.org/jira/browse/SLING-4873
> Project: Sling
>  Issue Type: Improvement
>  Components: Karaf, Launchpad, Oak
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: JCR Oak Server 1.0.0, Karaf Features 0.2.0, Launchpad 
> Builder 8
>
>
> using unstable branch {{1.3}} should be noncritical as [Moving to 
> Oak|SLING-4528] is still work in progress



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-4890) provide Feature Flags feature

[Oliver Lietz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-4890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz updated SLING-4890:

Component/s: Karaf

> provide Feature Flags feature
> -
>
> Key: SLING-4890
> URL: https://issues.apache.org/jira/browse/SLING-4890
> Project: Sling
>  Issue Type: New Feature
>  Components: Karaf
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
>Priority: Minor
> Fix For: Karaf Features 0.2.0, Karaf Integration Tests 0.2.0
>
>
> {{sling-extension-featureflags}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-4868) provide Karaf Archive of Launchpad features

[Oliver Lietz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-4868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz updated SLING-4868:

Component/s: (was: Launchpad)
 Karaf

> provide Karaf Archive of Launchpad features
> ---
>
> Key: SLING-4868
> URL: https://issues.apache.org/jira/browse/SLING-4868
> Project: Sling
>  Issue Type: New Feature
>  Components: Karaf
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Karaf Features 0.2.0
>
>
> [Karaf Archive - 
> KAR|http://karaf.apache.org/manual/latest/users-guide/kar.html]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-4871) use component configurations (Config Admin) instead of framework properties

[Oliver Lietz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-4871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz updated SLING-4871:

Component/s: Karaf

> use component configurations (Config Admin) instead of framework properties
> ---
>
> Key: SLING-4871
> URL: https://issues.apache.org/jira/browse/SLING-4871
> Project: Sling
>  Issue Type: Improvement
>  Components: Best practices, Karaf, Launchpad
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Karaf Features 0.2.0, Launchpad Builder 8
>
>
> framework properties have several drawbacks (as discussed in SLING-4649)
> * framework properties have to be set before framework start
> * framework properties can not be changed at runtime
> * framework properties can be shared by multiple components _but_ are used as 
> a last resort here only
> * component configurations otherwise can be created and changed at runtime
> * component configurations serve as documentation also
> for components falling back to {{repository.home}} (found by [~rombert]) 
> additionally configurations may be required:
> {noformat}
> oak-blob/src/main/java/org/apache/jackrabbit/oak/spi/blob/osgi/FileBlobStoreService.java:
> private static final String PROP_HOME = "repository.home";
> oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/blob/datastore/AbstractDataStoreService.java:
> private static final String PROP_HOME = "repository.home";
> oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/segment/SegmentNodeStoreService.java:
> public static final String DIRECTORY = "repository.home";
> oak-lucene/src/main/java/org/apache/jackrabbit/oak/plugins/index/lucene/LuceneIndexProviderService.java:
> public static final String REPOSITORY_HOME = "repository.home";
> {noformat}
> Not setting {{repository.home}} points us quickly to missing component 
> configurations.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[RESULT][VOTE] Release Apache Sling Launchpad Testing Services 2.0.10, Testing Services WAR 2.0.10, Apache Sling Integration Tests 1.0.2

[Bertrand Delacretaz]

On Thu, Jul 21, 2016 at 3:17 PM, Bertrand Delacretaz
 wrote:
> ...Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-1484/ ...

The vote passes with four +1s and no other votes, thanks!

I'll take care of the remaining steps.

-Bertrand

[jira] [Updated] (SLING-5119) Update Mongo Java Driver to 2.13.3

[Oliver Lietz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-5119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz updated SLING-5119:

Component/s: Karaf

> Update Mongo Java Driver to 2.13.3
> --
>
> Key: SLING-5119
> URL: https://issues.apache.org/jira/browse/SLING-5119
> Project: Sling
>  Issue Type: Sub-task
>  Components: Karaf, Launchpad, Oak
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Karaf Features 0.2.0, Launchpad Builder 8
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-4995) Upgrade to Oak 1.3.4

[Oliver Lietz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-4995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz updated SLING-4995:

Component/s: Oak
 Launchpad
 Karaf

> Upgrade to Oak 1.3.4
> 
>
> Key: SLING-4995
> URL: https://issues.apache.org/jira/browse/SLING-4995
> Project: Sling
>  Issue Type: Task
>  Components: Karaf, Launchpad, Oak
>Reporter: Bertrand Delacretaz
>Assignee: Bertrand Delacretaz
> Fix For: JCR Oak Server 1.0.0, Karaf Features 0.2.0, Launchpad 
> Builder 8
>
>
> Oak 1.3.4 is the latest release



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-5120) align repository.home and localIndexDir with Launchpad

[Oliver Lietz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-5120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz updated SLING-5120:

Component/s: Karaf

> align repository.home and localIndexDir with Launchpad
> --
>
> Key: SLING-5120
> URL: https://issues.apache.org/jira/browse/SLING-5120
> Project: Sling
>  Issue Type: Improvement
>  Components: Karaf, Launchpad
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Karaf Features 0.2.0
>
>
> set {{repository.home}} to {{sling/repository}} and {{localIndexDir}} to 
> {{sling/repository/index}} (remove {{oak}} from paths)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[VOTE] Release Apache Sling Launchpad Testing Fragment Bundle 2.0.10

[Bertrand Delacretaz]

Hi,

This is the first release of this minor module, used by one test in
the lauchpad/integration-tests module that we are releasing.

Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-1486/

You can use this UNIX script to download the release and verify the signatures:
http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh

Usage:
sh check_staged_release.sh 1486 /tmp/sling-staging

Please vote to approve this release:

  [ ] +1 Approve the release
  [ ]  0 Don't care
  [ ] -1 Don't release, because ...

This majority vote is open for at least 72 hours.

Here's my +1.

[jira] [Commented] (SLING-920) Sling Jenkins setup

[Robert Munteanu (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15391492#comment-15391492
 ] 

Robert Munteanu commented on SLING-920:
---

If you look at the [full build 
output|https://builds.apache.org/job/sling-trunk-1.7/4354/consoleText] you'll 
see the problem reported at the end:

{noformat}[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-source-plugin:3.0.0:jar (attach-sources) on 
project org.apache.sling.testing.paxexam: Error creating source archive: 
Problem creating jar: Execution exception: Java heap space -> [Help 1]{noformat}

> Sling Jenkins setup
> ---
>
> Key: SLING-920
> URL: https://issues.apache.org/jira/browse/SLING-920
> Project: Sling
>  Issue Type: Task
>  Components: Testing
>Reporter: Bertrand Delacretaz
>
> Use this issue to record changes to the Jenkins setup at 
> https://builds.apache.org/view/S-Z/view/Sling/



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (SLING-5291) Update existing and provide new Discovery features

[Oliver Lietz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-5291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz resolved SLING-5291.
-
Resolution: Fixed

[r1753068|https://svn.apache.org/r1753068]

> Update existing and provide new Discovery features
> --
>
> Key: SLING-5291
> URL: https://issues.apache.org/jira/browse/SLING-5291
> Project: Sling
>  Issue Type: Task
>  Components: Karaf
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Karaf Features 0.2.0, Karaf Integration Tests 0.2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-5248) Update Oak to 1.3.9

[Oliver Lietz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-5248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz updated SLING-5248:

Component/s: Oak
 Karaf

> Update Oak to 1.3.9
> ---
>
> Key: SLING-5248
> URL: https://issues.apache.org/jira/browse/SLING-5248
> Project: Sling
>  Issue Type: Task
>  Components: JCR, Karaf, Launchpad, Oak
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Karaf Features 0.2.0, JCR Oak Server 1.0.2, Launchpad 
> Builder 9
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-5132) remove Jackrabbit Server and Launchpad features and tests

[Oliver Lietz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-5132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz updated SLING-5132:

Component/s: (was: Launchpad)
 Karaf

> remove Jackrabbit Server and Launchpad features and tests
> -
>
> Key: SLING-5132
> URL: https://issues.apache.org/jira/browse/SLING-5132
> Project: Sling
>  Issue Type: Task
>  Components: Karaf
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Karaf 0.2.0, Karaf Features 0.2.0, Karaf Integration 
> Tests 0.2.0
>
>
> support Oak only



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-5247) Update Jackrabbit to 2.11.2

[Oliver Lietz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-5247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz updated SLING-5247:

Component/s: Karaf

> Update Jackrabbit to 2.11.2
> ---
>
> Key: SLING-5247
> URL: https://issues.apache.org/jira/browse/SLING-5247
> Project: Sling
>  Issue Type: Task
>  Components: JCR, Karaf, Launchpad
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Karaf Features 0.2.0, Launchpad Builder 9
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-5292) Provide Composum feature

[Oliver Lietz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-5292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz updated SLING-5292:

Component/s: (was: Launchpad)
 Karaf

> Provide Composum feature
> 
>
> Key: SLING-5292
> URL: https://issues.apache.org/jira/browse/SLING-5292
> Project: Sling
>  Issue Type: Task
>  Components: Karaf
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Karaf Features 0.2.0, Karaf Integration Tests 0.2.0
>
>
> {noformat}
>   
>   
> 
> mvn:com.composum.sling.core/composum-sling-core-commons/1.4.0-SNAPSHOT
> 
> mvn:com.composum.sling.core/composum-sling-core-console/1.4.0-SNAPSHOT
> 
> mvn:com.composum.sling.core/composum-sling-core-jslibs/1.4.0-SNAPSHOT
> 
> sling
> sling-jcr
> sling-scripting-jsp
>  dependency="true">mvn:org.apache.commons/commons-lang3/3.4
>   
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [VOTE] Release Apache Sling Launchpad Testing Services 2.0.10, Testing Services WAR 2.0.10, Apache Sling Integration Tests 1.0.2

[Bertrand Delacretaz]

Hi,

On Sun, Jul 24, 2016 at 11:04 AM, Oliver Lietz  wrote:
> ...additionally a release of org.apache.sling.launchpad.test-fragment is 
> required
> for ExportedPackagesTest...

Good catch! I'll release that as well.
-Bertrand

[jira] [Updated] (SLING-5291) Update existing and provide new Discovery features

[Oliver Lietz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-5291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz updated SLING-5291:

Component/s: (was: Launchpad)
 Karaf

> Update existing and provide new Discovery features
> --
>
> Key: SLING-5291
> URL: https://issues.apache.org/jira/browse/SLING-5291
> Project: Sling
>  Issue Type: Task
>  Components: Karaf
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Karaf Features 0.2.0, Karaf Integration Tests 0.2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-5307) Update Tika to 1.11

[Oliver Lietz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-5307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz updated SLING-5307:

Component/s: Launchpad
 Karaf

> Update Tika to 1.11
> ---
>
> Key: SLING-5307
> URL: https://issues.apache.org/jira/browse/SLING-5307
> Project: Sling
>  Issue Type: Task
>  Components: Karaf, Launchpad
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Karaf Features 0.2.0, Launchpad Builder 9
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-5360) Update Oak to 1.3.11

[Oliver Lietz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-5360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz updated SLING-5360:

Component/s: Oak

> Update Oak to 1.3.11
> 
>
> Key: SLING-5360
> URL: https://issues.apache.org/jira/browse/SLING-5360
> Project: Sling
>  Issue Type: Task
>  Components: Karaf, Launchpad, Oak
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Karaf Features 0.2.0, Launchpad Builder 9
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-5359) Update Jackrabbit to 2.11.3

[Oliver Lietz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-5359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz updated SLING-5359:

Component/s: Karaf

> Update Jackrabbit to 2.11.3
> ---
>
> Key: SLING-5359
> URL: https://issues.apache.org/jira/browse/SLING-5359
> Project: Sling
>  Issue Type: Task
>  Components: Karaf, Launchpad
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Karaf Features 0.2.0, Launchpad Builder 9
>
>
> new dependency {{com.google.guava/guava/15.0}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-5363) Provide Samples Fling feature

[Oliver Lietz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-5363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz updated SLING-5363:

Component/s: (was: Launchpad)
 Karaf

> Provide Samples Fling feature
> -
>
> Key: SLING-5363
> URL: https://issues.apache.org/jira/browse/SLING-5363
> Project: Sling
>  Issue Type: New Feature
>  Components: Karaf
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Karaf Features 0.2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-5360) Update Oak to 1.3.11

[Oliver Lietz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-5360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz updated SLING-5360:

Component/s: Karaf

> Update Oak to 1.3.11
> 
>
> Key: SLING-5360
> URL: https://issues.apache.org/jira/browse/SLING-5360
> Project: Sling
>  Issue Type: Task
>  Components: Karaf, Launchpad
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Karaf Features 0.2.0, Launchpad Builder 9
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-5308) Update Oak to 1.3.10

[Oliver Lietz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-5308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz updated SLING-5308:

Component/s: Launchpad
 Karaf

> Update Oak to 1.3.10
> 
>
> Key: SLING-5308
> URL: https://issues.apache.org/jira/browse/SLING-5308
> Project: Sling
>  Issue Type: Task
>  Components: Karaf, Launchpad, Oak
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Karaf Features 0.2.0, Launchpad Builder 9
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-5308) Update Oak to 1.3.10

[Oliver Lietz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-5308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz updated SLING-5308:

Component/s: Oak

> Update Oak to 1.3.10
> 
>
> Key: SLING-5308
> URL: https://issues.apache.org/jira/browse/SLING-5308
> Project: Sling
>  Issue Type: Task
>  Components: Karaf, Launchpad, Oak
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Karaf Features 0.2.0, Launchpad Builder 9
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-5562) Provide NoSQL features

[Oliver Lietz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-5562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz updated SLING-5562:

Component/s: (was: Launchpad)
 Karaf

> Provide NoSQL features
> --
>
> Key: SLING-5562
> URL: https://issues.apache.org/jira/browse/SLING-5562
> Project: Sling
>  Issue Type: New Feature
>  Components: Karaf
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Karaf Features 0.2.0, Karaf Integration Tests 0.2.0
>
>
> {{sling-nosql-generic}}
> {{sling-nosql-couchbase}}
> {{sling-nosql-mongodb}}
> {{sling-launchpad-nosql-couchbase}}
> {{sling-launchpad-nosql-mongodb}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-5572) Update Jackrabbit to 2.12.1

[Oliver Lietz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-5572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz updated SLING-5572:

Component/s: Karaf

> Update Jackrabbit to 2.12.1
> ---
>
> Key: SLING-5572
> URL: https://issues.apache.org/jira/browse/SLING-5572
> Project: Sling
>  Issue Type: Task
>  Components: JCR, Karaf, Launchpad, Testing
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: JCR Webdav 2.3.4, JCR DavEx 1.3.2, Karaf Features 0.2.0, 
> Karaf Integration Tests 0.2.0, Launchpad Builder 9, Commons Testing 2.0.26
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-5520) Update Oak to 1.4

[Oliver Lietz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-5520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz updated SLING-5520:

Component/s: Karaf

> Update Oak to 1.4
> -
>
> Key: SLING-5520
> URL: https://issues.apache.org/jira/browse/SLING-5520
> Project: Sling
>  Issue Type: Task
>  Components: JCR, Karaf, Launchpad, Oak
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Karaf Features 0.2.0, JCR Oak Server 1.0.2, Launchpad 
> Builder 9, JCR Oak Server 1.1.0
>
>
> Doing update in several more steps until Oak {{1.4}} is released due to major 
> changes, one of them being OAK-3842 (removed package exports, tracked in 
> SLING-5511).
> First updating to Oak {{1.3.14}} (latest pre OAK-3842 release) and then to 
> Oak {{1.3.15}}.
> Features deprecated for Oak {{1.4}} should be removed from 
> {{org.apache.sling.jcr.oak.server}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-5364) Provide Pipes feature

[Oliver Lietz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-5364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz updated SLING-5364:

Component/s: (was: Launchpad)
 Karaf

> Provide Pipes feature
> -
>
> Key: SLING-5364
> URL: https://issues.apache.org/jira/browse/SLING-5364
> Project: Sling
>  Issue Type: New Feature
>  Components: Karaf
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Karaf Features 0.2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-5376) Update Jackrabbit to 2.12.0

[Oliver Lietz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-5376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz updated SLING-5376:

Component/s: Karaf

> Update Jackrabbit to 2.12.0
> ---
>
> Key: SLING-5376
> URL: https://issues.apache.org/jira/browse/SLING-5376
> Project: Sling
>  Issue Type: Task
>  Components: JCR, Karaf, Launchpad, Testing
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: JCR Webdav 2.3.4, Karaf Features 0.2.0, Launchpad 
> Builder 9, Commons Testing 2.0.26
>
>
> new dependency {{com.google.guava/guava/15.0}} is required by 
> {{jackrabbit-jcr-commons}} indeed



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-5808) Update Tika to 1.13

[Oliver Lietz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-5808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz updated SLING-5808:

Component/s: Karaf

> Update Tika to 1.13
> ---
>
> Key: SLING-5808
> URL: https://issues.apache.org/jira/browse/SLING-5808
> Project: Sling
>  Issue Type: Task
>  Components: Karaf, Launchpad
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Karaf Features 0.2.0, Launchpad Builder 9
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-5685) Upgrade Commons IO to 2.5

[Oliver Lietz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-5685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz updated SLING-5685:

Component/s: Karaf

> Upgrade Commons IO to 2.5
> -
>
> Key: SLING-5685
> URL: https://issues.apache.org/jira/browse/SLING-5685
> Project: Sling
>  Issue Type: Task
>  Components: Karaf, Launchpad, Scripting
>Reporter: Oliver Lietz
> Fix For: File System ClassLoader 1.0.4, Karaf Features 0.2.0, 
> Scripting Thymeleaf 1.0.0, Health Check Core 1.2.6
>
> Attachments: commons-io.java.txt, commons-io.pom.txt
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-5624) Health Check Core 1.2.4 fails on Karaf

[Oliver Lietz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-5624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz updated SLING-5624:

Component/s: (was: Launchpad)
 Karaf

> Health Check Core 1.2.4 fails on Karaf
> --
>
> Key: SLING-5624
> URL: https://issues.apache.org/jira/browse/SLING-5624
> Project: Sling
>  Issue Type: Bug
>  Components: Karaf
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Karaf Features 0.2.0
>
>
> {{SlingExtensionHealthcheckIT}} fails with 
> {{org.apache.sling/org.apache.sling.hc.core/1.2.4}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)