[jira] [Resolved] (SLING-3646) Sling website CSS makes images too big
[ https://issues.apache.org/jira/browse/SLING-3646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz resolved SLING-3646. Resolution: Fixed Thanks very much, all looks good to me! Sling website CSS makes images too big -- Key: SLING-3646 URL: https://issues.apache.org/jira/browse/SLING-3646 Project: Sling Issue Type: Bug Components: Site Reporter: Bertrand Delacretaz Assignee: Dan Klco Priority: Minor Attachments: bertrand-chrome.jpg At http://markmail.org/message/kseatjzm2rcwxoj7 Dan Klco mentions incorrect zooming of images on the Sling site - I'm creating this issue so we can attach screenshots, as the behavior might be different on various browsers. I'll attach a bertrand-chrome.jpg screenshot which shows the results on my Chrome 35.0.1916.114 browser on macosx, displaying http://sling.apache.org/documentation/bundles/osgi-installer.html - the image does get very big but not over 100% width of its container in my case. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SLING-3651) Improve Conversion To Bundle and Content Projects
[ https://issues.apache.org/jira/browse/SLING-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14032180#comment-14032180 ] Konrad Windszus commented on SLING-3651: Yes, the changes are all included in the pull request. Would you consider integrating that in Version 1.0.0? Improve Conversion To Bundle and Content Projects - Key: SLING-3651 URL: https://issues.apache.org/jira/browse/SLING-3651 Project: Sling Issue Type: Bug Components: IDE Affects Versions: Sling Eclipse IDE 1.0.0 Reporter: Konrad Windszus Currently the Convert To Bundle Project is always enabled and I can even add the bundle facet to a maven project which is of packaging content-package The Convert To Content Project... is only enabled under very specific conditions. Currently those conditions are neither described in https://cwiki.apache.org/confluence/display/SLING/Sling+IDE+tooling+User+Guide nor is there some warning/trace messages available. I would suggest the following: Always enable both conversion actions. Display a warning message with a very descriptive warning in case the conversion cannot be performed. -- This message was sent by Atlassian JIRA (v6.2#6252)
Re: [featureflags] Readding sling:features to resourceResolver
Hi, I would second the idea of Mike to implement featureflags on the technological base of a ResourceAccessGate but hiding it away. From a pure execution perspective it does exactly what is required. Regarding Performance I think this handling can be implemented in a cheap way while achiving the same via ACLs (as it was done for a long time) is much more expensive. It would probably be an option to define pathpatterns that won't be checked at all, since content created at runtime would most certainly not contain feature flags but there might be cases where you would like to define certain areas that need to be checked anyways. As for filters there need to be patterns to skip a check as early and cheap as possible. Comming back to the CRUD operations I do not really get the problem here, the problems are exactly the same as existing for ACL protected resources. We do even have an advantage here since we can utilize service users for dedicated visibility for processing and check existance of a resource via services without the need of a separate admin session to gracefully handle conflicts. Could someone please describe the scenario where a featureflag would be problematic in therms of create update or delete? I assume that the existing patterns to deal with the corresponding issues in ACL protected scenarios could be adapted and used as well. We could even decide to provide more information about why that fails when we decide that feature flag control is not to be handled as strict as ACLs (since no security feature). Best regards Dominik On Fri, Jun 13, 2014 at 12:10 AM, Carsten Ziegeler cziege...@apache.org wrote: In general I see two problems, one is performance and the other one is how to deal with CRUD operations wrt to feature flags on a resource. The latter point was the main trigger to pull this off. I think we should go back to talk about use cases. The number one use case I know in this area is displaying/hiding a button in a navigation - this can really easily be done in the navigation component itself when rendering: the resource has a specific property which is checked. If it contains a feature name this is compared with the active feature and then either this item is included or not. We could suggest a common name for the property and we could also come up with a filter utility class, so for code doing this it will be a short one liner. I don't want to add a heavy unclear concept into the resource resolver just for such a use case. Regards Carsten 2014-06-12 2:55 GMT-04:00 Mike Müller mike...@mysign.ch: Hi Just my 2 cents to it: Why not defining a featureflag-interface which is internally implemented with ResourceAccessGates. Personally I think ResourceAccessGates could do the job but I can follow the fear, that such a mechanism mixing up with a security mechanism could lead to bad design. So the solution could really be to wrap the ResourceAccessGates for the functionality of featureflags. Best regards mike -Original Message- From: Dominik Süß [mailto:dominik.su...@gmail.com] Sent: Tuesday, June 10, 2014 2:53 PM To: dev Subject: [featureflags] Readding sling:features to resourceResolver Hi everyone, although I know this touches an area with a lot of emotions involved I wanted to reopen the discussion around Featureflags support for the resourceresolver. The last thing that happend was removing it for a release due to potential confusion and subtle issues. See http://markmail.org/thread/jgpso52iqiivpa5t Here are my arguments why I think it would be good to readd it to the resourceResolver (or any other mechanism being able to filter the resource tree: - Currently writing frontend that needs to adapt to featureflags requires adding custom code to check and filter the ui to be rendered. This leads to a lot of boilerplate code written over and over again with minor differences - Mechanisms relying on the Default Get Servlet JSON output would need to implement the filterlogic in clientside code. - ACL based solutions complicate the security setup for administrators because each feature would require a group (if toggling should be achived by membership instead of complex permissionrewriting) and could potentially impact performance of acl checks (not my domain so some specialists might be able to tell if those additional groups and memberships have impact on performance) The argument that developers might mistake feature flags with security is indicating that they don't read documentation (where potential security warnings should be written down in a prominent location) or do not care. But who does not care will not take care of proper ACLs anyways and assuming developers are using features without reading or respecting warnings in the documentation sounds a bit paranoid. I still think Resource Access Gate
[GitHub] sling pull request: SLING-3499, add injector-specific annotations
Github user kwin closed the pull request at: https://github.com/apache/sling/pull/13 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] sling pull request: SLING-3547, add test for numerical defaults (b...
Github user kwin closed the pull request at: https://github.com/apache/sling/pull/16 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (SLING-3499) Support custom annotations with Sling Models
[ https://issues.apache.org/jira/browse/SLING-3499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14032189#comment-14032189 ] ASF GitHub Bot commented on SLING-3499: --- Github user kwin closed the pull request at: https://github.com/apache/sling/pull/13 Support custom annotations with Sling Models Key: SLING-3499 URL: https://issues.apache.org/jira/browse/SLING-3499 Project: Sling Issue Type: New Feature Components: Extensions Affects Versions: Sling Models API 1.0.0, Sling Models Implementation 1.0.2 Reporter: Konrad Windszus Assignee: Justin Edelson Fix For: Sling Models Implementation 1.0.6 Attachments: SLING-3499-Documentation-v1.patch, SLING-3499-Documentation-v2.patch To support custom annotations the API needs to be extended. The reasons for custom annotations are listed in http://www.mail-archive.com/dev%40sling.apache.org/msg27918.html. Also it is much more comfortable for developers, since they can use code completion in the IDE to see which options are available for each injector-specific annotation, apart from that it is less code to write (instead of multiple annotations on one field/method I would only have to write one annotation with some attributes). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SLING-3547) Default handling for numerical types on Sling Models broken
[ https://issues.apache.org/jira/browse/SLING-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14032191#comment-14032191 ] ASF GitHub Bot commented on SLING-3547: --- Github user kwin closed the pull request at: https://github.com/apache/sling/pull/16 Default handling for numerical types on Sling Models broken --- Key: SLING-3547 URL: https://issues.apache.org/jira/browse/SLING-3547 Project: Sling Issue Type: Bug Components: Extensions Affects Versions: Sling Models Implementation 1.0.2, Sling Models Implementation 1.0.4 Reporter: Konrad Windszus Assignee: Justin Edelson Fix For: Sling Models Implementation 1.0.6 Currently all default annotations on numeric types lead to the following warning: org.apache.sling.models.impl.ModelAdapterFactory Default values for class java.lang.Boolean are not supported and the default is not used. This is due to the fact that first all types are converted from Primitives to Object Wrapper Classes (in mapPrimitiveClasses). Then the comparison against that type only considers Primitives (in getDefaultValue, except for Strings), which obviously failed, because either those were Object Wrapper Classes right from the beginning, or they were converted to those. In my regard you should compare the Type against e.g. Integer.class instead of Integer.TYPE (ModelAdapterFactory, line 428ff). Otherwise defaults for numerical types will not work. -- This message was sent by Atlassian JIRA (v6.2#6252)
Release of Sling Models
Hi everyone, what about a new release of Sling Models? Two issues were fixed (although https://issues.apache.org/jira/browse/SLING-3510 does not have the fix version set yet) and another improvement was made. No further open issues are reported. WDYT? Thanks, Konrad
Re: [featureflags] Readding sling:features to resourceResolver
Hi, On Fri, Jun 13, 2014 at 12:10 AM, Carsten Ziegeler cziege...@apache.org wrote: ...I think we should go back to talk about use cases I agree, and keeping the list at https://cwiki.apache.org/confluence/display/SLING/Sling+Feature+Flags+support up to date might be a good starting point. -Bertrand
Re: [featureflags] Readding sling:features to resourceResolver
Hi, On Tue, Jun 10, 2014 at 2:53 PM, Dominik Süß dominik.su...@gmail.com wrote: -... Currently writing frontend that needs to adapt to featureflags requires adding custom code to check and filter the ui to be rendered. This leads to a lot of boilerplate code written over and over again with minor differences... Can't that be solved by a utility library? Maybe with minimal changes to the Sling core, but without baking feature flags into the core. -Bertrand
Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Sample Integration Tests #556
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.testing.samples.integrationtests/556/
Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Resource-Based Discovery Service #556
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.discovery.impl/556/
Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Resource Access Security Integration Tests #556
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.resourceaccesssecurity.it/556/
Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Models Integration Tests #556
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.models.integration-tests/556/
Jenkins build is still unstable: sling-trunk-1.7 #556
See https://builds.apache.org/job/sling-trunk-1.7/changes
Jenkins build became unstable: sling-trunk-1.6 » Apache Sling Launchpad Base #2180
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.base/2180/
Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Sample Integration Tests #2180
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.testing.samples.integrationtests/2180/
Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Models Integration Tests #2180
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.models.integration-tests/2180/
Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Launchpad Testing #2180
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing/2180/
Jenkins build became unstable: sling-trunk-1.6 » Apache Sling Resource-Based Discovery Service #2180
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.discovery.impl/2180/
Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Resource Access Security Integration Tests #2180
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.resourceaccesssecurity.it/2180/
Jenkins build is still unstable: sling-trunk-1.6 #2180
See https://builds.apache.org/job/sling-trunk-1.6/changes
[jira] [Assigned] (SLING-3651) Improve Conversion To Bundle and Content Projects
[ https://issues.apache.org/jira/browse/SLING-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli reassigned SLING-3651: -- Assignee: Stefan Egli Improve Conversion To Bundle and Content Projects - Key: SLING-3651 URL: https://issues.apache.org/jira/browse/SLING-3651 Project: Sling Issue Type: Bug Components: IDE Affects Versions: Sling Eclipse IDE 1.0.0 Reporter: Konrad Windszus Assignee: Stefan Egli Currently the Convert To Bundle Project is always enabled and I can even add the bundle facet to a maven project which is of packaging content-package The Convert To Content Project... is only enabled under very specific conditions. Currently those conditions are neither described in https://cwiki.apache.org/confluence/display/SLING/Sling+IDE+tooling+User+Guide nor is there some warning/trace messages available. I would suggest the following: Always enable both conversion actions. Display a warning message with a very descriptive warning in case the conversion cannot be performed. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SLING-3651) Improve Conversion To Bundle and Content Projects
[ https://issues.apache.org/jira/browse/SLING-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14032245#comment-14032245 ] Stefan Egli commented on SLING-3651: Yes, I think this should go into 1.0.0. I'll look at it next. Improve Conversion To Bundle and Content Projects - Key: SLING-3651 URL: https://issues.apache.org/jira/browse/SLING-3651 Project: Sling Issue Type: Bug Components: IDE Affects Versions: Sling Eclipse IDE 1.0.0 Reporter: Konrad Windszus Assignee: Stefan Egli Currently the Convert To Bundle Project is always enabled and I can even add the bundle facet to a maven project which is of packaging content-package The Convert To Content Project... is only enabled under very specific conditions. Currently those conditions are neither described in https://cwiki.apache.org/confluence/display/SLING/Sling+IDE+tooling+User+Guide nor is there some warning/trace messages available. I would suggest the following: Always enable both conversion actions. Display a warning message with a very descriptive warning in case the conversion cannot be performed. -- This message was sent by Atlassian JIRA (v6.2#6252)
Re: [featureflags] Readding sling:features to resourceResolver
Hi Betrand, I fear it is not as easy since this mandates rendering engines to be able to perform that filtering (in other words - to be able to skip rendering based on the feature flag) or we would require developers to utilize filters which are way more intrusive then a Resource Access Gate and could potentially do much more harm. Additionally this code needs to be applied to each consumer. This might not be that much work if applying features in the first place, but just think of a solution like AEM where a huge codebase should be featurized (e.g. a part should be deactivable due to licencing or some other criteria): each and every part of the application depending on a contentstructure would need to learn this new concept instead of filtering the resourcetree in first place. If I got the idea of featureflags right they should be at least invasive in code as possible, keeping the risk low that a deactivated feature by accident influences the rest of the system at all. From a consumers perspective I would like to be able to declare resources to be part of a feature (whitelisting) and probably to be removed for a feature (blacklisting - although this requires a logic resolving potential theoretical conflicts with a whitelist) by adding attributes. This attribute check must be implemented in a cheap way (not much more then already done during resource resolution process). Best regards Dominik On Mon, Jun 16, 2014 at 9:58 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: Hi, On Tue, Jun 10, 2014 at 2:53 PM, Dominik Süß dominik.su...@gmail.com wrote: -... Currently writing frontend that needs to adapt to featureflags requires adding custom code to check and filter the ui to be rendered. This leads to a lot of boilerplate code written over and over again with minor differences... Can't that be solved by a utility library? Maybe with minimal changes to the Sling core, but without baking feature flags into the core. -Bertrand
[jira] [Created] (SLING-3671) Atom Taglib: tag attribute requirements to do not reflect standard's definition
Christoph Dahlen created SLING-3671:
---
Summary: Atom Taglib: tag attribute requirements to do not reflect
standard's definition
Key: SLING-3671
URL: https://issues.apache.org/jira/browse/SLING-3671
Project: Sling
Issue Type: Improvement
Components: Scripting
Affects Versions: Scripting JSP-Atom-Taglib 1.0.0
Reporter: Christoph Dahlen
The current
[TLD|http://svn.apache.org/repos/asf/sling/trunk/contrib/scripting/jsp-taglib-atom/src/main/resources/META-INF/atom.tld]
for the Atom taglib allows creating Atom Feeds that do not meet the standard's
requirements.
Most simple example:
{code:xml}
atom:feedatom:entry //atom:feed
{code}
will create the following output
{code:xml}
feed
xmlns=http://www.w3.org/2005/Atom;updated2014-06-16T12:39:03.382Z/updatedentry
//feed
{code}
This output fails to [validate|http://validator.w3.org/feed/] due to missing,
but mandatory elements id and title for _feed_ and _entry_ and missing
element updated for _entry_.
According to http://atomenabled.org/ the required elements for both
[feed|http://atomenabled.org/developers/syndication/#requiredFeedElements] and
[entry|developers/syndication/#requiredEntryElements] are:
* id
* title
* updated
Enforcing this requirements would require the following changes:
# make the id attribute required for _feed_ and _entry_ element
# either
## make the updated attribute required for _feed_ and _entry_ OR
## auto-compute the updated attribute for _entry_, as it is obviously done for
the _feed_ element
# replace the title element by a title attribute for _entry_ and _feed_ and
make it mandatory.
Comments on the feasibility are very welcome.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
Re: [featureflags] Readding sling:features to resourceResolver
Hi Dominik, On Mon, Jun 16, 2014 at 1:55 PM, Dominik Süß dominik.su...@gmail.com wrote: ...I fear it is not as easy since this mandates rendering engines to be able to perform that filtering (in other words - to be able to skip rendering based on the feature flag)... so IIUC you're looking at the alter resource rendering use case of [1] ? Note that even if the resource resolver hides rendering resources like scripts, I suspect you'll get in trouble as rendering scripts are cached. That's a good example of why I pushed for the SLING-3483 removal. ...This might not be that much work if applying features in the first place, but just think of a solution like AEM where a huge codebase should be featurized (e.g. a part should be deactivable due to licencing or some other criteria)... I sense a slightly more complex use case than [1] here...not sure if in-content feature flags are the right way to implement this. ... If I got the idea of featureflags right they should be at least invasive in code as possible, keeping the risk low that a deactivated feature by accident influences the rest of the system at all aka magic feature flags ;-) I agree that this looks nice, but as mentioned before I'm wary of multiple weird side effects like the caching thing mentioned above. We've seen those coming before SLING-3483, and so far no one has been able to reassure me that we're not opening a can of worms. ...From a consumers perspective I would like to be able to declare resources to be part of a feature (whitelisting) and probably to be removed for a feature (blacklisting - although this requires a logic resolving potential theoretical conflicts with a whitelist) by adding attributes... Assuming you want to work like this for scripts, how to you handle rendering servlets? -Bertrand [1] https://cwiki.apache.org/confluence/display/SLING/Sling+Feature+Flags+support P.S. no emotions about this on my side...I'm just not convinced so far, and wary of possible side effects. Best way to convince me is probably a prototype with sufficiently good tests that prove me wrong.
[event] JobManager.findJobs question
Hi all, while working with Sling replication I found a strange behavior, probably changed recently (as I didn't have it before), where calling: CollectionJob jobs = jobManager.findJobs(QueryType.QUEUED, topic, -1); returns me all the queued jobs, while calling: MapString,Object props = new HashMapString,Object(); CollectionJob jobs = jobManager.findJobs(QueryType.QUEUED, topic, -1, props); returns an empty collection. I don't think that's expected (a void template should work as no template given) and also it's a different behavior between 3.3.0 (my provided version) and 3.3.10 (my actual version). Am I missing something? Regards, Tommaso
Re: [featureflags] Readding sling:features to resourceResolver
Hi Bertrand, I'm not really about altering resource rendering but enable disable resources for rendering, so I probably wouldn't decorate the scripts and servlets but the resources that define those resourceTypes. This is what we all have done a lot when hiding away frontend for endusers (at least I know nobody who didn't have to do that once in a while) via ACLs wherever the UI was composed from resources. I get the case where you would like to alter the Script/Servlet that handles a resourceType but as you mentioned this comes with quite some constraints and locations that would require some changes to work. To get this working we would definitively need some script metadata which could also be added as annotation to be able to distinct on servletresolution. I do not like the term magic feature flags since it implies there would happen something out of control for a developert. Declarative feature flags is matching what I'm thinking of - declaring something being part of a feature and having a unified behavior of the system to handle these for the specific cases just as we have a declarative way of defining selectorbased filtering for scripts and/or servlets (declaration syntax is different but declaration and behavior of the system is always the same. IMHO we should go for the simplest mechanism first - which is the endresource being declared being part of a specific feature and carefully checking the lower level mechanisms for alter resource rendering. It still is better to have an easy and cheap solution that covers the easy cases but requires some engineering where more complex scenarios come into the game then forcing people to write custom code everywhere even for such common cases like disabling a Tab in a ui. Best regards Dominik On Mon, Jun 16, 2014 at 3:13 PM, Bertrand Delacretaz bdelacre...@apache.org wrote: Hi Dominik, On Mon, Jun 16, 2014 at 1:55 PM, Dominik Süß dominik.su...@gmail.com wrote: ...I fear it is not as easy since this mandates rendering engines to be able to perform that filtering (in other words - to be able to skip rendering based on the feature flag)... so IIUC you're looking at the alter resource rendering use case of [1] ? Note that even if the resource resolver hides rendering resources like scripts, I suspect you'll get in trouble as rendering scripts are cached. That's a good example of why I pushed for the SLING-3483 removal. ...This might not be that much work if applying features in the first place, but just think of a solution like AEM where a huge codebase should be featurized (e.g. a part should be deactivable due to licencing or some other criteria)... I sense a slightly more complex use case than [1] here...not sure if in-content feature flags are the right way to implement this. ... If I got the idea of featureflags right they should be at least invasive in code as possible, keeping the risk low that a deactivated feature by accident influences the rest of the system at all aka magic feature flags ;-) I agree that this looks nice, but as mentioned before I'm wary of multiple weird side effects like the caching thing mentioned above. We've seen those coming before SLING-3483, and so far no one has been able to reassure me that we're not opening a can of worms. ...From a consumers perspective I would like to be able to declare resources to be part of a feature (whitelisting) and probably to be removed for a feature (blacklisting - although this requires a logic resolving potential theoretical conflicts with a whitelist) by adding attributes... Assuming you want to work like this for scripts, how to you handle rendering servlets? -Bertrand [1] https://cwiki.apache.org/confluence/display/SLING/Sling+Feature+Flags+support P.S. no emotions about this on my side...I'm just not convinced so far, and wary of possible side effects. Best way to convince me is probably a prototype with sufficiently good tests that prove me wrong.
[jira] [Updated] (SLING-3672) Sling Jobs based queue looks always empty
[
https://issues.apache.org/jira/browse/SLING-3672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tommaso Teofili updated SLING-3672:
---
Description:
When using Sling Event 3.3.10 calling {code}MapString,Object props = new
HashMapString,Object();
CollectionJob jobs = jobManager.findJobs(QueryType.QUEUED, topic, -1,
props);{code} returns no jobs even if there are, therefore queues using Sling
Jobs always look empty as this code is used in ReplicationQueue#getHead.
was:
Calling {code}MapString,Object props = new HashMapString,Object();
CollectionJob jobs = jobManager.findJobs(QueryType.QUEUED, topic, -1,
props);{code} returns no jobs even if there are, therefore queues using Sling
Jobs always look empty as this code is used in ReplicationQueue#getHead.
Sling Jobs based queue looks always empty
-
Key: SLING-3672
URL: https://issues.apache.org/jira/browse/SLING-3672
Project: Sling
Issue Type: Bug
Components: Extensions
Reporter: Tommaso Teofili
Assignee: Tommaso Teofili
Labels: replication
When using Sling Event 3.3.10 calling {code}MapString,Object props = new
HashMapString,Object();
CollectionJob jobs = jobManager.findJobs(QueryType.QUEUED, topic, -1,
props);{code} returns no jobs even if there are, therefore queues using Sling
Jobs always look empty as this code is used in ReplicationQueue#getHead.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (SLING-3672) Sling Jobs based queue looks always empty
Tommaso Teofili created SLING-3672:
--
Summary: Sling Jobs based queue looks always empty
Key: SLING-3672
URL: https://issues.apache.org/jira/browse/SLING-3672
Project: Sling
Issue Type: Bug
Components: Extensions
Reporter: Tommaso Teofili
Assignee: Tommaso Teofili
Calling {code}MapString,Object props = new HashMapString,Object();
CollectionJob jobs = jobManager.findJobs(QueryType.QUEUED, topic, -1,
props);{code} returns no jobs even if there are, therefore queues using Sling
Jobs always look empty as this code is used in ReplicationQueue#getHead.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Resolved] (SLING-3672) Sling Jobs based queue looks always empty
[
https://issues.apache.org/jira/browse/SLING-3672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tommaso Teofili resolved SLING-3672.
Resolution: Fixed
Sling Jobs based queue looks always empty
-
Key: SLING-3672
URL: https://issues.apache.org/jira/browse/SLING-3672
Project: Sling
Issue Type: Bug
Components: Extensions
Reporter: Tommaso Teofili
Assignee: Tommaso Teofili
Labels: replication
When using Sling Event 3.3.10 calling {code}MapString,Object props = new
HashMapString,Object();
CollectionJob jobs = jobManager.findJobs(QueryType.QUEUED, topic, -1,
props);{code} returns no jobs even if there are, therefore queues using Sling
Jobs always look empty as this code is used in ReplicationQueue#getHead.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (SLING-3672) Sling Jobs based queue looks always empty
[
https://issues.apache.org/jira/browse/SLING-3672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14032489#comment-14032489
]
Tommaso Teofili commented on SLING-3672:
fixed in r1602882 by removing the empty template map.
Sling Jobs based queue looks always empty
-
Key: SLING-3672
URL: https://issues.apache.org/jira/browse/SLING-3672
Project: Sling
Issue Type: Bug
Components: Extensions
Reporter: Tommaso Teofili
Assignee: Tommaso Teofili
Labels: replication
When using Sling Event 3.3.10 calling {code}MapString,Object props = new
HashMapString,Object();
CollectionJob jobs = jobManager.findJobs(QueryType.QUEUED, topic, -1,
props);{code} returns no jobs even if there are, therefore queues using Sling
Jobs always look empty as this code is used in ReplicationQueue#getHead.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Sample Integration Tests #2181
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.testing.samples.integrationtests/2181/
Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Resource Access Security Integration Tests #2181
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.resourceaccesssecurity.it/2181/
Jenkins build is back to stable : sling-trunk-1.6 » Apache Sling Launchpad Base #2181
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.base/2181/
Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Launchpad Testing #2181
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing/2181/
Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Resource-Based Discovery Service #2181
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.discovery.impl/2181/
Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Models Integration Tests #2181
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.models.integration-tests/2181/
Jenkins build is still unstable: sling-trunk-1.6 #2181
See https://builds.apache.org/job/sling-trunk-1.6/changes
Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Resource Access Security Integration Tests #557
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.resourceaccesssecurity.it/557/
Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Sample Integration Tests #557
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.testing.samples.integrationtests/557/
Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Resource-Based Discovery Service #557
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.discovery.impl/557/
Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Launchpad Testing #557
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing/557/
Jenkins build became unstable: sling-trunk-1.7 » Apache Sling SLF4J Implementation (Logback) #557
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.commons.log/557/
Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Models Integration Tests #557
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.models.integration-tests/557/
Jenkins build is still unstable: sling-trunk-1.7 #557
See https://builds.apache.org/job/sling-trunk-1.7/changes
[jira] [Assigned] (SLING-3495) TopologyTest.testLargeTopologyWithHub failures on Jenkins
[ https://issues.apache.org/jira/browse/SLING-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli reassigned SLING-3495: -- Assignee: Stefan Egli TopologyTest.testLargeTopologyWithHub failures on Jenkins - Key: SLING-3495 URL: https://issues.apache.org/jira/browse/SLING-3495 Project: Sling Issue Type: Bug Components: Extensions Affects Versions: Discovery Impl 1.0.6 Reporter: Robert Munteanu Assignee: Stefan Egli Attachments: TopologyTest.testLargeTopologyWithHub-failure-sling-trunk-1.6.txt, TopologyTest.testLargeTopologyWithHub-failure-sling-trunk-1.7.txt TopologyTest.testLargeTopologyWithHub has failed in the last testing run for both sling-trunk-1.6 [1] and sling-trunk-1.7 [2] . The errors are attached, in case the build results will expire. [1]: https://builds.apache.org/view/S-Z/view/Sling/job/sling-trunk-1.6/lastBuild/org.apache.sling$org.apache.sling.discovery.impl/testReport/org.apache.sling.discovery.impl.topology/TopologyTest/testLargeTopologyWithHub/ [2]: https://builds.apache.org/view/S-Z/view/Sling/job/sling-trunk-1.7/lastBuild/org.apache.sling$org.apache.sling.discovery.impl/testReport/org.apache.sling.discovery.impl.topology/TopologyTest/testLargeTopologyWithHub/ -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SLING-3495) TopologyTest.testLargeTopologyWithHub failures on Jenkins
[ https://issues.apache.org/jira/browse/SLING-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14032560#comment-14032560 ] Stefan Egli commented on SLING-3495: using default timeout of 30s instead of 20s - plus using TimeoutProvider which allows to configure an additional factor - to adjust for slow machines, thanks [~bdelacretaz] for the pointer TopologyTest.testLargeTopologyWithHub failures on Jenkins - Key: SLING-3495 URL: https://issues.apache.org/jira/browse/SLING-3495 Project: Sling Issue Type: Bug Components: Extensions Affects Versions: Discovery Impl 1.0.6 Reporter: Robert Munteanu Assignee: Stefan Egli Attachments: TopologyTest.testLargeTopologyWithHub-failure-sling-trunk-1.6.txt, TopologyTest.testLargeTopologyWithHub-failure-sling-trunk-1.7.txt TopologyTest.testLargeTopologyWithHub has failed in the last testing run for both sling-trunk-1.6 [1] and sling-trunk-1.7 [2] . The errors are attached, in case the build results will expire. [1]: https://builds.apache.org/view/S-Z/view/Sling/job/sling-trunk-1.6/lastBuild/org.apache.sling$org.apache.sling.discovery.impl/testReport/org.apache.sling.discovery.impl.topology/TopologyTest/testLargeTopologyWithHub/ [2]: https://builds.apache.org/view/S-Z/view/Sling/job/sling-trunk-1.7/lastBuild/org.apache.sling$org.apache.sling.discovery.impl/testReport/org.apache.sling.discovery.impl.topology/TopologyTest/testLargeTopologyWithHub/ -- This message was sent by Atlassian JIRA (v6.2#6252)
Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Launchpad Testing #2182
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing/2182/
Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Models Integration Tests #2182
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.models.integration-tests/2182/
Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Sample Integration Tests #2182
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.testing.samples.integrationtests/2182/
Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Resource Access Security Integration Tests #2182
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.resourceaccesssecurity.it/2182/
Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Resource-Based Discovery Service #2182
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.discovery.impl/2182/
Jenkins build is still unstable: sling-trunk-1.6 #2182
See https://builds.apache.org/job/sling-trunk-1.6/changes
Jenkins build is back to stable : sling-trunk-1.7 » Apache Sling SLF4J Implementation (Logback) #558
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.commons.log/558/
Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Sample Integration Tests #558
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.testing.samples.integrationtests/558/
Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Resource-Based Discovery Service #558
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.discovery.impl/558/
Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Resource Access Security Integration Tests #558
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.resourceaccesssecurity.it/558/
Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Models Integration Tests #558
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.models.integration-tests/558/
Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Launchpad Testing #558
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing/558/
Jenkins build is still unstable: sling-trunk-1.7 #558
See https://builds.apache.org/job/sling-trunk-1.7/changes
Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Sample Integration Tests #559
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.testing.samples.integrationtests/559/
Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Resource Access Security Integration Tests #559
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.resourceaccesssecurity.it/559/
Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Models Integration Tests #559
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.models.integration-tests/559/
Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Resource-Based Discovery Service #559
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.discovery.impl/changes
Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Launchpad Testing #559
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing/559/
Jenkins build is still unstable: sling-trunk-1.7 #559
See https://builds.apache.org/job/sling-trunk-1.7/changes
Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Models Integration Tests #2183
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.models.integration-tests/2183/
Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Launchpad Testing #2183
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing/2183/
Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Resource-Based Discovery Service #2183
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.discovery.impl/changes
Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Sample Integration Tests #2183
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.testing.samples.integrationtests/2183/
Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Resource Access Security Integration Tests #2183
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.resourceaccesssecurity.it/2183/
Jenkins build is still unstable: sling-trunk-1.6 #2183
See https://builds.apache.org/job/sling-trunk-1.6/changes
Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Resource-Based Discovery Service #560
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.discovery.impl/changes
Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Resource Access Security Integration Tests #560
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.resourceaccesssecurity.it/560/
Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Launchpad Testing #560
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing/560/
Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Sample Integration Tests #560
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.testing.samples.integrationtests/560/
Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Models Integration Tests #560
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.models.integration-tests/560/
Jenkins build is still unstable: sling-trunk-1.7 #560
See https://builds.apache.org/job/sling-trunk-1.7/changes
[jira] [Resolved] (SLING-3510) Check for null classUrls and warn when no @Model classes found by Sling Models
[ https://issues.apache.org/jira/browse/SLING-3510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson resolved SLING-3510. --- Resolution: Fixed Fix Version/s: Sling Models Implementation 1.0.4 Check for null classUrls and warn when no @Model classes found by Sling Models -- Key: SLING-3510 URL: https://issues.apache.org/jira/browse/SLING-3510 Project: Sling Issue Type: Bug Components: Extensions Affects Versions: Sling Models Implementation 1.0.2 Reporter: Chris Pilsworth Fix For: Sling Models Implementation 1.0.4 When a non-existent package is added to Sling-Model-Packages, then an NPE is thrown as there are no matching classes found. I guess the same would happen for existing packages that contain no @Model classes. Check for classUrls and warn, then continue if null. -- This message was sent by Atlassian JIRA (v6.2#6252)
Re: Release of Sling Models
Hi Konrad, I'd like to get SLING-3516 into the next release. But if I don't have time to do that this week, I might go ahead and cut the next release anyway. Regards, Justin On Mon, Jun 16, 2014 at 3:38 AM, Konrad Windszus konra...@gmx.de wrote: Hi everyone, what about a new release of Sling Models? Two issues were fixed (although https://issues.apache.org/jira/browse/SLING-3510 does not have the fix version set yet) and another improvement was made. No further open issues are reported. WDYT? Thanks, Konrad
Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Models Integration Tests #2184
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.models.integration-tests/2184/
Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Resource Access Security Integration Tests #2184
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.resourceaccesssecurity.it/2184/
Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Sample Integration Tests #2184
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.testing.samples.integrationtests/2184/
Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Launchpad Testing #2184
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing/2184/
Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Resource-Based Discovery Service #2184
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.discovery.impl/changes
Jenkins build is still unstable: sling-trunk-1.6 #2184
See https://builds.apache.org/job/sling-trunk-1.6/changes
[jira] [Commented] (SLING-3661) ftp server should support resumable file uploads
[ https://issues.apache.org/jira/browse/SLING-3661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14032901#comment-14032901 ] Alexander Klimetschek commented on SLING-3661: -- There already is a chunked upload implementation for the sling POST servlet, it should reuse the same mechanism and (temporary) chunk content structure. SLING-2707 and SLING-3036 ftp server should support resumable file uploads Key: SLING-3661 URL: https://issues.apache.org/jira/browse/SLING-3661 Project: Sling Issue Type: Improvement Components: Extensions Reporter: Amrit Verma Attachments: resumeUploadDiff.txt The ftp server should support resuming file uploads. Steps: 1. Connect to ftp server and start file upload. 2. Terminate file upload in the middle. 3. Try resuming the upload. Issue: The server sends 551 error code. It only supports overwriting the existing file. -- This message was sent by Atlassian JIRA (v6.2#6252)
Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Sample Integration Tests #2185
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.testing.samples.integrationtests/2185/
Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Resource Access Security Integration Tests #2185
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.resourceaccesssecurity.it/2185/
Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Resource-Based Discovery Service #2185
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.discovery.impl/changes
Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Launchpad Testing #2185
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing/2185/
Jenkins build is still unstable: sling-trunk-1.6 #2185
See https://builds.apache.org/job/sling-trunk-1.6/changes
Jenkins build is back to stable : sling-trunk-1.7 » Apache Sling Resource-Based Discovery Service #561
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.discovery.impl/561/changes
Build failed in Jenkins: sling-contrib-1.6 » Apache Sling Replication Integration Tests #1148
See https://builds.apache.org/job/sling-contrib-1.6/org.apache.sling$org.apache.sling.replication.it/1148/ -- [INFO] [INFO] [INFO] Building Apache Sling Replication Integration Tests 0.0.1-SNAPSHOT [INFO] Downloading: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.testing.tools/1.0.7-SNAPSHOT/maven-metadata.xml [INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ org.apache.sling.replication.it --- [INFO] Deleting https://builds.apache.org/job/sling-contrib-1.6/org.apache.sling$org.apache.sling.replication.it/ws/target [INFO] Deleting https://builds.apache.org/job/sling-contrib-1.6/org.apache.sling$org.apache.sling.replication.it/ws/ (includes = [sling/**], excludes = []) [INFO] [INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-java) @ org.apache.sling.replication.it --- [INFO] [INFO] --- maven-antrun-plugin:1.7:run (set-bundle-required-execution-environment) @ org.apache.sling.replication.it --- [INFO] Executing tasks main: [INFO] Executed tasks [INFO] [INFO] --- maven-remote-resources-plugin:1.5:process (default) @ org.apache.sling.replication.it --- [INFO] [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ org.apache.sling.replication.it --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory https://builds.apache.org/job/sling-contrib-1.6/org.apache.sling$org.apache.sling.replication.it/ws/src/main/resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-antrun-plugin:1.7:run (check-memory-task) @ org.apache.sling.replication.it --- [INFO] Executing tasks main: [echo] WARNING (SLING-443/SLING-1782) ** [echo] On most platforms, you'll get OutOfMemoryErrors when building unless you set [echo] on 32bit platforms: MAVEN_OPTS=-Xmx256M -XX:MaxPermSize=256M, see SLING-443 [echo] on 64bit platforms: MAVEN_OPTS=-Xmx512M -XX:MaxPermSize=512M, see SLING-1782 [echo] ** [INFO] Executed tasks [INFO] [INFO] --- maven-dependency-plugin:2.8:copy-dependencies (copy-runnable-jar) @ org.apache.sling.replication.it --- [INFO] Copying org.apache.sling.launchpad-7-SNAPSHOT-standalone.jar to https://builds.apache.org/job/sling-contrib-1.6/org.apache.sling$org.apache.sling.replication.it/ws/target/dependency/org.apache.sling.launchpad-7-SNAPSHOT-standalone.jar [INFO] [INFO] --- maven-dependency-plugin:2.8:copy-dependencies (copy-additional-bundles) @ org.apache.sling.replication.it --- [INFO] Copying org.apache.sling.commons.json-2.0.6.jar to https://builds.apache.org/job/sling-contrib-1.6/org.apache.sling$org.apache.sling.replication.it/ws/target/sling/additional-bundles/org.apache.sling.commons.json-2.0.6.jar [INFO] Copying jackrabbit-jcr-commons-2.7.2.jar to https://builds.apache.org/job/sling-contrib-1.6/org.apache.sling$org.apache.sling.replication.it/ws/target/sling/additional-bundles/jackrabbit-jcr-commons-2.7.2.jar [INFO] Copying slf4j-api-1.5.11.jar to https://builds.apache.org/job/sling-contrib-1.6/org.apache.sling$org.apache.sling.replication.it/ws/target/sling/additional-bundles/slf4j-api-1.5.11.jar [INFO] Copying jackrabbit-api-2.7.2.jar to https://builds.apache.org/job/sling-contrib-1.6/org.apache.sling$org.apache.sling.replication.it/ws/target/sling/additional-bundles/jackrabbit-api-2.7.2.jar [INFO] Copying commons-io-2.4.jar to https://builds.apache.org/job/sling-contrib-1.6/org.apache.sling$org.apache.sling.replication.it/ws/target/sling/additional-bundles/commons-io-2.4.jar [INFO] Copying jcr-2.0.jar to https://builds.apache.org/job/sling-contrib-1.6/org.apache.sling$org.apache.sling.replication.it/ws/target/sling/additional-bundles/jcr-2.0.jar [INFO] Copying junit-4.8.2.jar to https://builds.apache.org/job/sling-contrib-1.6/org.apache.sling$org.apache.sling.replication.it/ws/target/sling/additional-bundles/junit-4.8.2.jar [INFO] Copying org.apache.sling.replication-0.0.1-SNAPSHOT.jar to https://builds.apache.org/job/sling-contrib-1.6/org.apache.sling$org.apache.sling.replication.it/ws/target/sling/additional-bundles/org.apache.sling.replication-0.0.1-SNAPSHOT.jar [INFO] Copying bndlib-1.50.0.jar to https://builds.apache.org/job/sling-contrib-1.6/org.apache.sling$org.apache.sling.replication.it/ws/target/sling/additional-bundles/bndlib-1.50.0.jar [INFO] Copying org.apache.felix.scr.annotations-1.9.8.jar to https://builds.apache.org/job/sling-contrib-1.6/org.apache.sling$org.apache.sling.replication.it/ws/target/sling/additional-bundles/org.apache.felix.scr.annotations-1.9.8.jar [INFO] Copying org.apache.sling.api-2.5.0.jar to
Build failed in Jenkins: sling-contrib-1.6 #1148
See https://builds.apache.org/job/sling-contrib-1.6/1148/changes Changes: [olli] SLING-3518 remove default name, don't use properties for label and description -- [...truncated 2932 lines...] [INFO] Copying jackrabbit-jcr-commons-2.7.2.jar to https://builds.apache.org/job/sling-contrib-1.6/ws/contrib-1.6/extensions/replication/it/target/sling/additional-bundles/jackrabbit-jcr-commons-2.7.2.jar [INFO] Copying slf4j-api-1.5.11.jar to https://builds.apache.org/job/sling-contrib-1.6/ws/contrib-1.6/extensions/replication/it/target/sling/additional-bundles/slf4j-api-1.5.11.jar [INFO] Copying jackrabbit-api-2.7.2.jar to https://builds.apache.org/job/sling-contrib-1.6/ws/contrib-1.6/extensions/replication/it/target/sling/additional-bundles/jackrabbit-api-2.7.2.jar [INFO] Copying commons-io-2.4.jar to https://builds.apache.org/job/sling-contrib-1.6/ws/contrib-1.6/extensions/replication/it/target/sling/additional-bundles/commons-io-2.4.jar [INFO] Copying jcr-2.0.jar to https://builds.apache.org/job/sling-contrib-1.6/ws/contrib-1.6/extensions/replication/it/target/sling/additional-bundles/jcr-2.0.jar [INFO] Copying junit-4.8.2.jar to https://builds.apache.org/job/sling-contrib-1.6/ws/contrib-1.6/extensions/replication/it/target/sling/additional-bundles/junit-4.8.2.jar [INFO] Copying org.apache.sling.replication-0.0.1-SNAPSHOT.jar to https://builds.apache.org/job/sling-contrib-1.6/ws/contrib-1.6/extensions/replication/it/target/sling/additional-bundles/org.apache.sling.replication-0.0.1-SNAPSHOT.jar [INFO] Copying bndlib-1.50.0.jar to https://builds.apache.org/job/sling-contrib-1.6/ws/contrib-1.6/extensions/replication/it/target/sling/additional-bundles/bndlib-1.50.0.jar [INFO] Copying org.apache.felix.scr.annotations-1.9.8.jar to https://builds.apache.org/job/sling-contrib-1.6/ws/contrib-1.6/extensions/replication/it/target/sling/additional-bundles/org.apache.felix.scr.annotations-1.9.8.jar [INFO] Copying org.apache.sling.api-2.5.0.jar to https://builds.apache.org/job/sling-contrib-1.6/ws/contrib-1.6/extensions/replication/it/target/sling/additional-bundles/org.apache.sling.api-2.5.0.jar [INFO] Copying org.apache.sling.commons.osgi-2.2.0.jar to https://builds.apache.org/job/sling-contrib-1.6/ws/contrib-1.6/extensions/replication/it/target/sling/additional-bundles/org.apache.sling.commons.osgi-2.2.0.jar [INFO] Copying org.apache.sling.hc.core-1.0.6.jar to https://builds.apache.org/job/sling-contrib-1.6/ws/contrib-1.6/extensions/replication/it/target/sling/additional-bundles/org.apache.sling.hc.core-1.0.6.jar [INFO] Copying slf4j-simple-1.5.11.jar to https://builds.apache.org/job/sling-contrib-1.6/ws/contrib-1.6/extensions/replication/it/target/sling/additional-bundles/slf4j-simple-1.5.11.jar [INFO] Copying org.apache.sling.testing.tools-1.0.7-SNAPSHOT.jar to https://builds.apache.org/job/sling-contrib-1.6/ws/contrib-1.6/extensions/replication/it/target/sling/additional-bundles/org.apache.sling.testing.tools-1.0.7-SNAPSHOT.jar [INFO] Copying httpclient-osgi-4.3.2.jar to https://builds.apache.org/job/sling-contrib-1.6/ws/contrib-1.6/extensions/replication/it/target/sling/additional-bundles/httpclient-osgi-4.3.2.jar [INFO] Copying org.apache.sling.launchpad-7-SNAPSHOT-standalone.jar to https://builds.apache.org/job/sling-contrib-1.6/ws/contrib-1.6/extensions/replication/it/target/sling/additional-bundles/org.apache.sling.launchpad-7-SNAPSHOT-standalone.jar [INFO] Copying servlet-api-2.4.jar to https://builds.apache.org/job/sling-contrib-1.6/ws/contrib-1.6/extensions/replication/it/target/sling/additional-bundles/servlet-api-2.4.jar [INFO] Copying org.apache.jackrabbit.vault-3.0.0.jar to https://builds.apache.org/job/sling-contrib-1.6/ws/contrib-1.6/extensions/replication/it/target/sling/additional-bundles/org.apache.jackrabbit.vault-3.0.0.jar [INFO] Copying httpcore-osgi-4.3.1.jar to https://builds.apache.org/job/sling-contrib-1.6/ws/contrib-1.6/extensions/replication/it/target/sling/additional-bundles/httpcore-osgi-4.3.1.jar [INFO] [INFO] --- build-helper-maven-plugin:1.8:reserve-network-port (reserve-server-port) @ org.apache.sling.replication.it --- [INFO] Reserved port 41198 for author.http.port [INFO] Reserved port 46192 for publish.http.port [INFO] [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ org.apache.sling.replication.it --- [INFO] No sources to compile [INFO] [INFO] --- maven-scr-plugin:1.16.0:scr (generate-scr-scrdescriptor) @ org.apache.sling.replication.it --- [WARNING] Source tree does not exist. Ignoring https://builds.apache.org/job/sling-contrib-1.6/ws/contrib-1.6/extensions/replication/it/src/main/java [WARNING] Source tree does not exist. Ignoring https://builds.apache.org/job/sling-contrib-1.6/ws/contrib-1.6/extensions/replication/it/src/main/java [WARNING] Source tree does not exist. Ignoring https://builds.apache.org/job/sling-contrib-1.6/ws/contrib-1.6/extensions/replication/it/src/main/java [INFO] [INFO]
Jenkins build is unstable: sling-trunk-1.7 » Apache Sling Models Integration Tests #562
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.models.integration-tests/562/
Jenkins build is unstable: sling-trunk-1.7 » Apache Sling Resource Access Security Integration Tests #562
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.resourceaccesssecurity.it/562/
Jenkins build is unstable: sling-trunk-1.7 » Apache Sling Sample Integration Tests #562
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.testing.samples.integrationtests/562/
