one (binding) vote is missing...
stefan
[
https://issues.apache.org/jira/browse/SLING-7200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu resolved SLING-7200.
Resolution: Fixed
Fixed in [r1812253|https://svn.apache.org/r1812253]
> Jenkins: stop
Robert Munteanu created SLING-7200:
--
Summary: Jenkins: stop rebuilding the launchpad on module update
Key: SLING-7200
URL: https://issues.apache.org/jira/browse/SLING-7200
Project: Sling
Yes, branching could be an option. To avoid confusion, it may be
prudent to do any releases from such branches only with odd bundle
micro-versions and a qualifier. Such a version number could e.g. look
like this: 1.4.7-EXPERIMENTAL.
That way a released artifact is clearly labelled as being
Github user asfgit closed the pull request at:
https://github.com/apache/sling/pull/255
---
GitHub user cschneider opened a pull request:
https://github.com/apache/sling/pull/255
Update from old snapshot to current release to fix build
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/cschneider/sling
[
https://issues.apache.org/jira/browse/SLING-7185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16205783#comment-16205783
]
Stefan Seifert commented on SLING-7185:
---
it would definitely make sense to support other (and more
Hi Ian
The only bundle with a direct dependency to Oak is Sling JCR Resource.
All other bundles you mention require an updated Sling API (for
ExternalizableInputStream), which should be no problem.
In detail:
- Sling API defines ExternalizableInputStream
- Sling JCR Resource implements
Hi,
I think it would be better to go back and look at the earlier proposals for
this patch that did not require any new APIs from Oak to work. They were
written that way to avoid exactly the problem of a long dependency chain
now blocking the feature.
Since Oak only releases its first stable
[
https://issues.apache.org/jira/browse/SLING-7201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu resolved SLING-7201.
-
Resolution: Fixed
Fixed in [r1812299|https://svn.apache.org/r1812299].
Tests enabled through
Hi all,
this is my first mail to the list. I just started at Adobe in October and
will be working on the AEM platform.
Before I worked at Talend for more than 6 years as Open Source Architect
and was mainly active in the projects Karaf, Aries, CXF and Camel.
So currently I am making myself
[
https://issues.apache.org/jira/browse/SLING-7185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16206179#comment-16206179
]
Jason E Bailey commented on SLING-7185:
---
So is your thinking a configurable formatting or a cascade?
Hi,
My first proposal used javax.net.URI. It could do that again. No Oak API
required.
Best Regards
Ian
On 16 October 2017 at 14:34, Julian Sedding wrote:
> Hi Ian
>
> The only bundle with a direct dependency to Oak is Sling JCR Resource.
> All other bundles you mention
Hi Christian,
Is the performance test failure consistent on your machine? I cannot
reproduce it on my Mid 2015 MacBook Pro and the test has also been pretty
stable on Jenkins [1].
Cheers,
Radu
[1] -
Hi Christian and welcome!
On Mon, Oct 16, 2017 at 5:00 PM, Christian Schneider
wrote:
> ...Currently the build works until the Scripting HTL Integration Tests. There
> I get a failure at one of the performance tests "test3SlyJavaPojoRepo". The
> expected performance
Hi Bertrand,
I can confirm it is exactly this module and the "test3SlyJavaPojoRepo"
fails all the time for me. All other tests in this module work fine for me.
After setting the value to 2.5 I got the build passing but of course I am
not sure if this is a good value to actually test for
Radu was able to help me with the problem. It seems I still had the on
access virus scanner active on my build directory .. that of course pulled
the performance down badly.
I will try to document what I learned either in the test module or on the
documentation about building sling.
Christian
[
https://issues.apache.org/jira/browse/SLING-7201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu updated SLING-7201:
Description:
It seems that the changes added in SLING-6737 made the
Yes. It is persistent. Do I maybe need to tune any settings for the build?
Christian
2017-10-16 17:11 GMT+02:00 Radu Cotescu :
> Hi Christian,
>
> Is the performance test failure consistent on your machine? I cannot
> reproduce it on my Mid 2015 MacBook Pro and the test has
[
https://issues.apache.org/jira/browse/SLING-7185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16206244#comment-16206244
]
Stefan Seifert commented on SLING-7185:
---
in minor problem is of course that in case of JSON parsing
[
https://issues.apache.org/jira/browse/SLING-7185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16206243#comment-16206243
]
Stefan Seifert commented on SLING-7185:
---
cascade should be fine, and perhaps try ISO-8601 first and
Radu Cotescu created SLING-7201:
---
Summary: ScriptCache implementation doesn't correctly flush stale
entries
Key: SLING-7201
URL: https://issues.apache.org/jira/browse/SLING-7201
Project: Sling
[
https://issues.apache.org/jira/browse/SLING-7185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16206504#comment-16206504
]
Jason E Bailey commented on SLING-7185:
---
Would it be a problem to update the Content Parser to
[
https://issues.apache.org/jira/browse/SLING-7185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16206548#comment-16206548
]
Stefan Seifert commented on SLING-7185:
---
i would prefer still supporting Java 7.
jackrabbit has a
24 matches
Mail list logo