[jira] [Resolved] (SLING-3730) ResourceResolver does not always set the metadata sling.resolutionPath properly
[ https://issues.apache.org/jira/browse/SLING-3730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-3730. - Resolution: Fixed ResourceResolver does not always set the metadata sling.resolutionPath properly - Key: SLING-3730 URL: https://issues.apache.org/jira/browse/SLING-3730 Project: Sling Issue Type: Bug Affects Versions: JCR Resource 2.3.6, Resource Resolver 1.1.0 Reporter: Konrad Windszus Assignee: Carsten Ziegeler Priority: Critical Fix For: JCR Resource 2.3.8, Resource Resolver 1.1.2 Attachments: rewriter-issue-1.0.zip This metadata is evaluated by calling: SlingHttpServletRequest.getRequestPathInfo().getResourcePath() (you can see how this field is initially set in org.apache.sling.engine.impl.request.SlingRequestPathInfo, line 59). This is e.g. the case in org.apache.sling.rewriter.impl.ProcessorConfigurationImpl.match(ProcessorConfigurationImpl.java:411). If it returns null like it does for MergedResources (due to that metadata not being set) that leads easily to NPEs like in the example with the SlingRewriter. According to the Javadocs of RequestPathInfo (https://github.com/apache/sling/blob/trunk/bundles/api/src/main/java/org/apache/sling/api/request/RequestPathInfo.java) I would assume that getResourcePath() never returns null. For all the other methods it is explicitly stated if they are expected to return null in some cases. All the other Resources like SyntheticResource or JcrItemResource already set that metadata in their constructor. -- This message was sent by Atlassian JIRA (v6.2#6252)
Jenkins build is back to stable : sling-trunk-1.7 » Apache Sling Sample Integration Tests #684
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.testing.samples.integrationtests/684/
Jenkins build is still unstable: sling-trunk-1.7 #684
See https://builds.apache.org/job/sling-trunk-1.7/changes
[RESULT] [VOTE] Release Apache Sling Test Tools 1.0.8
Hi, The vote has passed with the following result: +1 (binding) : Robert Munteanu, Bertrand Delacretaz, Daniel Klco, Carsten Ziegeler +1 (non-binding) : Davide Giannella I'll take care of the remaining steps Cheers, Stefan
Jenkins build became unstable: sling-trunk-1.6 » Apache Sling Pax Exam Utilities #2310
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.paxexam.util/2310/
Jenkins build became unstable: sling-trunk-1.6 » Apache Sling Models Integration Tests #2310
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.models.integration-tests/2310/
Jenkins build is still unstable: sling-trunk-1.6 #2310
See https://builds.apache.org/job/sling-trunk-1.6/changes
Re: Launchpad 7 Release?
Hi, On Tue, Jul 22, 2014 at 7:59 AM, Carsten Ziegeler cziege...@apache.org wrote: ...Basically I see two options: a) we simply release all snapshot bundles now as is and get the launchpad out of the door b) we reduce the list... The launchpad has conflicting requirements IMO 1) Run integration tests for all relevant bundles (the test launchpad) 2) Provide a good starting point to experiment with Sling (the user launchpad) For 2) we can reduce the set of bundles and cannot use any snapshots, but IMO for 1) we need to use snapshots, and test as many bundles as possible. So maybe we need two launchpad variants? Testing both would be difficult though, as newer tests often require the latest snapshots. -Bertrand
obr/sling.xml
Hi, I just tried to follow the release process steps and noticed when updating the obr/sling.xml, that it hasn't been done so for quite a while (2.5 years). So I'm not sure what the idea with this is, but I guess we should update it. Also, when trying to do a 'svn up' on people.apache.org, I got the following: stefanegli@minotaur:/x1/www/sling.apache.org/content/obr$ svn up svn: E155004: Working copy '/x1/www/sling.apache.org/content' locked svn: E200031: sqlite: attempt to write a readonly database svn: E200031: sqlite: attempt to write a readonly database svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details) I'm uncertain if doing a 'svn cleanup' there does not have any side-effects.. :S Anyone familiar with the setup there? Cheers, Stefan
Re: obr/sling.xml
Hi Stefan, On Tue, Jul 22, 2014 at 10:47 AM, Stefan Egli stefane...@apache.org wrote: ...I just tried to follow the release process steps and noticed when updating the obr/sling.xml, that it hasn't been done so for quite a while (2.5 years)... This seems to prove that nobody is using that feature - we might as well drop the file to make that clear? Also, when trying to do a 'svn up' on people.apache.org, I got the following: ... svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details) ... That only touches your local sandbox - if you check with svn stat / svn diff what you are about to commit you can see exactly what will happen. -Bertrand
[RESULT][VOTE] accept the SLING-3667 Sling Query contribution
On Thu, Jul 17, 2014 at 2:32 PM, Bertrand Delacretaz bdelacre...@apache.org wrote: ...See SLING-3667 for details - please vote to accept this contribution... The vote passes with binding +1s from Robert Muntenau, Carsten Ziegeler, Justin Edelson and myself, non-binding +1s from Gabriel Walt and Tommaso Teofili and no other votes. Thanks - I'll proceed with the IP clearance and update SLING-3667 -Bertrand
[jira] [Commented] (SLING-3776) JsonRendererServlet should provide a way to list children as an array
[
https://issues.apache.org/jira/browse/SLING-3776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14070079#comment-14070079
]
Bertrand Delacretaz commented on SLING-3776:
Thanks for the added tests at https://github.com/apache/sling/pull/23
The more I look at this the more I think it belongs to JSONObject - we already
have JSON formatting code scattered around, we shouldn't make that worse.
Instead of having the formatting code in JsonRendererServlet I suggest adding
something like this to JSONObject, with some tests in that module:
{code}
// a new class
public class JSONStringOptions {
final int perLevelIndent;
final int initialIndent;
boolean useArraysForChildObjects:
//...with a suitable constructor...
}
public class JSONObject {
...
public String toString(JSONStringOptions opt) {
// ...dispatch to the existing formatting methods +
// the new one with harray support
}
}
{code}
WDYT?
JsonRendererServlet should provide a way to list children as an array
-
Key: SLING-3776
URL: https://issues.apache.org/jira/browse/SLING-3776
Project: Sling
Issue Type: Improvement
Components: Servlets
Affects Versions: Servlets Get 2.1.8
Reporter: Damien Antipa
The default JSON renderer prints all children of a node as another key-value
attribute. But browsers do not respect the order printed in the response of
object attributes (since the standard does not describe this).
In a lot of cases I continue writing my own servlets to print the children as
a json array which respects the order. Imo the default renderer should
provide a selector to change the output and print children in an array.
PR: https://github.com/apache/sling/pull/23
--
This message was sent by Atlassian JIRA
(v6.2#6252)
Build failed in Jenkins: sling-trunk-1.6 » Apache Sling Scripting JavaScript Support #2311
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.scripting.javascript/2311/ -- [INFO] [INFO] [INFO] Building Apache Sling Scripting JavaScript Support 2.0.15-SNAPSHOT [INFO] Downloading: http://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.scripting.api/2.0.2-incubator/org.apache.sling.scripting.api-2.0.2-incubator.pom Downloading: http://repo.maven.apache.org/maven2/org/mozilla/rhino/1.7R4/rhino-1.7R4.pom Downloading: http://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.commons.testing/2.0.4-incubator/org.apache.sling.commons.testing-2.0.4-incubator.pom [JENKINS] Archiving disabled
Build failed in Jenkins: sling-trunk-1.6 #2311
See https://builds.apache.org/job/sling-trunk-1.6/2311/changes Changes: [stefanegli] SLING-3775 : relaxed check for valid child node types: if there is any childNodeDef which has no name property set, then this allows any name -- [...truncated 13697 lines...] [INFO] Sling Bundle Archetype SUCCESS [8.680s] [INFO] Sling JCRInstall Bundle Archetype . SUCCESS [8.341s] [INFO] Sling Taglib Archetype SUCCESS [5.680s] [INFO] Apache Sling API .. SUCCESS [27.111s] [INFO] Apache Sling Resource Resolver SUCCESS [18.020s] [INFO] Apache Sling System Bundle Extension: Java Transaction API SUCCESS [5.870s] [INFO] Apache Sling System Bundle Extension: XML APIs SUCCESS [3.370s] [INFO] Apache Sling System Bundle Extension: Activation API SUCCESS [5.117s] [INFO] Apache Sling System Bundle Extension: WS APIs . SUCCESS [3.604s] [INFO] Apache Sling Dynamic Class Loader Support . SUCCESS [27.627s] [INFO] Apache Sling Commons Java Compiler SUCCESS [19.065s] [INFO] Apache Sling JSON Library . SUCCESS [8.412s] [INFO] Apache Sling SLF4J Implementation (Logback) ... SUCCESS [39.191s] [INFO] Apache Sling OSGi LogService Implementation ... SUCCESS [5.712s] [INFO] Apache Sling MIME type mapping support SUCCESS [9.432s] [INFO] Apache Sling Commons OSGi support . SUCCESS [6.235s] [INFO] Apache Sling Scheduler Support SUCCESS [6.440s] [INFO] Apache Sling Testing Utilities SUCCESS [18.737s] [INFO] Apache Sling Thread Dumper SUCCESS [6.312s] [INFO] Apache Sling Thread Support ... SUCCESS [5.356s] [INFO] Apache Sling Authentication Service ... SUCCESS [14.357s] [INFO] Apache Sling OpenID Authentication SUCCESS [9.155s] [INFO] Apache Sling Form Based Authentication Handler SUCCESS [13.070s] [INFO] Apache Sling Authentication Selector .. SUCCESS [15.558s] [INFO] Apache Sling Engine Implementation SUCCESS [18.510s] [INFO] Apache Sling Repository API Bundle SUCCESS [5.709s] [INFO] Apache Sling JCR Base Bundle .. SUCCESS [6.868s] [INFO] Apache Sling JCR ClassLoader .. SUCCESS [5.971s] [INFO] Apache Sling Initial Content Loader ... SUCCESS [11.249s] [INFO] Apache Sling Jackrabbit Embedded Repository ... SUCCESS [9.251s] [INFO] Apache Sling Jackrabbit UserManager Support ... SUCCESS [11.580s] [INFO] Apache Sling Jackrabbit JSR-283 Access Control Manager Support SUCCESS [6.941s] [INFO] Apache Sling Wrapper Bundle for the JCR API ... SUCCESS [3.464s] [INFO] Apache Sling Object Content Mapping ... SUCCESS [8.415s] [INFO] Apache Sling JCR Resource Resolver SUCCESS [38.866s] [INFO] Apache Sling JCR Repository Registration .. SUCCESS [6.936s] [INFO] Apache Sling Simple WebDAV Access to repositories . SUCCESS [11.998s] [INFO] Apache Sling DavEx Access to repositories . SUCCESS [8.885s] [INFO] Apache Sling JCR WebConsole Bundle SUCCESS [6.308s] [INFO] Apache Sling Oak Repository Server SUCCESS [8.233s] [INFO] Apache Sling SlingRepository Integration Tests SUCCESS [26.809s] [INFO] Apache Sling Servlet Resolver . SUCCESS [8.323s] [INFO] Apache Sling Default GET Servlets . SUCCESS [8.314s] [INFO] Apache Sling Default POST Servlets SUCCESS [8.461s] [INFO] Apache Sling Compat Servlets .. SUCCESS [5.906s] [INFO] Apache Sling Scripting Implementation API . SUCCESS [3.743s] [INFO] Apache Sling Scripting Core implementation SUCCESS [14.453s] [INFO] Apache Sling Scripting JavaScript Support . FAILURE [33.576s] [INFO] Apache Sling Scripting JSP Support SKIPPED [INFO] Apache Sling JSP Tag Library .. SKIPPED [INFO] Apache Sling JSP Standard Tag Library . SKIPPED [INFO] Apache Sling Adapter Manager Implementation ... SKIPPED [INFO] Apache Sling Bundle Resource Provider . SKIPPED [INFO] Apache Sling Discovery API SKIPPED [INFO] Apache Sling Resource-Based Discovery Service . SKIPPED [INFO] Apache Sling Discovery Support Bundle . SKIPPED [INFO] Apache Sling Discovery Standalone Implementation .. SKIPPED [INFO] Apache Sling Event Support SKIPPED [INFO] Apache Sling Feature Flags SKIPPED [INFO] Apache Sling Filesystem Resource Provider . SKIPPED [INFO] Apache Sling javax.activation bundle .. SKIPPED [INFO] Apache Sling Service User Mapper .. SKIPPED [INFO] Apache Sling Settings . SKIPPED
Re: Launchpad 7 Release?
On Tuesday 22 July 2014 07:59:22 Carsten Ziegeler wrote: Hi, hello, a new launchpad release is long time overdue. I think one of the problems is that we include so many different bundles that there is always a couple of them which need just a little bit of work to be released. And once those are done, the next bundles are on that list. the problem I see is that the list from launchpad is used for development and we don't maintain a stable list with non-SNAPSHOT bundles. Basically I see two options: a) we simply release all snapshot bundles now as is and get the launchpad out of the door I haven't checked the SNAPSHOT bundles, but I think there are some bundles where nothing changed after their latest release so we may use some already released bundles and not release *all* now. b) we reduce the list Can we split the list (into features) like I've done for Karaf? I think we should try to do something in between :) Reducing the list and then simply releasing everything. As a first step I think we shouldn't support two repository implementations. Oak is now mature and can be used in production, so why not just include Oak? This would already remove several bundles. I'm fine with just supporting Oak in 7 but I think there is some work left to be on par with Jackrabbit 2. If we stick to Jackrabbit 2 for 7 we should downgrade to 2.6 or upgrade to 2.8 as 2.7 is an unstable branch, no? Then there are things like OCM which we don't really support - so why ship it? Because people ask for it. Same for other bundles like Freemarker and Groovy templating. If we don't support bundles we should clearly state it and move them to contrib. And I guess there is more A roadmap (wiki page?) with milestones for (a) next release(s) would really be helpful as one can spend spare cycles to work on more important tasks - e.g. using Service User Mapping in JCR Server et al. Also we should use a common set of bundles in our (integration) tests to verify that everything is working with the bundle list from launchpad. My goals for a first *Karaf* Launchpad release are a current released JCR Server (whether Jackrabbit or Oak) and getting the Event bundle fixed (not sure what's the cause for a failing IT yet). Regards, O. WDYT Regards Carsten
Build failed in Jenkins: sling-trunk-1.7 » Apache Sling Discovery Support Bundle #685
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.discovery.support/685/ -- [INFO] [INFO] [INFO] Building Apache Sling Discovery Support Bundle 1.0.1-SNAPSHOT [INFO] Downloading: http://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.settings/1.3.0/org.apache.sling.settings-1.3.0.pom [JENKINS] Archiving disabled
Jenkins build became unstable: sling-trunk-1.7 » Apache Sling Dynamic Class Loader Support #685
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.commons.classloader/685/
Jenkins build became unstable: sling-trunk-1.7 » Apache Sling SlingRepository Integration Tests #685
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.jcr.repository.it-jackrabbit-oak/685/
[jira] [Resolved] (SLING-3778) [tooling] multi valued properties are not correctly exported to the server
[
https://issues.apache.org/jira/browse/SLING-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu resolved SLING-3778.
Resolution: Fixed
[tooling] multi valued properties are not correctly exported to the server
--
Key: SLING-3778
URL: https://issues.apache.org/jira/browse/SLING-3778
Project: Sling
Issue Type: Bug
Components: IDE
Reporter: Stefan Egli
Assignee: Robert Munteanu
Fix For: Sling Eclipse IDE 1.0.2
Consider the following .content.xml:
{code}
?xml version=1.0 encoding=UTF-8?
jcr:root
xmlns:sling=http://sling.apache.org/jcr/sling/1.0;
xmlns:jcr=http://www.jcp.org/jcr/1.0;
jcr:primaryType=sling:Folder
multi=[first]/
{code}
This content is not correctly exported to the server - the property ends up
as a non-mvp.
A subsequent change of the properties an array with 2 entries results in :
{code}
[July 21, 2014 9:28:44 PM CEST] AddOrUpdateNodeCommand -
/apps/beispielapp/foo : JcrResult[ success:false, exception:
org.apache.sling.ide.transport.RepositoryException -
javax.jcr.ValueFormatException: /apps/beispielapp/foo/multiMultivalue
definition of /apps/beispielapp/foo/multi does not match to given value(s).]
(92 ms)
org.apache.sling.ide.transport.RepositoryException:
javax.jcr.ValueFormatException: /apps/beispielapp/foo/multiMultivalue
definition of /apps/beispielapp/foo/multi does not match to given value(s).
at org.apache.sling.ide.impl.vlt.JcrResult.failure(JcrResult.java:33)
at org.apache.sling.ide.impl.vlt.JcrCommand.execute(JcrCommand.java:65)
at
org.apache.sling.ide.transport.TracingCommand.execute(TracingCommand.java:43)
at
org.apache.sling.ide.eclipse.core.internal.SlingLaunchpadBehaviour.execute(SlingLaunchpadBehaviour.java:455)
at
org.apache.sling.ide.eclipse.core.internal.SlingLaunchpadBehaviour.publishContentModule(SlingLaunchpadBehaviour.java:415)
at
org.apache.sling.ide.eclipse.core.internal.SlingLaunchpadBehaviour.publishModule(SlingLaunchpadBehaviour.java:231)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:1091)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:1183)
at
org.apache.sling.ide.eclipse.core.internal.ServerBehaviourDelegateWithModulePublishSupport.publish(ServerBehaviourDelegateWithModulePublishSupport.java:137)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774)
at
org.apache.sling.ide.eclipse.core.internal.ServerBehaviourDelegateWithModulePublishSupport.publish(ServerBehaviourDelegateWithModulePublishSupport.java:54)
at
org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3154)
at
org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
Caused by: javax.jcr.ValueFormatException:
/apps/beispielapp/foo/multiMultivalue definition of
/apps/beispielapp/foo/multi does not match to given value(s).
at
org.apache.jackrabbit.jcr2spi.PropertyImpl.checkIsWritable(PropertyImpl.java:511)
at
org.apache.jackrabbit.jcr2spi.PropertyImpl.setValue(PropertyImpl.java:117)
at org.apache.jackrabbit.jcr2spi.NodeImpl.setProperty(NodeImpl.java:283)
at org.apache.jackrabbit.jcr2spi.NodeImpl.setProperty(NodeImpl.java:269)
at
org.apache.sling.ide.impl.vlt.AddOrUpdateNodeCommand.updateNode(AddOrUpdateNodeCommand.java:304)
at
org.apache.sling.ide.impl.vlt.AddOrUpdateNodeCommand.update(AddOrUpdateNodeCommand.java:99)
at
org.apache.sling.ide.impl.vlt.AddOrUpdateNodeCommand.execute0(AddOrUpdateNodeCommand.java:80)
at
org.apache.sling.ide.impl.vlt.AddOrUpdateNodeCommand.execute0(AddOrUpdateNodeCommand.java:1)
at org.apache.sling.ide.impl.vlt.JcrCommand.execute(JcrCommand.java:57)
... 12 more
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (SLING-3779) Export Wizard does not report all errors
[ https://issues.apache.org/jira/browse/SLING-3779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14070184#comment-14070184 ] Robert Munteanu commented on SLING-3779: Fixed in http://svn.apache.org/viewvc?view=revisionrevision=r1612554 Export Wizard does not report all errors Key: SLING-3779 URL: https://issues.apache.org/jira/browse/SLING-3779 Project: Sling Issue Type: Bug Components: IDE Affects Versions: Sling Eclipse IDE 1.0.0 Reporter: Robert Munteanu Assignee: Robert Munteanu Fix For: Sling Eclipse IDE 1.0.2 The export wizard does not report errors from runtime exceptions and pressing 'Finish' leads to a confusing state - the wizard is not closed but no error message is displayed. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (SLING-3779) Export Wizard does not report all errors
[ https://issues.apache.org/jira/browse/SLING-3779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-3779. Resolution: Fixed Export Wizard does not report all errors Key: SLING-3779 URL: https://issues.apache.org/jira/browse/SLING-3779 Project: Sling Issue Type: Bug Components: IDE Affects Versions: Sling Eclipse IDE 1.0.0 Reporter: Robert Munteanu Assignee: Robert Munteanu Fix For: Sling Eclipse IDE 1.0.2 The export wizard does not report errors from runtime exceptions and pressing 'Finish' leads to a confusing state - the wizard is not closed but no error message is displayed. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (SLING-3780) Enrich the ResourceProxy model to hold more information about the property metadata
Robert Munteanu created SLING-3780:
--
Summary: Enrich the ResourceProxy model to hold more information
about the property metadata
Key: SLING-3780
URL: https://issues.apache.org/jira/browse/SLING-3780
Project: Sling
Issue Type: Improvement
Components: IDE
Reporter: Robert Munteanu
Fix For: Sling Eclipse IDE 1.1.0
At the moment the ResourceProxy holds a plain {{MapString,Object}} for its
properties. As a start, it has worked pretty well. However, it leads to code
that is a bit convoluted and not correct.
For instance, we have instanceof checks to determine the property type and
multiplicity. And we probably fails to distinguish between a {{REFERENCE}} and
a {{WEAKREFERENCE}} property, or a {{STRING}} and {{NAME}} property.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
Jenkins build is unstable: sling-trunk-1.7 » Apache Sling Models Integration Tests #686
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.models.integration-tests/686/
Jenkins build is back to normal : sling-trunk-1.7 » Apache Sling Discovery Support Bundle #686
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.discovery.support/686/
Jenkins build is back to stable : sling-trunk-1.7 » Apache Sling SlingRepository Integration Tests #686
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.jcr.repository.it-jackrabbit-oak/686/
Jenkins build is unstable: sling-trunk-1.7 #686
See https://builds.apache.org/job/sling-trunk-1.7/686/changes
Jenkins build is back to normal : sling-trunk-1.6 » Apache Sling Scripting JavaScript Support #2312
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.scripting.javascript/2312/
Jenkins build is back to stable : sling-trunk-1.6 » Apache Sling Models Integration Tests #2312
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.models.integration-tests/2312/
Jenkins build is back to stable : sling-trunk-1.6 » Apache Sling Pax Exam Utilities #2312
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.paxexam.util/2312/
Jenkins build is unstable: sling-trunk-1.6 #2312
See https://builds.apache.org/job/sling-trunk-1.6/2312/changes
[jira] [Comment Edited] (SLING-3685) Document and further automate the IDE tooling release process
[
https://issues.apache.org/jira/browse/SLING-3685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14040663#comment-14040663
]
Robert Munteanu edited comment on SLING-3685 at 7/22/14 12:58 PM:
--
For reference, this is the current release process, assuming that the current
version is 1.0.1-SNAPSHOT
* set the fix version as released: {{mvn tycho-versions:set-version
-DnewVersion=1.0.2}}
* update the version of the source-bundle project to 1.0.2
* commit the change to svn
* manually tag in svn {{svn copy
https://svn.apache.org/repos/asf/sling/trunk/tooling/ide
https://svn.apache.org/repos/asf/sling/tags/sling-ide-tooling-1.0.2}}
* build the project with p2/gpg signing enabled {{mvn clean package -Psign}}
* build the source bundle from the source-bundle directory {{ mvn clean
package}}
* copy the following artifacts to
https://dist.apache.org/repos/dist/dev/sling/ide-tooling-1.0.2
** source bundle ( sling-ide-tooling-1.0.2.jar )
** zipped p2 repository ( org.apache.sling.ide.p2update-1.0.2.zip )
** ensure the artifacts are checksummed and gpg-signed
* call the vote
* Update to next version, e.g. {{mvn tycho-versions:set-version
-DnewVersion=1.0.3-SNAPSHOT}}
Once the release has passed, the following must be done:
* upload p2update.zip* to https://dist.apache.org/repos/dist/release/sling/
* upload unzipped update site to
https://dist.apache.org/repos/dist/release/sling/eclipse/1.0.2
** create GPG signatures and checksums for all uploaded jars, possibly using
the attached [^sign.sh] script
* update
https://dist.apache.org/repos/dist/release/sling/eclipse/composite\{Content,Artifacts\}.xml
to point to the latest $VERSION ( remove old one )
* (TODO how?) archive the old artifact versions but leave pointers to
archive.apache.org
was (Author: rombert):
For reference, this is the current release process, assuming that the current
version is 1.0.1-SNAPSHOT
* set the fix version as released: {{mvn tycho-versions:set-version
-DnewVersion=1.0.2}}
* commit the change to svn
* manually tag in svn {{svn copy
https://svn.apache.org/repos/asf/sling/trunk/tooling/ide
https://svn.apache.org/repos/asf/sling/tags/sling-ide-tooling-1.0.2}}
* deploy the project with p2/gpg signing enabled {{mvn clean deploy
-Psign,!eclipse-test}} ( alternatively {{mvn clean deploy
-Psign,\!eclipse-test}} to make bash happy)
* inspect the staging repository from nexus to ensure that all artifacts are
properly deployed
* call the vote
* Update to next version, e.g. {{mvn tycho-versions:set-version
-DnewVersion=1.0.3-SNAPSHOT}}
Once the release has passed, the following must be done:
* upload p2update.zip* to https://dist.apache.org/repos/dist/release/sling/
* upload unzipped update site to
https://dist.apache.org/repos/dist/release/sling/eclipse/1.0.2
** create GPG signatures and checksums for all uploaded jars, possibly using
the attached [^sign.sh] script
* update
https://dist.apache.org/repos/dist/release/sling/eclipse/composite\{Content,Artifacts\}.xml
to point to the latest $VERSION ( remove old one )
* (TODO how?) archive the old artifact versions but leave pointers to
archive.apache.org
Document and further automate the IDE tooling release process
-
Key: SLING-3685
URL: https://issues.apache.org/jira/browse/SLING-3685
Project: Sling
Issue Type: Task
Components: IDE
Reporter: Robert Munteanu
Fix For: Sling Eclipse IDE 1.0.2
Attachments: sign.sh
The current release process is very much manual, due to some of tycho's
peculiarities ( see also SLING-3620 ). This task tracks the documentation of
this release process and possible automation enhancements.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (SLING-3685) Document and further automate the IDE tooling release process
[ https://issues.apache.org/jira/browse/SLING-3685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-3685: --- Attachment: sign.sh Document and further automate the IDE tooling release process - Key: SLING-3685 URL: https://issues.apache.org/jira/browse/SLING-3685 Project: Sling Issue Type: Task Components: IDE Reporter: Robert Munteanu Fix For: Sling Eclipse IDE 1.0.2 Attachments: sign.sh The current release process is very much manual, due to some of tycho's peculiarities ( see also SLING-3620 ). This task tracks the documentation of this release process and possible automation enhancements. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (SLING-3685) Document and further automate the IDE tooling release process
[ https://issues.apache.org/jira/browse/SLING-3685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-3685: --- Attachment: (was: sign.sh) Document and further automate the IDE tooling release process - Key: SLING-3685 URL: https://issues.apache.org/jira/browse/SLING-3685 Project: Sling Issue Type: Task Components: IDE Reporter: Robert Munteanu Fix For: Sling Eclipse IDE 1.0.2 Attachments: sign.sh The current release process is very much manual, due to some of tycho's peculiarities ( see also SLING-3620 ). This task tracks the documentation of this release process and possible automation enhancements. -- This message was sent by Atlassian JIRA (v6.2#6252)
[VOTE] Release Apache Sling IDE Tooling 1.0.2
Hi, We solved 20 issues in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12327150 There are still some outstanding issues: https://issues.apache.org/jira/browse/SLING/component/12320908 The release candidate has been uploaded at https://dist.apache.org/repos/dist/dev/sling, The release artifact is the source bundle - sling-ide-tooling-1.0.2.jar - which can be used to build the project using mvn clean package The resulting binaries can be installed into an Eclipse instance from from the update site which is found at p2update/target/repository after building the project. For convenience, a pre-built update site - org.apache.sling.ide.p2update-1.0.2.zip - has also been uploaded. 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 Thanks, Robert
[jira] [Created] (SLING-3781) Fix unstable Eclipse-based tests
Robert Munteanu created SLING-3781: -- Summary: Fix unstable Eclipse-based tests Key: SLING-3781 URL: https://issues.apache.org/jira/browse/SLING-3781 Project: Sling Issue Type: Test Components: IDE, Testing Affects Versions: Sling Eclipse IDE 1.0.2 Reporter: Robert Munteanu Fix For: Sling Eclipse IDE 1.0.4 The eclipse-based tests from the eclipse-test project don't always pass. These are likely timing issues, but they result in lower confidence in their ability to catch regression tests. Here's what I have so far: * importFilesAndFoldersRespectsVltFilters(org.apache.sling.ide.test.impl.ContentImportTest): Unable to update a stale item: item.save() * importFilesWithExtraNodesUnderJcrContent(org.apache.sling.ide.test.impl.ContentImportTest): Unable to update a stale item: item.save() * deploySlingOrderedFolderWithJcrContentNode(org.apache.sling.ide.test.impl.JcrPartialCoverageAggregatesDeploymentTest): javax.jcr.PathNotFoundException: /content/test-root * deployFileWithAttachedMetadata(org.apache.sling.ide.test.impl.ContentDeploymentTest): javax.jcr.PathNotFoundException: /test/hello.esp * deployFile(org.apache.sling.ide.test.impl.ContentDeploymentTest): Unexpected status call for http://localhost:40325/test/hello.txt * deployNodeWithContentXmlInParentFolder_reverse(org.apache.sling.ide.test.impl.JcrPartialCoverageAggregatesDeploymentTest): javax.jcr.PathNotFoundException: /content/test-root/mapping/jcr:content/par/folder * changeNodePrimaryType(org.apache.sling.ide.test.impl.ContentDeploymentTest): javax.jcr.PathNotFoundException: /test -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (SLING-3782) Enable the eclipse-based tests on builds.apache.org
Robert Munteanu created SLING-3782: -- Summary: Enable the eclipse-based tests on builds.apache.org Key: SLING-3782 URL: https://issues.apache.org/jira/browse/SLING-3782 Project: Sling Issue Type: Test Components: IDE, Testing Reporter: Robert Munteanu Fix For: Sling Eclipse IDE 1.0.4 Last time I checked we were unable to run the UI tests on Jenkins since the slaves are headless and we need something like xvnc running. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (SLING-3783) Capture command-related Events during test execution
Robert Munteanu created SLING-3783: -- Summary: Capture command-related Events during test execution Key: SLING-3783 URL: https://issues.apache.org/jira/browse/SLING-3783 Project: Sling Issue Type: Test Components: IDE, Testing Reporter: Robert Munteanu Fix For: Sling Eclipse IDE 1.0.4 I have occasionally seen tests which pass but at some command executions fail. We should listen for the related events and fail if an error is reported. Also, waiting for Event execution to complete might be a good stabilisation approach for SLING-3781 -- This message was sent by Atlassian JIRA (v6.2#6252)
Re: Launchpad 7 Release?
My initial thought before writing this mail was to suggest two launchpads, one very minimal which we can release more frequently. This would contain the bare minimum and gets people playing around with it. And the other one would be the full blown thing used for testing. We could even add all modules to the full one. Looking at the snapshot list of the builder project, I guess we could just release all of them and we're got with Sling 7 and then maybe have a look at how to change things after Sling 7? So if there are people interested in driving the release of the individual bundles, we should be done with that prett fast :) And I totally agree that the documentation needs to be updated, revised Carsten 2014-07-22 14:31 GMT+02:00 Daniel Klco dk...@apache.org: I agree with a release of 7 in general. I think we need to also as Oliver indicated, create a release roadmap so we have some schedule in mind for the future. On that note, what about increasing the frequency of Launchpad releases? Right now releases are infrequent enough that it's a 'big deal' if a dependency isn't ready, which may not be the case if the launchpad releases we biannual or even quarterly. Also, the documentation for Sling 6 is quite stale and does not include many important features which are used in downstream applications. -Dan On Tue, Jul 22, 2014 at 7:30 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Tue, Jul 22, 2014 at 12:20 PM, Oliver Lietz apa...@oliverlietz.de wrote: ...My goals for a first *Karaf* Launchpad release are a current released JCR Server (whether Jackrabbit or Oak) and getting the Event bundle fixed (not sure what's the cause for a failing IT yet) Are you planning to setup integration tests for that Karaf-based launcher? If we can provide that (at http://ci.apache.org/ as well) it lets users decide which launcher they want to use, knowing that all our tests pass when that launcher is used. -Bertrand -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
Jenkins build is back to stable : sling-trunk-1.7 » Apache Sling Models Integration Tests #687
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.models.integration-tests/687/
Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Launchpad Testing #687
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing/687/
Re: obr/sling.xml
Thanks for bringing this up, Stefan - we definitely should invest some time and bring the repository xml up to date. A repository is one of the key concepts in the OSGi world and we should provide a repo with our Sling stuff. That's why this has been listed on the instructions :) But - mea culpa - I'm guilty of not following that step as well :( But I'm interested in bringing it back on Carsten 2014-07-22 10:49 GMT+02:00 Bertrand Delacretaz bdelacre...@apache.org: Hi Stefan, On Tue, Jul 22, 2014 at 10:47 AM, Stefan Egli stefane...@apache.org wrote: ...I just tried to follow the release process steps and noticed when updating the obr/sling.xml, that it hasn't been done so for quite a while (2.5 years)... This seems to prove that nobody is using that feature - we might as well drop the file to make that clear? Also, when trying to do a 'svn up' on people.apache.org, I got the following: ... svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details) ... That only touches your local sandbox - if you check with svn stat / svn diff what you are about to commit you can see exactly what will happen. -Bertrand -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
Jenkins build is still unstable: sling-trunk-1.7 #687
See https://builds.apache.org/job/sling-trunk-1.7/changes
[jira] [Created] (SLING-3784) Convert majority of eclipse-based tests to test vlt commands or the ResourceChangeCommandFactory
Robert Munteanu created SLING-3784:
--
Summary: Convert majority of eclipse-based tests to test vlt
commands or the ResourceChangeCommandFactory
Key: SLING-3784
URL: https://issues.apache.org/jira/browse/SLING-3784
Project: Sling
Issue Type: Test
Components: IDE, Testing
Affects Versions: Sling Eclipse IDE 1.0.2
Reporter: Robert Munteanu
Fix For: Sling Eclipse IDE 1.0.4
The current mechanism for content sync is
* for reach resource change/build event/manual publish
* {{SlingContentModuleFactory}} generates lists of module resources
* Eclipse change detection mechanism generates a diff
* {{SlingLaunchpadBehaviour}} invokes the {{ResourceChangeCommandFactory}} to
build vlt commands
* vlt commands are executed
The current eclipse-based tests, while useful, exercise the whole process and
are therefore more brittle and more difficult to write that the alternatives
testing a smaller part of the stack
We now have tests in place for each of the steps ( excluding of course Eclipse
diff generation, but that's out of scope ). Moving the tests to simpler
fixtures will make the tests more stable, faster and easier to write.
We should still keep some end-to-end tests, but we will not aim to test all
scenarios end-to-end.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Launchpad Testing #2313
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing/2313/
Jenkins build is still unstable: sling-trunk-1.6 #2313
See https://builds.apache.org/job/sling-trunk-1.6/changes
Re: obr/sling.xml
The instructions were predating the CMS for our site, I've updated and verified the instructions - so there is no excuse anymore to update the OBR :) Regards Carsten 2014-07-22 15:32 GMT+02:00 Carsten Ziegeler cziege...@apache.org: Thanks for bringing this up, Stefan - we definitely should invest some time and bring the repository xml up to date. A repository is one of the key concepts in the OSGi world and we should provide a repo with our Sling stuff. That's why this has been listed on the instructions :) But - mea culpa - I'm guilty of not following that step as well :( But I'm interested in bringing it back on Carsten 2014-07-22 10:49 GMT+02:00 Bertrand Delacretaz bdelacre...@apache.org: Hi Stefan, On Tue, Jul 22, 2014 at 10:47 AM, Stefan Egli stefane...@apache.org wrote: ...I just tried to follow the release process steps and noticed when updating the obr/sling.xml, that it hasn't been done so for quite a while (2.5 years)... This seems to prove that nobody is using that feature - we might as well drop the file to make that clear? Also, when trying to do a 'svn up' on people.apache.org, I got the following: ... svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details) ... That only touches your local sandbox - if you check with svn stat / svn diff what you are about to commit you can see exactly what will happen. -Bertrand -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
[jira] [Created] (SLING-3785) Try to work around repository problems during voting
Stefan Egli created SLING-3785:
--
Summary: Try to work around repository problems during voting
Key: SLING-3785
URL: https://issues.apache.org/jira/browse/SLING-3785
Project: Sling
Issue Type: Bug
Components: Extensions
Reporter: Stefan Egli
Assignee: Stefan Egli
Priority: Critical
Fix For: Discovery Impl 1.0.10
We've seen race-conditions, where the repository refuses to delete a node, with
the following exception:
{code}
16.07.2014 14:58:59.134 *ERROR* [pool-5-thread-5]
org.apache.sling.discovery.impl.common.heartbeat.HeartbeatHandler checkView:
encountered a persistence exception during view check:
org.apache.sling.api.resource.PersistenceException: Unable to delete resource
at /var/discovery/impl/previousView/4df5cd91-c99c-45d3-9b27-728c6e84f0f4
org.apache.sling.api.resource.PersistenceException: Unable to delete resource
at /var/discovery/impl/previousView/4df5cd91-c99c-45d3-9b27-728c6e84f0f4
at
org.apache.sling.jcr.resource.internal.helper.jcr.JcrResourceProvider.delete(JcrResourceProvider.java:491)
at
org.apache.sling.resourceresolver.impl.ResourceResolverImpl.delete(ResourceResolverImpl.java:1044)
at
org.apache.sling.discovery.impl.cluster.voting.VotingHandler.promote(VotingHandler.java:314)
at
org.apache.sling.discovery.impl.cluster.voting.VotingHandler.analyzeVotings(VotingHandler.java:141)
at
org.apache.sling.discovery.impl.common.heartbeat.HeartbeatHandler.doCheckView(HeartbeatHandler.java:299)
at
org.apache.sling.discovery.impl.common.heartbeat.HeartbeatHandler.checkView(HeartbeatHandler.java:277)
at
org.apache.sling.discovery.impl.common.heartbeat.HeartbeatHandler.run(HeartbeatHandler.java:153)
at
org.apache.sling.commons.scheduler.impl.QuartzJobExecutor.execute(QuartzJobExecutor.java:105)
at org.quartz.core.JobRunShell.run(JobRunShell.java:207)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: javax.jcr.ItemNotFoundException: 4f06dc87-401d-44b6-b6da-2e0bff2e2bb6
at org.apache.jackrabbit.core.ItemManager.getItemData(ItemManager.java:384)
at org.apache.jackrabbit.core.ItemManager.getNode(ItemManager.java:669)
at org.apache.jackrabbit.core.NodeImpl.onRemove(NodeImpl.java:696)
at org.apache.jackrabbit.core.NodeImpl.removeChildNode(NodeImpl.java:624)
at
org.apache.jackrabbit.core.ItemRemoveOperation.perform(ItemRemoveOperation.java:78)
at
org.apache.jackrabbit.core.session.SessionState.perform(SessionState.java:216)
at org.apache.jackrabbit.core.ItemImpl.perform(ItemImpl.java:91)
at org.apache.jackrabbit.core.ItemImpl.remove(ItemImpl.java:322)
at
org.apache.sling.jcr.resource.internal.helper.jcr.JcrResourceProvider.delete(JcrResourceProvider.java:486)
... 11 more
{code}
While this needs to be treated at the repository level, the discovery.impl can
help work around this issue by following a tested workaround:
* when delete fails, try to rename the 'previousview' node to
'previousview_trash_${UUID}'
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Resolved] (SLING-3785) Try to work around repository problems during voting
[
https://issues.apache.org/jira/browse/SLING-3785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Egli resolved SLING-3785.
Resolution: Fixed
workaround implemented as described
Try to work around repository problems during voting
Key: SLING-3785
URL: https://issues.apache.org/jira/browse/SLING-3785
Project: Sling
Issue Type: Bug
Components: Extensions
Reporter: Stefan Egli
Assignee: Stefan Egli
Priority: Critical
Fix For: Discovery Impl 1.0.10
We've seen race-conditions, where the repository refuses to delete a node,
with the following exception:
{code}
16.07.2014 14:58:59.134 *ERROR* [pool-5-thread-5]
org.apache.sling.discovery.impl.common.heartbeat.HeartbeatHandler checkView:
encountered a persistence exception during view check:
org.apache.sling.api.resource.PersistenceException: Unable to delete resource
at /var/discovery/impl/previousView/4df5cd91-c99c-45d3-9b27-728c6e84f0f4
org.apache.sling.api.resource.PersistenceException: Unable to delete resource
at /var/discovery/impl/previousView/4df5cd91-c99c-45d3-9b27-728c6e84f0f4
at
org.apache.sling.jcr.resource.internal.helper.jcr.JcrResourceProvider.delete(JcrResourceProvider.java:491)
at
org.apache.sling.resourceresolver.impl.ResourceResolverImpl.delete(ResourceResolverImpl.java:1044)
at
org.apache.sling.discovery.impl.cluster.voting.VotingHandler.promote(VotingHandler.java:314)
at
org.apache.sling.discovery.impl.cluster.voting.VotingHandler.analyzeVotings(VotingHandler.java:141)
at
org.apache.sling.discovery.impl.common.heartbeat.HeartbeatHandler.doCheckView(HeartbeatHandler.java:299)
at
org.apache.sling.discovery.impl.common.heartbeat.HeartbeatHandler.checkView(HeartbeatHandler.java:277)
at
org.apache.sling.discovery.impl.common.heartbeat.HeartbeatHandler.run(HeartbeatHandler.java:153)
at
org.apache.sling.commons.scheduler.impl.QuartzJobExecutor.execute(QuartzJobExecutor.java:105)
at org.quartz.core.JobRunShell.run(JobRunShell.java:207)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: javax.jcr.ItemNotFoundException:
4f06dc87-401d-44b6-b6da-2e0bff2e2bb6
at
org.apache.jackrabbit.core.ItemManager.getItemData(ItemManager.java:384)
at org.apache.jackrabbit.core.ItemManager.getNode(ItemManager.java:669)
at org.apache.jackrabbit.core.NodeImpl.onRemove(NodeImpl.java:696)
at org.apache.jackrabbit.core.NodeImpl.removeChildNode(NodeImpl.java:624)
at
org.apache.jackrabbit.core.ItemRemoveOperation.perform(ItemRemoveOperation.java:78)
at
org.apache.jackrabbit.core.session.SessionState.perform(SessionState.java:216)
at org.apache.jackrabbit.core.ItemImpl.perform(ItemImpl.java:91)
at org.apache.jackrabbit.core.ItemImpl.remove(ItemImpl.java:322)
at
org.apache.sling.jcr.resource.internal.helper.jcr.JcrResourceProvider.delete(JcrResourceProvider.java:486)
... 11 more
{code}
While this needs to be treated at the repository level, the discovery.impl
can help work around this issue by following a tested workaround:
* when delete fails, try to rename the 'previousview' node to
'previousview_trash_${UUID}'
--
This message was sent by Atlassian JIRA
(v6.2#6252)
Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Launchpad Testing #688
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing/688/
[jira] [Updated] (SLING-3776) JsonRendererServlet should provide a way to list children as an array
[ https://issues.apache.org/jira/browse/SLING-3776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz updated SLING-3776: --- Priority: Minor (was: Major) JsonRendererServlet should provide a way to list children as an array - Key: SLING-3776 URL: https://issues.apache.org/jira/browse/SLING-3776 Project: Sling Issue Type: Improvement Components: Servlets Affects Versions: Servlets Get 2.1.8 Reporter: Damien Antipa Priority: Minor The default JSON renderer prints all children of a node as another key-value attribute. But browsers do not respect the order printed in the response of object attributes (since the standard does not describe this). In a lot of cases I continue writing my own servlets to print the children as a json array which respects the order. Imo the default renderer should provide a selector to change the output and print children in an array. PR: https://github.com/apache/sling/pull/23 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (SLING-3786) Add tests and refactor JSON to String conversion
Bertrand Delacretaz created SLING-3786: -- Summary: Add tests and refactor JSON to String conversion Key: SLING-3786 URL: https://issues.apache.org/jira/browse/SLING-3786 Project: Sling Issue Type: Improvement Components: Commons Affects Versions: Commons JSON 2.0.6 Reporter: Bertrand Delacretaz Assignee: Bertrand Delacretaz Priority: Minor Fix For: Commons JSON 2.0.8 There's some code duplication in JSONObject, JSONArray and JSONWriter when it comes to creating JSON strings, and the test coverage is very low. We should improve this to allow extensions like SLING-3776 to be introduced without breaking existing code. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Reopened] (SLING-3785) Try to work around repository problems during voting
[
https://issues.apache.org/jira/browse/SLING-3785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Egli reopened SLING-3785:
use JackrabbitNode.rename() instead of Session.move()
Try to work around repository problems during voting
Key: SLING-3785
URL: https://issues.apache.org/jira/browse/SLING-3785
Project: Sling
Issue Type: Bug
Components: Extensions
Reporter: Stefan Egli
Assignee: Stefan Egli
Priority: Critical
Fix For: Discovery Impl 1.0.10
We've seen race-conditions, where the repository refuses to delete a node,
with the following exception:
{code}
16.07.2014 14:58:59.134 *ERROR* [pool-5-thread-5]
org.apache.sling.discovery.impl.common.heartbeat.HeartbeatHandler checkView:
encountered a persistence exception during view check:
org.apache.sling.api.resource.PersistenceException: Unable to delete resource
at /var/discovery/impl/previousView/4df5cd91-c99c-45d3-9b27-728c6e84f0f4
org.apache.sling.api.resource.PersistenceException: Unable to delete resource
at /var/discovery/impl/previousView/4df5cd91-c99c-45d3-9b27-728c6e84f0f4
at
org.apache.sling.jcr.resource.internal.helper.jcr.JcrResourceProvider.delete(JcrResourceProvider.java:491)
at
org.apache.sling.resourceresolver.impl.ResourceResolverImpl.delete(ResourceResolverImpl.java:1044)
at
org.apache.sling.discovery.impl.cluster.voting.VotingHandler.promote(VotingHandler.java:314)
at
org.apache.sling.discovery.impl.cluster.voting.VotingHandler.analyzeVotings(VotingHandler.java:141)
at
org.apache.sling.discovery.impl.common.heartbeat.HeartbeatHandler.doCheckView(HeartbeatHandler.java:299)
at
org.apache.sling.discovery.impl.common.heartbeat.HeartbeatHandler.checkView(HeartbeatHandler.java:277)
at
org.apache.sling.discovery.impl.common.heartbeat.HeartbeatHandler.run(HeartbeatHandler.java:153)
at
org.apache.sling.commons.scheduler.impl.QuartzJobExecutor.execute(QuartzJobExecutor.java:105)
at org.quartz.core.JobRunShell.run(JobRunShell.java:207)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: javax.jcr.ItemNotFoundException:
4f06dc87-401d-44b6-b6da-2e0bff2e2bb6
at
org.apache.jackrabbit.core.ItemManager.getItemData(ItemManager.java:384)
at org.apache.jackrabbit.core.ItemManager.getNode(ItemManager.java:669)
at org.apache.jackrabbit.core.NodeImpl.onRemove(NodeImpl.java:696)
at org.apache.jackrabbit.core.NodeImpl.removeChildNode(NodeImpl.java:624)
at
org.apache.jackrabbit.core.ItemRemoveOperation.perform(ItemRemoveOperation.java:78)
at
org.apache.jackrabbit.core.session.SessionState.perform(SessionState.java:216)
at org.apache.jackrabbit.core.ItemImpl.perform(ItemImpl.java:91)
at org.apache.jackrabbit.core.ItemImpl.remove(ItemImpl.java:322)
at
org.apache.sling.jcr.resource.internal.helper.jcr.JcrResourceProvider.delete(JcrResourceProvider.java:486)
... 11 more
{code}
While this needs to be treated at the repository level, the discovery.impl
can help work around this issue by following a tested workaround:
* when delete fails, try to rename the 'previousview' node to
'previousview_trash_${UUID}'
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Comment Edited] (SLING-3785) Try to work around repository problems during voting
[
https://issues.apache.org/jira/browse/SLING-3785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14070369#comment-14070369
]
Stefan Egli edited comment on SLING-3785 at 7/22/14 3:15 PM:
-
-use JackrabbitNode.rename() instead of Session.move()-
was (Author: egli):
use JackrabbitNode.rename() instead of Session.move()
Try to work around repository problems during voting
Key: SLING-3785
URL: https://issues.apache.org/jira/browse/SLING-3785
Project: Sling
Issue Type: Bug
Components: Extensions
Reporter: Stefan Egli
Assignee: Stefan Egli
Priority: Critical
Fix For: Discovery Impl 1.0.10
We've seen race-conditions, where the repository refuses to delete a node,
with the following exception:
{code}
16.07.2014 14:58:59.134 *ERROR* [pool-5-thread-5]
org.apache.sling.discovery.impl.common.heartbeat.HeartbeatHandler checkView:
encountered a persistence exception during view check:
org.apache.sling.api.resource.PersistenceException: Unable to delete resource
at /var/discovery/impl/previousView/4df5cd91-c99c-45d3-9b27-728c6e84f0f4
org.apache.sling.api.resource.PersistenceException: Unable to delete resource
at /var/discovery/impl/previousView/4df5cd91-c99c-45d3-9b27-728c6e84f0f4
at
org.apache.sling.jcr.resource.internal.helper.jcr.JcrResourceProvider.delete(JcrResourceProvider.java:491)
at
org.apache.sling.resourceresolver.impl.ResourceResolverImpl.delete(ResourceResolverImpl.java:1044)
at
org.apache.sling.discovery.impl.cluster.voting.VotingHandler.promote(VotingHandler.java:314)
at
org.apache.sling.discovery.impl.cluster.voting.VotingHandler.analyzeVotings(VotingHandler.java:141)
at
org.apache.sling.discovery.impl.common.heartbeat.HeartbeatHandler.doCheckView(HeartbeatHandler.java:299)
at
org.apache.sling.discovery.impl.common.heartbeat.HeartbeatHandler.checkView(HeartbeatHandler.java:277)
at
org.apache.sling.discovery.impl.common.heartbeat.HeartbeatHandler.run(HeartbeatHandler.java:153)
at
org.apache.sling.commons.scheduler.impl.QuartzJobExecutor.execute(QuartzJobExecutor.java:105)
at org.quartz.core.JobRunShell.run(JobRunShell.java:207)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: javax.jcr.ItemNotFoundException:
4f06dc87-401d-44b6-b6da-2e0bff2e2bb6
at
org.apache.jackrabbit.core.ItemManager.getItemData(ItemManager.java:384)
at org.apache.jackrabbit.core.ItemManager.getNode(ItemManager.java:669)
at org.apache.jackrabbit.core.NodeImpl.onRemove(NodeImpl.java:696)
at org.apache.jackrabbit.core.NodeImpl.removeChildNode(NodeImpl.java:624)
at
org.apache.jackrabbit.core.ItemRemoveOperation.perform(ItemRemoveOperation.java:78)
at
org.apache.jackrabbit.core.session.SessionState.perform(SessionState.java:216)
at org.apache.jackrabbit.core.ItemImpl.perform(ItemImpl.java:91)
at org.apache.jackrabbit.core.ItemImpl.remove(ItemImpl.java:322)
at
org.apache.sling.jcr.resource.internal.helper.jcr.JcrResourceProvider.delete(JcrResourceProvider.java:486)
... 11 more
{code}
While this needs to be treated at the repository level, the discovery.impl
can help work around this issue by following a tested workaround:
* when delete fails, try to rename the 'previousview' node to
'previousview_trash_${UUID}'
--
This message was sent by Atlassian JIRA
(v6.2#6252)
Jenkins build became unstable: sling-trunk-1.7 » Apache Sling Resource-Based Discovery Service #689
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.discovery.impl/689/changes
Jenkins build is still unstable: sling-trunk-1.7 #689
See https://builds.apache.org/job/sling-trunk-1.7/changes
Re: [VOTE] Release Apache Sling IDE Tooling 1.0.2
+1 (verified source.jar can be built via 'mvn clean install' - installed in local eclipse and smoke-tested) Cheers, Stefan On 7/22/14 3:16 PM, Robert Munteanu romb...@apache.org wrote: Hi, We solved 20 issues in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12327150 There are still some outstanding issues: https://issues.apache.org/jira/browse/SLING/component/12320908 The release candidate has been uploaded at https://dist.apache.org/repos/dist/dev/sling, The release artifact is the source bundle - sling-ide-tooling-1.0.2.jar - which can be used to build the project using mvn clean package The resulting binaries can be installed into an Eclipse instance from from the update site which is found at p2update/target/repository after building the project. For convenience, a pre-built update site - org.apache.sling.ide.p2update-1.0.2.zip - has also been uploaded. 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 Thanks, Robert
Build failed in Jenkins: sling-trunk-1.6 » Apache Sling JCR Installer #2314
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.installer.provider.jcr/2314/ -- [...truncated 16 lines...] [INFO] --- maven-remote-resources-plugin:1.5:process (default) @ org.apache.sling.installer.provider.jcr --- [INFO] [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ org.apache.sling.installer.provider.jcr --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 2 resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-antrun-plugin:1.7:run (check-memory-task) @ org.apache.sling.installer.provider.jcr --- [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-compiler-plugin:3.1:compile (default-compile) @ org.apache.sling.installer.provider.jcr --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 8 source files to https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.installer.provider.jcr/ws/target/classes [WARNING] Note: Some input files use or override a deprecated API. [WARNING] Note: Recompile with -Xlint:deprecation for details. [INFO] [INFO] --- maven-scr-plugin:1.16.0:scr (generate-scr-scrdescriptor) @ org.apache.sling.installer.provider.jcr --- [INFO] Generating 1 MetaType Descriptors in https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.installer.provider.jcr/ws/target/classes/OSGI-INF/metatype/org.apache.sling.installer.provider.jcr.impl.JcrInstaller.xml [INFO] Writing 1 Service Component Descriptors to https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.installer.provider.jcr/ws/target/classes/OSGI-INF/org.apache.sling.installer.provider.jcr.impl.JcrInstaller.xml [INFO] [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ org.apache.sling.installer.provider.jcr --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 1 resource [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ org.apache.sling.installer.provider.jcr --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 11 source files to https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.installer.provider.jcr/ws/target/test-classes [WARNING] Note: https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.installer.provider.jcr/ws/src/test/java/org/apache/sling/installer/provider/jcr/impl/ContentHelper.java uses or overrides a deprecated API. [WARNING] Note: Recompile with -Xlint:deprecation for details. [INFO] [INFO] --- maven-surefire-plugin:2.16:test (default-test) @ org.apache.sling.installer.provider.jcr --- [INFO] Surefire report directory: https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.installer.provider.jcr/ws/target/surefire-reports --- T E S T S --- Running org.apache.sling.installer.provider.jcr.impl.FolderNameFilterTest 15:30:49,364 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Found resource [logback-test.xml] at [https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.installer.provider.jcr/ws/target/test-classes/logback-test.xml] 15:30:49,454 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - debug attribute not set 15:30:49,462 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.ConsoleAppender] 15:30:49,468 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [STDOUT] 15:30:49,490 |-ERROR in ch.qos.logback.core.joran.spi.Interpreter@21:15 - no applicable action for [file], current pattern is [[configuration][appender][file]] 15:30:49,493 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property 15:30:49,493 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Pushing component [encoder] on top of the object stack. 15:30:49,560 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [org.apache.sling.jcr.jcrinstall.impl] to DEBUG 15:30:49,560 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting additivity of logger [org.apache.sling.jcr.jcrinstall.impl] to true 15:30:49,560 |-INFO in
[jira] [Created] (SLING-3787) Make the server info configurable
Carsten Ziegeler created SLING-3787: --- Summary: Make the server info configurable Key: SLING-3787 URL: https://issues.apache.org/jira/browse/SLING-3787 Project: Sling Issue Type: Improvement Components: Engine Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Engine 2.3.4 Right now, the server info returned by Sling is more or less hard coded, it would be nice to make this configurable to allow custom server information to be returned. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (SLING-3785) Try to work around repository problems during voting
[
https://issues.apache.org/jira/browse/SLING-3785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Egli resolved SLING-3785.
Resolution: Fixed
Can't use JackrabbitNode.rename() since that would not work on oak
Try to work around repository problems during voting
Key: SLING-3785
URL: https://issues.apache.org/jira/browse/SLING-3785
Project: Sling
Issue Type: Bug
Components: Extensions
Reporter: Stefan Egli
Assignee: Stefan Egli
Priority: Critical
Fix For: Discovery Impl 1.0.10
We've seen race-conditions, where the repository refuses to delete a node,
with the following exception:
{code}
16.07.2014 14:58:59.134 *ERROR* [pool-5-thread-5]
org.apache.sling.discovery.impl.common.heartbeat.HeartbeatHandler checkView:
encountered a persistence exception during view check:
org.apache.sling.api.resource.PersistenceException: Unable to delete resource
at /var/discovery/impl/previousView/4df5cd91-c99c-45d3-9b27-728c6e84f0f4
org.apache.sling.api.resource.PersistenceException: Unable to delete resource
at /var/discovery/impl/previousView/4df5cd91-c99c-45d3-9b27-728c6e84f0f4
at
org.apache.sling.jcr.resource.internal.helper.jcr.JcrResourceProvider.delete(JcrResourceProvider.java:491)
at
org.apache.sling.resourceresolver.impl.ResourceResolverImpl.delete(ResourceResolverImpl.java:1044)
at
org.apache.sling.discovery.impl.cluster.voting.VotingHandler.promote(VotingHandler.java:314)
at
org.apache.sling.discovery.impl.cluster.voting.VotingHandler.analyzeVotings(VotingHandler.java:141)
at
org.apache.sling.discovery.impl.common.heartbeat.HeartbeatHandler.doCheckView(HeartbeatHandler.java:299)
at
org.apache.sling.discovery.impl.common.heartbeat.HeartbeatHandler.checkView(HeartbeatHandler.java:277)
at
org.apache.sling.discovery.impl.common.heartbeat.HeartbeatHandler.run(HeartbeatHandler.java:153)
at
org.apache.sling.commons.scheduler.impl.QuartzJobExecutor.execute(QuartzJobExecutor.java:105)
at org.quartz.core.JobRunShell.run(JobRunShell.java:207)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: javax.jcr.ItemNotFoundException:
4f06dc87-401d-44b6-b6da-2e0bff2e2bb6
at
org.apache.jackrabbit.core.ItemManager.getItemData(ItemManager.java:384)
at org.apache.jackrabbit.core.ItemManager.getNode(ItemManager.java:669)
at org.apache.jackrabbit.core.NodeImpl.onRemove(NodeImpl.java:696)
at org.apache.jackrabbit.core.NodeImpl.removeChildNode(NodeImpl.java:624)
at
org.apache.jackrabbit.core.ItemRemoveOperation.perform(ItemRemoveOperation.java:78)
at
org.apache.jackrabbit.core.session.SessionState.perform(SessionState.java:216)
at org.apache.jackrabbit.core.ItemImpl.perform(ItemImpl.java:91)
at org.apache.jackrabbit.core.ItemImpl.remove(ItemImpl.java:322)
at
org.apache.sling.jcr.resource.internal.helper.jcr.JcrResourceProvider.delete(JcrResourceProvider.java:486)
... 11 more
{code}
While this needs to be treated at the repository level, the discovery.impl
can help work around this issue by following a tested workaround:
* when delete fails, try to rename the 'previousview' node to
'previousview_trash_${UUID}'
--
This message was sent by Atlassian JIRA
(v6.2#6252)
Build failed in Jenkins: sling-trunk-1.6 #2314
See https://builds.apache.org/job/sling-trunk-1.6/2314/changes Changes: [bdelacretaz] SLING-3786 - add tests for the conversion of JSON data to strings [stefanegli] SLING-3785 : trying moving previousviews if delete does not work - might help as a workaround of a repository problem -- [...truncated 37021 lines...] [INFO] Sling Taglib Archetype SUCCESS [5.082s] [INFO] Apache Sling API .. SUCCESS [12.349s] [INFO] Apache Sling Resource Resolver SUCCESS [11.459s] [INFO] Apache Sling System Bundle Extension: Java Transaction API SUCCESS [5.224s] [INFO] Apache Sling System Bundle Extension: XML APIs SUCCESS [5.568s] [INFO] Apache Sling System Bundle Extension: Activation API SUCCESS [5.250s] [INFO] Apache Sling System Bundle Extension: WS APIs . SUCCESS [5.520s] [INFO] Apache Sling Dynamic Class Loader Support . SUCCESS [14.544s] [INFO] Apache Sling Commons Java Compiler SUCCESS [8.738s] [INFO] Apache Sling JSON Library . SUCCESS [8.593s] [INFO] Apache Sling SLF4J Implementation (Logback) ... SUCCESS [35.757s] [INFO] Apache Sling OSGi LogService Implementation ... SUCCESS [3.530s] [INFO] Apache Sling MIME type mapping support SUCCESS [8.405s] [INFO] Apache Sling Commons OSGi support . SUCCESS [8.079s] [INFO] Apache Sling Scheduler Support SUCCESS [6.355s] [INFO] Apache Sling Testing Utilities SUCCESS [15.495s] [INFO] Apache Sling Thread Dumper SUCCESS [3.731s] [INFO] Apache Sling Thread Support ... SUCCESS [3.833s] [INFO] Apache Sling Authentication Service ... SUCCESS [6.455s] [INFO] Apache Sling OpenID Authentication SUCCESS [12.302s] [INFO] Apache Sling Form Based Authentication Handler SUCCESS [9.148s] [INFO] Apache Sling Authentication Selector .. SUCCESS [3.911s] [INFO] Apache Sling Engine Implementation SUCCESS [21.883s] [INFO] Apache Sling Repository API Bundle SUCCESS [4.061s] [INFO] Apache Sling JCR Base Bundle .. SUCCESS [6.450s] [INFO] Apache Sling JCR ClassLoader .. SUCCESS [6.017s] [INFO] Apache Sling Initial Content Loader ... SUCCESS [8.840s] [INFO] Apache Sling Jackrabbit Embedded Repository ... SUCCESS [11.656s] [INFO] Apache Sling Jackrabbit UserManager Support ... SUCCESS [6.822s] [INFO] Apache Sling Jackrabbit JSR-283 Access Control Manager Support SUCCESS [5.736s] [INFO] Apache Sling Wrapper Bundle for the JCR API ... SUCCESS [5.156s] [INFO] Apache Sling Object Content Mapping ... SUCCESS [8.464s] [INFO] Apache Sling JCR Resource Resolver SUCCESS [27.701s] [INFO] Apache Sling JCR Repository Registration .. SUCCESS [6.349s] [INFO] Apache Sling Simple WebDAV Access to repositories . SUCCESS [6.332s] [INFO] Apache Sling DavEx Access to repositories . SUCCESS [8.422s] [INFO] Apache Sling JCR WebConsole Bundle SUCCESS [6.233s] [INFO] Apache Sling Oak Repository Server SUCCESS [6.652s] [INFO] Apache Sling SlingRepository Integration Tests SUCCESS [24.551s] [INFO] Apache Sling Servlet Resolver . SUCCESS [9.202s] [INFO] Apache Sling Default GET Servlets . SUCCESS [6.557s] [INFO] Apache Sling Default POST Servlets SUCCESS [9.914s] [INFO] Apache Sling Compat Servlets .. SUCCESS [3.871s] [INFO] Apache Sling Scripting Implementation API . SUCCESS [4.119s] [INFO] Apache Sling Scripting Core implementation SUCCESS [15.393s] [INFO] Apache Sling Scripting JavaScript Support . SUCCESS [14.598s] [INFO] Apache Sling Scripting JSP Support SUCCESS [13.624s] [INFO] Apache Sling JSP Tag Library .. SUCCESS [9.686s] [INFO] Apache Sling JSP Standard Tag Library . SUCCESS [3.451s] [INFO] Apache Sling Adapter Manager Implementation ... SUCCESS [6.152s] [INFO] Apache Sling Bundle Resource Provider . SUCCESS [5.683s] [INFO] Apache Sling Discovery API SUCCESS [5.056s] [INFO] Apache Sling Resource-Based Discovery Service . SUCCESS [2:36.569s] [INFO] Apache Sling Discovery Support Bundle . SUCCESS [6.152s] [INFO] Apache Sling Discovery Standalone Implementation .. SUCCESS [5.677s] [INFO] Apache Sling Event Support SUCCESS [6:20.298s] [INFO] Apache Sling Feature Flags SUCCESS [5.966s] [INFO] Apache Sling Filesystem Resource Provider . SUCCESS [5.561s] [INFO] Apache Sling javax.activation bundle .. SUCCESS [8.363s] [INFO] Apache Sling Service User Mapper .. SUCCESS [8.273s] [INFO] Apache Sling Settings
Re: [VOTE] Release Apache Sling IDE Tooling 1.0.2
I think what might me missing is an SVN tag for the release? Or am I just not finding it :S Cheers, Stefan On 7/22/14 5:31 PM, Stefan Egli stefane...@apache.org wrote: +1 (verified source.jar can be built via 'mvn clean install' - installed in local eclipse and smoke-tested) Cheers, Stefan On 7/22/14 3:16 PM, Robert Munteanu romb...@apache.org wrote: Hi, We solved 20 issues in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12327150 There are still some outstanding issues: https://issues.apache.org/jira/browse/SLING/component/12320908 The release candidate has been uploaded at https://dist.apache.org/repos/dist/dev/sling, The release artifact is the source bundle - sling-ide-tooling-1.0.2.jar - which can be used to build the project using mvn clean package The resulting binaries can be installed into an Eclipse instance from from the update site which is found at p2update/target/repository after building the project. For convenience, a pre-built update site - org.apache.sling.ide.p2update-1.0.2.zip - has also been uploaded. 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 Thanks, Robert
Re: [VOTE] Release Apache Sling IDE Tooling 1.0.2
On Tue, Jul 22, 2014 at 6:55 PM, Stefan Egli stefane...@apache.org wrote: I think what might me missing is an SVN tag for the release? Or am I just not finding it :S The release is tagged at https://svn.apache.org/repos/asf/sling/tags/sling-ide-tooling-1.0.2/ Robert Cheers, Stefan On 7/22/14 5:31 PM, Stefan Egli stefane...@apache.org wrote: +1 (verified source.jar can be built via 'mvn clean install' - installed in local eclipse and smoke-tested) Cheers, Stefan On 7/22/14 3:16 PM, Robert Munteanu romb...@apache.org wrote: Hi, We solved 20 issues in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12327150 There are still some outstanding issues: https://issues.apache.org/jira/browse/SLING/component/12320908 The release candidate has been uploaded at https://dist.apache.org/repos/dist/dev/sling, The release artifact is the source bundle - sling-ide-tooling-1.0.2.jar - which can be used to build the project using mvn clean package The resulting binaries can be installed into an Eclipse instance from from the update site which is found at p2update/target/repository after building the project. For convenience, a pre-built update site - org.apache.sling.ide.p2update-1.0.2.zip - has also been uploaded. 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 Thanks, Robert -- Sent from my (old) computer
Re: [VOTE] Release Apache Sling IDE Tooling 1.0.2
okeee :) On 7/22/14 5:56 PM, Robert Munteanu rob...@lmn.ro wrote: On Tue, Jul 22, 2014 at 6:55 PM, Stefan Egli stefane...@apache.org wrote: I think what might me missing is an SVN tag for the release? Or am I just not finding it :S The release is tagged at https://svn.apache.org/repos/asf/sling/tags/sling-ide-tooling-1.0.2/ Robert Cheers, Stefan On 7/22/14 5:31 PM, Stefan Egli stefane...@apache.org wrote: +1 (verified source.jar can be built via 'mvn clean install' - installed in local eclipse and smoke-tested) Cheers, Stefan On 7/22/14 3:16 PM, Robert Munteanu romb...@apache.org wrote: Hi, We solved 20 issues in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12327150 There are still some outstanding issues: https://issues.apache.org/jira/browse/SLING/component/12320908 The release candidate has been uploaded at https://dist.apache.org/repos/dist/dev/sling, The release artifact is the source bundle - sling-ide-tooling-1.0.2.jar - which can be used to build the project using mvn clean package The resulting binaries can be installed into an Eclipse instance from from the update site which is found at p2update/target/repository after building the project. For convenience, a pre-built update site - org.apache.sling.ide.p2update-1.0.2.zip - has also been uploaded. 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 Thanks, Robert -- Sent from my (old) computer
[jira] [Resolved] (SLING-3787) Make the server info configurable
[ https://issues.apache.org/jira/browse/SLING-3787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-3787. - Resolution: Fixed Added configuration option in rev 1612605 Make the server info configurable - Key: SLING-3787 URL: https://issues.apache.org/jira/browse/SLING-3787 Project: Sling Issue Type: Improvement Components: Engine Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Engine 2.3.4 Right now, the server info returned by Sling is more or less hard coded, it would be nice to make this configurable to allow custom server information to be returned. -- This message was sent by Atlassian JIRA (v6.2#6252)
problems launching the current sling release
hi, I downloaded the standalone bundle from [1] and trying to run it with java -jar org.apache.sling.launchpad-6-standalone.jar getting the following exception (java 7 on windows): 22.07.2014 09:30:18.229 *INFO* [main] Setting sling.home=sling (default) 22.07.2014 09:30:18.230 *INFO* [main] Starting Sling in sling (C:\projects\sling\sling) 22.07.2014 09:30:18.243 *INFO* [main] Renaming current launcher jar org.apache.sling.launchpad.base.jar.1406046590632 to org.apache.sling.launchpad.base.jar 22.07.2014 09:30:18.245 *INFO* [main] Checking launcher JAR in folder sling 22.07.2014 09:30:18.255 *INFO* [main] Existing launcher is up to date, using it: 2.3.0 (org.apache.sling.launchpad.base.jar) 22.07.2014 09:30:18.256 *INFO* [main] Loading launcher class org.apache.sling.launchpad.base.app.MainDelegate from org.apache.sling.launchpad.base.jar 22.07.2014 09:30:18.276 *INFO* [main] Starting launcher ... 22.07.2014 09:30:18.277 *INFO* [main] HTTP server port: 8080 22.07.2014 09:30:18.349 *ERROR* [main] Failed to Start OSGi framework org.osgi.framework.BundleException: Uncaught Instantiation Issue: java.lang.ArrayIndexOutOfBoundsException: -1 at org.apache.sling.launchpad.base.impl.Sling.init(Sling.java:245) at org.apache.sling.launchpad.base.app.MainDelegate$1.init(MainDelegate.java:159) at org.apache.sling.launchpad.base.app.MainDelegate.start(MainDelegate.java:159) at org.apache.sling.launchpad.app.Main.startSling(Main.java:244) at org.apache.sling.launchpad.app.Main.init(Main.java:107) at org.apache.sling.launchpad.app.Main.main(Main.java:56) Caused by: java.lang.ArrayIndexOutOfBoundsException: -1 at java.util.ArrayList.elementData(ArrayList.java:403) at java.util.ArrayList.get(ArrayList.java:416) at org.apache.felix.framework.BundleImpl.getCurrentModule(BundleImpl.java:1046) at org.apache.felix.framework.BundleImpl.getSymbolicName(BundleImpl.java:863) at org.apache.sling.launchpad.base.impl.SlingFelix.getSymbolicName(SlingFelix.java:32) at org.apache.felix.framework.Felix.toString(Felix.java:1012) at org.apache.felix.framework.Logger.doLog(Logger.java:128) at org.apache.felix.framework.Logger._log(Logger.java:181) at org.apache.felix.framework.Logger.log(Logger.java:114) at org.apache.felix.framework.ExtensionManager.init(ExtensionManager.java:201) at org.apache.felix.framework.Felix.init(Felix.java:374) at org.apache.sling.launchpad.base.impl.SlingFelix.init(SlingFelix.java:39) at org.apache.sling.launchpad.base.impl.Sling.init(Sling.java:235) ... 5 more 22.07.2014 09:30:18.351 *ERROR* [main] There was a problem launching Sling 22.07.2014 09:30:18.352 *INFO* [Sling Terminator] Java VM is shutting down [1] http://sling.apache.org/downloads.cgi
Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Launchpad Testing #690
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing/690/
Jenkins build is back to stable : sling-trunk-1.7 » Apache Sling Resource-Based Discovery Service #690
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.discovery.impl/690/
Jenkins build is still unstable: sling-trunk-1.7 #690
See https://builds.apache.org/job/sling-trunk-1.7/changes
Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Launchpad Testing #691
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing/691/
Jenkins build is still unstable: sling-trunk-1.7 #691
See https://builds.apache.org/job/sling-trunk-1.7/changes
Re: problems launching the current sling release
I am not sure if launchpad 6 is supported on Java 7. I had similar issue in past as well. Yogesh On Jul 22, 2014, at 9:37 AM, Ruben Reusser r...@headwire.com wrote: hi, I downloaded the standalone bundle from [1] and trying to run it with java -jar org.apache.sling.launchpad-6-standalone.jar getting the following exception (java 7 on windows): 22.07.2014 09:30:18.229 *INFO* [main] Setting sling.home=sling (default) 22.07.2014 09:30:18.230 *INFO* [main] Starting Sling in sling (C:\projects\sling\sling) 22.07.2014 09:30:18.243 *INFO* [main] Renaming current launcher jar org.apache.sling.launchpad.base.jar.1406046590632 to org.apache.sling.launchpad.base.jar 22.07.2014 09:30:18.245 *INFO* [main] Checking launcher JAR in folder sling 22.07.2014 09:30:18.255 *INFO* [main] Existing launcher is up to date, using it: 2.3.0 (org.apache.sling.launchpad.base.jar) 22.07.2014 09:30:18.256 *INFO* [main] Loading launcher class org.apache.sling.launchpad.base.app.MainDelegate from org.apache.sling.launchpad.base.jar 22.07.2014 09:30:18.276 *INFO* [main] Starting launcher ... 22.07.2014 09:30:18.277 *INFO* [main] HTTP server port: 8080 22.07.2014 09:30:18.349 *ERROR* [main] Failed to Start OSGi framework org.osgi.framework.BundleException: Uncaught Instantiation Issue: java.lang.ArrayIndexOutOfBoundsException: -1 at org.apache.sling.launchpad.base.impl.Sling.init(Sling.java:245) at org.apache.sling.launchpad.base.app.MainDelegate$1.init(MainDelegate.java:159) at org.apache.sling.launchpad.base.app.MainDelegate.start(MainDelegate.java:159) at org.apache.sling.launchpad.app.Main.startSling(Main.java:244) at org.apache.sling.launchpad.app.Main.init(Main.java:107) at org.apache.sling.launchpad.app.Main.main(Main.java:56) Caused by: java.lang.ArrayIndexOutOfBoundsException: -1 at java.util.ArrayList.elementData(ArrayList.java:403) at java.util.ArrayList.get(ArrayList.java:416) at org.apache.felix.framework.BundleImpl.getCurrentModule(BundleImpl.java:1046) at org.apache.felix.framework.BundleImpl.getSymbolicName(BundleImpl.java:863) at org.apache.sling.launchpad.base.impl.SlingFelix.getSymbolicName(SlingFelix.java:32) at org.apache.felix.framework.Felix.toString(Felix.java:1012) at org.apache.felix.framework.Logger.doLog(Logger.java:128) at org.apache.felix.framework.Logger._log(Logger.java:181) at org.apache.felix.framework.Logger.log(Logger.java:114) at org.apache.felix.framework.ExtensionManager.init(ExtensionManager.java:201) at org.apache.felix.framework.Felix.init(Felix.java:374) at org.apache.sling.launchpad.base.impl.SlingFelix.init(SlingFelix.java:39) at org.apache.sling.launchpad.base.impl.Sling.init(Sling.java:235) ... 5 more 22.07.2014 09:30:18.351 *ERROR* [main] There was a problem launching Sling 22.07.2014 09:30:18.352 *INFO* [Sling Terminator] Java VM is shutting down [1] http://sling.apache.org/downloads.cgi
Jenkins build is unstable: sling-trunk-1.6 » Apache Sling Launchpad Testing #2315
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing/2315/
Jenkins build is back to normal : sling-trunk-1.6 » Apache Sling JCR Installer #2315
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.installer.provider.jcr/2315/
Jenkins build is unstable: sling-trunk-1.6 #2315
See https://builds.apache.org/job/sling-trunk-1.6/2315/changes
Re: problems launching the current sling release
On Tue, Jul 22, 2014 at 8:34 PM, Yogesh Upadhyay upadhyay.yog...@gmail.com wrote: I am not sure if launchpad 6 is supported on Java 7. I had similar issue in past as well. Launchpad 6 does not support Java 7. We're discussing a new release which will correct this. Robert Yogesh On Jul 22, 2014, at 9:37 AM, Ruben Reusser r...@headwire.com wrote: hi, I downloaded the standalone bundle from [1] and trying to run it with java -jar org.apache.sling.launchpad-6-standalone.jar getting the following exception (java 7 on windows): 22.07.2014 09:30:18.229 *INFO* [main] Setting sling.home=sling (default) 22.07.2014 09:30:18.230 *INFO* [main] Starting Sling in sling (C:\projects\sling\sling) 22.07.2014 09:30:18.243 *INFO* [main] Renaming current launcher jar org.apache.sling.launchpad.base.jar.1406046590632 to org.apache.sling.launchpad.base.jar 22.07.2014 09:30:18.245 *INFO* [main] Checking launcher JAR in folder sling 22.07.2014 09:30:18.255 *INFO* [main] Existing launcher is up to date, using it: 2.3.0 (org.apache.sling.launchpad.base.jar) 22.07.2014 09:30:18.256 *INFO* [main] Loading launcher class org.apache.sling.launchpad.base.app.MainDelegate from org.apache.sling.launchpad.base.jar 22.07.2014 09:30:18.276 *INFO* [main] Starting launcher ... 22.07.2014 09:30:18.277 *INFO* [main] HTTP server port: 8080 22.07.2014 09:30:18.349 *ERROR* [main] Failed to Start OSGi framework org.osgi.framework.BundleException: Uncaught Instantiation Issue: java.lang.ArrayIndexOutOfBoundsException: -1 at org.apache.sling.launchpad.base.impl.Sling.init(Sling.java:245) at org.apache.sling.launchpad.base.app.MainDelegate$1.init(MainDelegate.java:159) at org.apache.sling.launchpad.base.app.MainDelegate.start(MainDelegate.java:159) at org.apache.sling.launchpad.app.Main.startSling(Main.java:244) at org.apache.sling.launchpad.app.Main.init(Main.java:107) at org.apache.sling.launchpad.app.Main.main(Main.java:56) Caused by: java.lang.ArrayIndexOutOfBoundsException: -1 at java.util.ArrayList.elementData(ArrayList.java:403) at java.util.ArrayList.get(ArrayList.java:416) at org.apache.felix.framework.BundleImpl.getCurrentModule(BundleImpl.java:1046) at org.apache.felix.framework.BundleImpl.getSymbolicName(BundleImpl.java:863) at org.apache.sling.launchpad.base.impl.SlingFelix.getSymbolicName(SlingFelix.java:32) at org.apache.felix.framework.Felix.toString(Felix.java:1012) at org.apache.felix.framework.Logger.doLog(Logger.java:128) at org.apache.felix.framework.Logger._log(Logger.java:181) at org.apache.felix.framework.Logger.log(Logger.java:114) at org.apache.felix.framework.ExtensionManager.init(ExtensionManager.java:201) at org.apache.felix.framework.Felix.init(Felix.java:374) at org.apache.sling.launchpad.base.impl.SlingFelix.init(SlingFelix.java:39) at org.apache.sling.launchpad.base.impl.Sling.init(Sling.java:235) ... 5 more 22.07.2014 09:30:18.351 *ERROR* [main] There was a problem launching Sling 22.07.2014 09:30:18.352 *INFO* [Sling Terminator] Java VM is shutting down [1] http://sling.apache.org/downloads.cgi
Re: Launchpad 7 Release?
On Tue, 2014-07-22 at 15:30 +0200, Carsten Ziegeler wrote: Looking at the snapshot list of the builder project, I guess we could just release all of them and we're got with Sling 7 and then maybe have a look at how to change things after Sling 7? +1, I think it's important to have a Sling 7 release soon. It's going to be fun though, we have a large number of releases to perform :-) $ grep -c -e SNAPSHOT src/main/bundles/list.xml 20 Robert
[jira] [Commented] (SLING-3782) Enable the eclipse-based tests on builds.apache.org
[
https://issues.apache.org/jira/browse/SLING-3782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14070741#comment-14070741
]
Robert Munteanu commented on SLING-3782:
Set up
https://builds.apache.org/view/S-Z/view/Sling/job/sling-ide-1.6-ui-tests/ to
verify the way UI tests are executed.
The job execution has failed, the underlying error, found in
https://builds.apache.org/view/S-Z/view/Sling/job/sling-ide-1.6-ui-tests/ws/eclipse-test/target/work/data/.metadata/.log,
is
{noformat}!SESSION 2014-07-22 19:15:27.294
---
eclipse.buildId=unknown
java.version=1.6.0_45
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
Framework arguments: -application org.eclipse.tycho.surefire.osgibooter.uitest
-testproperties
/home/jenkins/jenkins-slave/workspace/sling-ide-1.6-ui-tests/eclipse-test/target/surefire.properties
-nouithread
Command-line arguments: -data
/home/jenkins/jenkins-slave/workspace/sling-ide-1.6-ui-tests/eclipse-test/target/work/data
-application org.eclipse.tycho.surefire.osgibooter.uitest -testproperties
/home/jenkins/jenkins-slave/workspace/sling-ide-1.6-ui-tests/eclipse-test/target/surefire.properties
-nouithread
!ENTRY org.eclipse.osgi 4 0 2014-07-22 19:15:29.669
!MESSAGE Application error
!STACK 1
java.lang.UnsatisfiedLinkError: Could not load SWT library. Reasons:
/home/jenkins/jenkins-slave/workspace/sling-ide-1.6-ui-tests/eclipse-test/target/work/configuration/org.eclipse.osgi/bundles/146/1/.cp/libswt-pi-gtk-4335.so:
libgtk-x11-2.0.so.0: cannot open shared object file: No such file or directory
no swt-pi-gtk in java.library.path
Can't load library:
/home/jenkins/.swt/lib/linux/x86/libswt-pi-gtk-4335.so
Can't load library: /home/jenkins/.swt/lib/linux/x86/libswt-pi-gtk.so
/home/jenkins/.swt/lib/linux/x86/libswt-pi-gtk-4335.so:
libgtk-x11-2.0.so.0: cannot open shared object file: No such file or directory
at org.eclipse.swt.internal.Library.loadLibrary(Library.java:331)
at org.eclipse.swt.internal.Library.loadLibrary(Library.java:240)
at org.eclipse.swt.internal.gtk.OS.clinit(OS.java:45)
at org.eclipse.swt.internal.Converter.wcsToMbcs(Converter.java:63)
at org.eclipse.swt.internal.Converter.wcsToMbcs(Converter.java:54)
at org.eclipse.swt.widgets.Display.clinit(Display.java:133)
at org.eclipse.ui.internal.Workbench.createDisplay(Workbench.java:683)
at org.eclipse.ui.PlatformUI.createDisplay(PlatformUI.java:162)
at
org.eclipse.ui.internal.ide.application.IDEApplication.createDisplay(IDEApplication.java:154)
at
org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:96)
at
org.eclipse.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31)
at
org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:114)
at
org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37)
at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
{noformat}
Enable the eclipse-based tests on builds.apache.org
---
Key: SLING-3782
URL: https://issues.apache.org/jira/browse/SLING-3782
Project: Sling
Issue Type: Test
Components: IDE, Testing
Reporter: Robert Munteanu
Fix For: Sling Eclipse IDE 1.0.4
Last time I checked we were unable to run the UI tests on Jenkins since the
slaves are headless and we need something like xvnc running.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Assigned] (SLING-3782) Enable the eclipse-based tests on builds.apache.org
[ https://issues.apache.org/jira/browse/SLING-3782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu reassigned SLING-3782: -- Assignee: Robert Munteanu Enable the eclipse-based tests on builds.apache.org --- Key: SLING-3782 URL: https://issues.apache.org/jira/browse/SLING-3782 Project: Sling Issue Type: Test Components: IDE, Testing Reporter: Robert Munteanu Assignee: Robert Munteanu Fix For: Sling Eclipse IDE 1.0.4 Last time I checked we were unable to run the UI tests on Jenkins since the slaves are headless and we need something like xvnc running. -- This message was sent by Atlassian JIRA (v6.2#6252)
Re: Launchpad 7 Release?
On Tuesday 22 July 2014 13:30:59 Bertrand Delacretaz wrote: On Tue, Jul 22, 2014 at 12:20 PM, Oliver Lietz apa...@oliverlietz.de wrote: ...My goals for a first *Karaf* Launchpad release are a current released JCR Server (whether Jackrabbit or Oak) and getting the Event bundle fixed (not sure what's the cause for a failing IT yet) Are you planning to setup integration tests for that Karaf-based launcher? Sure. There are already basic bootstrap tests which check if the required bundles are available and active in org.apache.sling.launchpad.karaf- integration-tests and also some extended tests which check for services and nodes in the repository. And there is sling-tests on GitHub. If we can provide that (at http://ci.apache.org/ as well) it lets users decide which launcher they want to use, knowing that all our tests pass when that launcher is used. I will have a look when back from holidays. Regards, O. -Bertrand
RE: Launchpad 7 Release?
On Tue, 2014-07-22 at 15:30 +0200, Carsten Ziegeler wrote: Looking at the snapshot list of the builder project, I guess we could just release all of them and we're got with Sling 7 and then maybe have a look at how to change things after Sling 7? +1, I think it's important to have a Sling 7 release soon. It's going to be fun though, we have a large number of releases to perform :-) $ grep -c -e SNAPSHOT src/main/bundles/list.xml 20 Robert +1 for a speedy Sling 7 release and discuss how to increase the frequency of future Launchpad releases after the Sling 7 release. Best regards mike
Re: Launchpad 7 Release?
On Tuesday 22 July 2014 20:49:45 Robert Munteanu wrote: On Tue, 2014-07-22 at 15:30 +0200, Carsten Ziegeler wrote: Looking at the snapshot list of the builder project, I guess we could just release all of them and we're got with Sling 7 and then maybe have a look at how to change things after Sling 7? +1, I think it's important to have a Sling 7 release soon. Yes, but not a half-baked one. We would have even more users complainig about 7 as we now have with 6. It's going to be fun though, we have a large number of releases to perform :-) $ grep -c -e SNAPSHOT src/main/bundles/list.xml 20 As said before... I haven't checked the SNAPSHOT bundles, but I think there are some bundles where nothing changed after their latest release so we may use some already released bundles and not release *all* now. there are probaly less than 20 bundles. Regards, O. Robert
[jira] [Commented] (SLING-3618) Unable to create node at /var/discovery error in sling trunk
[ https://issues.apache.org/jira/browse/SLING-3618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14070974#comment-14070974 ] Deke Smith commented on SLING-3618: --- The /var node is created as nt:folder by org.apache.sling.jcr.classloader.internal.ClassLoaderWriterImpl within private synchronized boolean mkdirs(final Session session, final String path) org.apache.sling.discovery.impl.common.heartbeat.HeartbeatHandler is using org.apache.sling.discovery.impl.common.resource.ResourceHelper to create the discovery node under /var as nt:unstructured. Unable to create node at /var/discovery error in sling trunk Key: SLING-3618 URL: https://issues.apache.org/jira/browse/SLING-3618 Project: Sling Issue Type: Bug Components: Extensions Environment: All Reporter: Yogesh Upadhyay Fix For: Discovery Impl 1.0.10 Getting following error after using trunk version of jar 29.05.2014 23:13:15.980 *ERROR* [Apache Sling JCR Resource Event Queue Processor for path '/'] org.apache.sling.discovery.impl [org.apache.sling.discovery.impl.DiscoveryServiceImpl(52)] The activate method has thrown an exception (java.lang.RuntimeException: Exception while talking to repository (org.apache.sling.api.resource.PersistenceException: Unable to create node at /var/discovery)) java.lang.RuntimeException: Exception while talking to repository (org.apache.sling.api.resource.PersistenceException: Unable to create node at /var/discovery) at org.apache.sling.discovery.impl.topology.announcement.AnnouncementRegistryImpl.listAnnouncementsInSameCluster(AnnouncementRegistryImpl.java:204) at org.apache.sling.discovery.impl.topology.announcement.AnnouncementRegistryImpl.listInstances(AnnouncementRegistryImpl.java:487) at org.apache.sling.discovery.impl.DiscoveryServiceImpl.getTopology(DiscoveryServiceImpl.java:423) at org.apache.sling.discovery.impl.DiscoveryServiceImpl.activate(DiscoveryServiceImpl.java:145) at sun.reflect.GeneratedMethodAccessor40.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.apache.felix.scr.impl.helper.BaseMethod.invokeMethod(BaseMethod.java:231) at org.apache.felix.scr.impl.helper.BaseMethod.access$500(BaseMethod.java:39) at org.apache.felix.scr.impl.helper.BaseMethod$Resolved.invoke(BaseMethod.java:624) at org.apache.felix.scr.impl.helper.BaseMethod.invoke(BaseMethod.java:508) at org.apache.felix.scr.impl.helper.ActivateMethod.invoke(ActivateMethod.java:149) at org.apache.felix.scr.impl.manager.SingleComponentManager.createImplementationObject(SingleComponentManager.java:315) at org.apache.felix.scr.impl.manager.SingleComponentManager.createComponent(SingleComponentManager.java:127) at org.apache.felix.scr.impl.manager.SingleComponentManager.getService(SingleComponentManager.java:871) at org.apache.felix.scr.impl.manager.SingleComponentManager.getServiceInternal(SingleComponentManager.java:838) at org.apache.felix.scr.impl.manager.SingleComponentManager.getService(SingleComponentManager.java:777) at org.apache.felix.framework.ServiceRegistrationImpl.getFactoryUnchecked(ServiceRegistrationImpl.java:320) at org.apache.felix.framework.ServiceRegistrationImpl.getService(ServiceRegistrationImpl.java:231) at org.apache.felix.framework.ServiceRegistry.getService(ServiceRegistry.java:327) at org.apache.felix.framework.Felix.getService(Felix.java:3574) at org.apache.felix.framework.BundleContextImpl.getService(BundleContextImpl.java:468) at org.apache.felix.scr.impl.helper.BindMethod.getServiceObject(BindMethod.java:572) at org.apache.felix.scr.impl.manager.DependencyManager.getServiceObject(DependencyManager.java:2012) at org.apache.felix.scr.impl.manager.DependencyManager$SingleStaticCustomizer.prebind(DependencyManager.java:1005) at org.apache.felix.scr.impl.manager.DependencyManager.prebind(DependencyManager.java:1439) at org.apache.felix.scr.impl.manager.AbstractComponentManager.collectDependencies(AbstractComponentManager.java:1119) at org.apache.felix.scr.impl.manager.SingleComponentManager.getServiceInternal(SingleComponentManager.java:807) at org.apache.felix.scr.impl.manager.SingleComponentManager.getService(SingleComponentManager.java:777) at org.apache.felix.framework.ServiceRegistrationImpl.getFactoryUnchecked(ServiceRegistrationImpl.java:320) at org.apache.felix.framework.ServiceRegistrationImpl.getService(ServiceRegistrationImpl.java:231) at
