[jira] [Created] (SLING-5662) Maven license report extracted URLs are 404
Bruce Edge created SLING-5662: - Summary: Maven license report extracted URLs are 404 Key: SLING-5662 URL: https://issues.apache.org/jira/browse/SLING-5662 Project: Sling Issue Type: Bug Components: Distribution Reporter: Bruce Edge Priority: Trivial The maven license plugin that extracts licenses from 3rd party components: org.codehaus.mojo license-maven-plugin 1.8 The extracted URLs for all of the sling components all 404. (The Apache Software License, Version 2.0) Apache Sling API (org.apache.sling:org.apache.sling.api:2.4.2 - http://sling.apache.org/org.apache.sling.api) (The Apache Software License, Version 2.0) Apache Sling Commons OSGi support (org.apache.sling:org.apache.sling.commons.osgi:2.2.2 - http://sling.apache.org/org.apache.sling.commons.osgi) (The Apache Software License, Version 2.0) Apache Sling Event Support (org.apache.sling:org.apache.sling.event:3.3.0 - http://sling.apache.org/org.apache.sling.event) (The Apache Software License, Version 2.0) Apache Sling Wrapper Bundle for the JCR API (org.apache.sling:org.apache.sling.jcr.jcr-wrapper:2.0.0 - http://sling.apache.org/org.apache.sling.jcr.jcr-wrapper) (The Apache Software License, Version 2.0) Apache Sling Query (org.apache.sling:org.apache.sling.query:3.0.0 - http://sling.apache.org/org.apache.sling.query) (The Apache Software License, Version 2.0) Apache Sling Default POST Servlets (org.apache.sling:org.apache.sling.servlets.post:2.3.6 - http://sling.apache.org/org.apache.sling.servlets.post) The same is true for all of the felix & jackrabbit components. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-4223) Make Content Loader extensible to support new import formats
[
https://issues.apache.org/jira/browse/SLING-4223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14379774#comment-14379774
]
Bruce Edge commented on SLING-4223:
---
Either approach works for me. I'm all for KISS in theory, so I assume there's
some use case addressed by the additional inheritance in the BaseContentReader
as opposed to the original whiteboard approach.
Make Content Loader extensible to support new import formats
Key: SLING-4223
URL: https://issues.apache.org/jira/browse/SLING-4223
Project: Sling
Issue Type: Improvement
Components: JCR
Affects Versions: JCR ContentLoader 2.1.10
Reporter: Oliver Lietz
Assignee: Tomek Rękawek
Fix For: JCR ContentLoader 2.2.0
Attachments: SLING-4223.patch
The current Content Loader supports a basic set of import formats which are
identified by extension: {{.xml}}, {{.jcr.xml}}, {{.json}}, {{.jar}} and
{{.zip}}.
There is a [user
request|http://mail-archives.apache.org/mod_mbox/sling-users/201412.mbox/%3cd0a6198c.20fbeb%25bruce.e...@nextissuemedia.com%3e]
to support custom formats like Adobe Folio and [some ideas how to
implement|http://mail-archives.apache.org/mod_mbox/sling-users/201412.mbox/%3ca2ab572f-fa83-4ae2-806e-49cce87b9...@adobe.com%3e]:
* we create a new org.apache.sling.contentloader.reader package to be
exported at version 1.0
* move the ContentCreator (@ProviderType) and ContentReader (@ConsumerType)
to that new package
* convert the BaseImportLoader into a standalone ContentReader service holder
used by the DefaultContentImporter and ContentLoaderService components.
* For the ContentReader service interface we define service registration
properties for the service to expose the file name extension (and maybe
content type) the reader supports.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SLING-4517) Update debian packaging to use crankstart.
[ https://issues.apache.org/jira/browse/SLING-4517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14380317#comment-14380317 ] Bruce Edge commented on SLING-4517: --- OK, thanks. Ignore the patch, will resubmit as a pull request. Update debian packaging to use crankstart. -- Key: SLING-4517 URL: https://issues.apache.org/jira/browse/SLING-4517 Project: Sling Issue Type: Bug Components: Crankstart Affects Versions: Launchpad Builder 8 Reporter: Bruce Edge Priority: Minor Attachments: sling-patch.diff The current debian packaging is launchpad based. This is OK for simple getting started configurations, but falls short of an end-user customizable solution that allows full configurability within the bounds of a pre-packaged env. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-4517) Update debian packaging to use crankstart.
[ https://issues.apache.org/jira/browse/SLING-4517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Edge updated SLING-4517: -- Attachment: sling-patch.diff Patch switches debian packaging over to using crankstart and sling-s3 contrib projects. Allows user to install a generic sling server, then edit one config file to select one of: - tar files for nodes and data - tar files for nodes, s3 for data - mongo for nodes and data - mongo for nodes, s3 for data Update debian packaging to use crankstart. -- Key: SLING-4517 URL: https://issues.apache.org/jira/browse/SLING-4517 Project: Sling Issue Type: Bug Components: Crankstart Affects Versions: Launchpad Builder 8 Reporter: Bruce Edge Priority: Minor Attachments: sling-patch.diff The current debian packaging is launchpad based. This is OK for simple getting started configurations, but falls short of an end-user customizable solution that allows full configurability within the bounds of a pre-packaged env. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-4517) Update debian packaging to use crankstart.
[ https://issues.apache.org/jira/browse/SLING-4517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14378932#comment-14378932 ] Bruce Edge commented on SLING-4517: --- Changed the artifact package name from sling-launchpad to sling-server to avoid colliding with other existing maven project names. Installation: % sudo dpkg -i sling-server_8~SNAPSHOT_all.deb Selecting previously unselected package sling-server. (Reading database ... 280095 files and directories currently installed.) Preparing to unpack .../sling-server_8~SNAPSHOT_all.deb ... Unpacking sling-server (8~SNAPSHOT) ... Setting up sling-server (8~SNAPSHOT) ... /var/lib/dpkg/info/sling-server.postinst configure Fix type of /var/lib/sling Update ownership of /opt/sling Update ownership of /etc/sling Fix type of /var/log/sling Adding system startup for /etc/init.d/sling ... /etc/rc0.d/K20sling - ../init.d/sling /etc/rc1.d/K20sling - ../init.d/sling /etc/rc6.d/K20sling - ../init.d/sling /etc/rc2.d/S20sling - ../init.d/sling /etc/rc3.d/S20sling - ../init.d/sling /etc/rc4.d/S20sling - ../init.d/sling /etc/rc5.d/S20sling - ../init.d/sling * is not running Processing triggers for ureadahead (0.100.0-16) ... Start in local config: %sudo service sling start * Starting sling serices /opt/sling/scripts/generate_crankfile.sh target/crank.txt * is running ...done. Start in s3 mode: %sudo service sling start * Starting sling serices /opt/sling/scripts/generate_crankfile.sh s3 target/crank-s3.txt * is running ...done. Thanks Tomasz for all the help. Update debian packaging to use crankstart. -- Key: SLING-4517 URL: https://issues.apache.org/jira/browse/SLING-4517 Project: Sling Issue Type: Bug Components: Crankstart Affects Versions: Launchpad Builder 8 Reporter: Bruce Edge Priority: Minor Attachments: sling-patch.diff The current debian packaging is launchpad based. This is OK for simple getting started configurations, but falls short of an end-user customizable solution that allows full configurability within the bounds of a pre-packaged env. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SLING-4517) Update debian packaging to use crankstart.
[ https://issues.apache.org/jira/browse/SLING-4517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Edge resolved SLING-4517. --- Resolution: Implemented Can resolve when merged. Update debian packaging to use crankstart. -- Key: SLING-4517 URL: https://issues.apache.org/jira/browse/SLING-4517 Project: Sling Issue Type: Bug Components: Crankstart Affects Versions: Launchpad Builder 8 Reporter: Bruce Edge Priority: Minor Attachments: sling-patch.diff The current debian packaging is launchpad based. This is OK for simple getting started configurations, but falls short of an end-user customizable solution that allows full configurability within the bounds of a pre-packaged env. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-4223) Make Content Loader extensible to support new import formats
[
https://issues.apache.org/jira/browse/SLING-4223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14372529#comment-14372529
]
Bruce Edge commented on SLING-4223:
---
I can see the advantage of the service ranking.
However, I get errors trying to co from the svn URLs above to review, what's
the trick to pulling down from there?
svn: E195019: Redirect cycle detected for URL
'http://svn.apache.org/viewvc/sling/whiteboard/olli/contentloader'
Make Content Loader extensible to support new import formats
Key: SLING-4223
URL: https://issues.apache.org/jira/browse/SLING-4223
Project: Sling
Issue Type: Improvement
Components: JCR
Affects Versions: JCR ContentLoader 2.1.10
Reporter: Oliver Lietz
Assignee: Tomek Rękawek
Fix For: JCR ContentLoader 2.2.0
Attachments: SLING-4223.patch
The current Content Loader supports a basic set of import formats which are
identified by extension: {{.xml}}, {{.jcr.xml}}, {{.json}}, {{.jar}} and
{{.zip}}.
There is a [user
request|http://mail-archives.apache.org/mod_mbox/sling-users/201412.mbox/%3cd0a6198c.20fbeb%25bruce.e...@nextissuemedia.com%3e]
to support custom formats like Adobe Folio and [some ideas how to
implement|http://mail-archives.apache.org/mod_mbox/sling-users/201412.mbox/%3ca2ab572f-fa83-4ae2-806e-49cce87b9...@adobe.com%3e]:
* we create a new org.apache.sling.contentloader.reader package to be
exported at version 1.0
* move the ContentCreator (@ProviderType) and ContentReader (@ConsumerType)
to that new package
* convert the BaseImportLoader into a standalone ContentReader service holder
used by the DefaultContentImporter and ContentLoaderService components.
* For the ContentReader service interface we define service registration
properties for the service to expose the file name extension (and maybe
content type) the reader supports.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (SLING-4517) Update debian packaging to use crankstart.
Bruce Edge created SLING-4517: - Summary: Update debian packaging to use crankstart. Key: SLING-4517 URL: https://issues.apache.org/jira/browse/SLING-4517 Project: Sling Issue Type: Bug Components: Crankstart Affects Versions: Launchpad Builder 8 Reporter: Bruce Edge Priority: Minor The current debian packaging is launchpad based. This is OK for simple getting started configurations, but falls short of an end-user customizable solution that allows full configurability within the bounds of a pre-packaged env. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-4517) Update debian packaging to use crankstart.
[ https://issues.apache.org/jira/browse/SLING-4517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14368200#comment-14368200 ] Bruce Edge commented on SLING-4517: --- Currently working on this. Will have patch soon. Update debian packaging to use crankstart. -- Key: SLING-4517 URL: https://issues.apache.org/jira/browse/SLING-4517 Project: Sling Issue Type: Bug Components: Crankstart Affects Versions: Launchpad Builder 8 Reporter: Bruce Edge Priority: Minor The current debian packaging is launchpad based. This is OK for simple getting started configurations, but falls short of an end-user customizable solution that allows full configurability within the bounds of a pre-packaged env. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-4223) make Content Loader extensible to support new import formats
[
https://issues.apache.org/jira/browse/SLING-4223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14338727#comment-14338727
]
Bruce Edge commented on SLING-4223:
---
Is this feature on anyone's road map?
This is highly desirable for our application as it allows the use of all
existing input channels without having to write a content-specific handler for
each one.
make Content Loader extensible to support new import formats
Key: SLING-4223
URL: https://issues.apache.org/jira/browse/SLING-4223
Project: Sling
Issue Type: Improvement
Components: JCR
Affects Versions: JCR ContentLoader 2.1.10
Reporter: Oliver Lietz
Fix For: JCR ContentLoader 2.2.0
The current Content Loader supports a basic set of import formats which are
identified by extension: {{.xml}}, {{.jcr.xml}}, {{.json}}, {{.jar}} and
{{.zip}}.
There is a [user
request|http://mail-archives.apache.org/mod_mbox/sling-users/201412.mbox/%3cd0a6198c.20fbeb%25bruce.e...@nextissuemedia.com%3e]
to support custom formats like Adobe Folio and [some ideas how to
implement|http://mail-archives.apache.org/mod_mbox/sling-users/201412.mbox/%3ca2ab572f-fa83-4ae2-806e-49cce87b9...@adobe.com%3e]:
* we create a new org.apache.sling.contentloader.reader package to be
exported at version 1.0
* move the ContentCreator (@ProviderType) and ContentReader (@ConsumerType)
to that new package
* convert the BaseImportLoader into a standalone ContentReader service holder
used by the DefaultContentImporter and ContentLoaderService components.
* For the ContentReader service interface we define service registration
properties for the service to expose the file name extension (and maybe
content type) the reader supports.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (SLING-4328) Loading gogo.shell in launchpad fails kills felix framework, won't restart.
[ https://issues.apache.org/jira/browse/SLING-4328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Edge resolved SLING-4328. --- Resolution: Duplicate Marking this a duplicate of a gogo shell bug as IMO the shell should not terminate the felix runtime if stdout is not available. Loading gogo.shell in launchpad fails kills felix framework, won't restart. - Key: SLING-4328 URL: https://issues.apache.org/jira/browse/SLING-4328 Project: Sling Issue Type: Bug Components: Console Affects Versions: Launchpad Builder 8 Environment: Ubuntu 14.04 java version 1.7.0_72 Java(TM) SE Runtime Environment (build 1.7.0_72-b14) Java HotSpot(TM) 64-Bit Server VM (build 24.72-b04, mixed mode) Reporter: Bruce Edge Attachments: gogo.log.zip I’m having trouble loading the gogo shell in a default launchpad config. I’m assuming I just need org.apache.felix.gogo.shell and it’s dependencies, which I can find in the with the default OBR config. Using a fresh launchpad installation built from trunk a few days ago, the OBR console search for gogo [1] shows: Resource Name Installed Version Apache Felix Gogo Command (org.apache.felix.gogo.command) Apache Felix Gogo Runtime (org.apache.felix.gogo.runtime) Apache Felix Gogo Shell (org.apache.felix.gogo.shell) 0.10.0 0.6.0 0.6.1 0.8.0 Apache Felix Gogo Shell Commands (org.apache.felix.gogo.commands) Apache Felix Gogo Shell Console (org.apache.felix.gogo.console) Apache Felix Gogo Shell Launcher (org.apache.felix.gogo.launcher) Apache Felix iPOJO Gogo Command (org.apache.felix.ipojo.arch.gogo) I select version 0.10.0 and check deploy optional dependencies” and click on “deploy and start”. In the logs it shows the gogo shell loading starting, but then I get a [FelixShutdown] org.apache.felix.framework BundleEvent STOPPING and everything shuts down: 16.01.2015 12:54:42.335 *INFO* [OBR Bundle Deployer (Apache Felix API)] groovy-all BundleEvent INSTALLED 16.01.2015 12:54:42.392 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.gogo.shell BundleEvent INSTALLED 16.01.2015 12:54:42.406 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.gogo.runtime BundleEvent RESOLVED 16.01.2015 12:54:42.423 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.gogo.runtime BundleEvent STARTING 16.01.2015 12:54:42.444 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.gogo.runtime Service [292] ServiceEvent REGISTERED 16.01.2015 12:54:42.461 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.gogo.runtime Service [293] ServiceEvent REGISTERED 16.01.2015 12:54:42.474 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.gogo.runtime BundleEvent STARTED 16.01.2015 12:54:42.480 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.shell BundleEvent RESOLVED 16.01.2015 12:54:42.492 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.shell BundleEvent STARTING 16.01.2015 12:54:42.532 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.sling.settings Service [Apache Sling Sling Run Mode Shell Command,295] ServiceEvent REGISTERED 16.01.2015 12:54:42.541 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.shell Service [294] ServiceEvent REGISTERED 16.01.2015 12:54:42.558 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.shell Service [296] ServiceEvent REGISTERED 16.01.2015 12:54:42.580 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.shell Service [297] ServiceEvent REGISTERED 16.01.2015 12:54:42.594 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.shell Service [298] ServiceEvent REGISTERED 16.01.2015 12:54:42.598 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.shell Service [299] ServiceEvent REGISTERED 16.01.2015 12:54:42.601 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.shell Service [300] ServiceEvent REGISTERED 16.01.2015 12:54:42.612 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.shell Service [301] ServiceEvent REGISTERED 16.01.2015 12:54:42.643 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.shell Service [302] ServiceEvent REGISTERED 16.01.2015 12:54:42.655 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.shell Service [303] ServiceEvent REGISTERED 16.01.2015 12:54:42.656 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.shell Service [304] ServiceEvent REGISTERED 16.01.2015 12:54:42.663 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.shell Service [305] ServiceEvent REGISTERED 16.01.2015 12:54:42.686 *INFO* [OBR
[jira] [Commented] (SLING-4318) Sling resource API does not expose any versioning features - bounty offered.
[ https://issues.apache.org/jira/browse/SLING-4318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14282811#comment-14282811 ] Bruce Edge commented on SLING-4318: --- After re-reading the activities vs labels docs in the JCS 2.0 spec, I agree, there's no need for activities in the sling versioning API as their intended use is as a merge scope handle. My original thought was that an activity would be a mechanism to obtain the difference between version labels thereby negating the need for the client to calculate the set of changes between labels. Sling resource API does not expose any versioning features - bounty offered. Key: SLING-4318 URL: https://issues.apache.org/jira/browse/SLING-4318 Project: Sling Issue Type: New Feature Components: Documentation, JCR, Servlets Affects Versions: Servlets Resolver 2.3.8 Environment: N/A Reporter: Bruce Edge Labels: api, crud, servlet-api, versioning, versions The javax.jcr.version.VersionManager is not exposed in the sling resource API: http://thread.gmane.org/gmane.comp.apache.sling.user/1610 My company is interested in paying for this development. Please contact if interested. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-4328) Loading gogo.shell in launchpad fails kills felix framework, won't restart.
[
https://issues.apache.org/jira/browse/SLING-4328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14282013#comment-14282013
]
Bruce Edge commented on SLING-4328:
---
This is a documentation problem.
I found a thread discussing gogo shell defaulting to opening a console on
stdout [1].
The resolution for this problem was to add
{code}
-Dgosh.args=--nointeractive
{code}
to the JVM args
Adding this arg to the JVM fixes the above problem. I can start the shell and
connect on port .
The docs [2] should be updated to reflect the requirement for this JVM arg if
the gogo shell is desired.
I'm leaving this open as I can't update the docs.
[1]
http://apache-felix.18485.x6.nabble.com/Gogo-shell-on-standard-input-output-streams-td4845969.html#a4845970
[2] http://felix.apache.org/site/apache-felix-remote-shell.html
Loading gogo.shell in launchpad fails kills felix framework, won't restart.
-
Key: SLING-4328
URL: https://issues.apache.org/jira/browse/SLING-4328
Project: Sling
Issue Type: Bug
Components: Console
Affects Versions: Launchpad Builder 8
Environment: Ubuntu 14.04
java version 1.7.0_72
Java(TM) SE Runtime Environment (build 1.7.0_72-b14)
Java HotSpot(TM) 64-Bit Server VM (build 24.72-b04, mixed mode)
Reporter: Bruce Edge
Attachments: gogo.log.zip
I’m having trouble loading the gogo shell in a default launchpad config.
I’m assuming I just need org.apache.felix.gogo.shell and it’s dependencies,
which I can find in the with the default OBR config.
Using a fresh launchpad installation built from trunk a few days ago, the OBR
console search for gogo [1] shows:
Resource Name Installed Version
Apache Felix Gogo Command (org.apache.felix.gogo.command)
Apache Felix Gogo Runtime (org.apache.felix.gogo.runtime)
Apache Felix Gogo Shell (org.apache.felix.gogo.shell)
0.10.0
0.6.0
0.6.1
0.8.0
Apache Felix Gogo Shell Commands (org.apache.felix.gogo.commands)
Apache Felix Gogo Shell Console (org.apache.felix.gogo.console)
Apache Felix Gogo Shell Launcher (org.apache.felix.gogo.launcher)
Apache Felix iPOJO Gogo Command (org.apache.felix.ipojo.arch.gogo)
I select version 0.10.0 and check deploy optional dependencies” and click on
“deploy and start”.
In the logs it shows the gogo shell loading starting, but then I get a
[FelixShutdown] org.apache.felix.framework BundleEvent STOPPING
and everything shuts down:
16.01.2015 12:54:42.335 *INFO* [OBR Bundle Deployer (Apache Felix API)]
groovy-all BundleEvent INSTALLED
16.01.2015 12:54:42.392 *INFO* [OBR Bundle Deployer (Apache Felix API)]
org.apache.felix.gogo.shell BundleEvent INSTALLED
16.01.2015 12:54:42.406 *INFO* [OBR Bundle Deployer (Apache Felix API)]
org.apache.felix.gogo.runtime BundleEvent RESOLVED
16.01.2015 12:54:42.423 *INFO* [OBR Bundle Deployer (Apache Felix API)]
org.apache.felix.gogo.runtime BundleEvent STARTING
16.01.2015 12:54:42.444 *INFO* [OBR Bundle Deployer (Apache Felix API)]
org.apache.felix.gogo.runtime Service [292] ServiceEvent REGISTERED
16.01.2015 12:54:42.461 *INFO* [OBR Bundle Deployer (Apache Felix API)]
org.apache.felix.gogo.runtime Service [293] ServiceEvent REGISTERED
16.01.2015 12:54:42.474 *INFO* [OBR Bundle Deployer (Apache Felix API)]
org.apache.felix.gogo.runtime BundleEvent STARTED
16.01.2015 12:54:42.480 *INFO* [OBR Bundle Deployer (Apache Felix API)]
org.apache.felix.shell BundleEvent RESOLVED
16.01.2015 12:54:42.492 *INFO* [OBR Bundle Deployer (Apache Felix API)]
org.apache.felix.shell BundleEvent STARTING
16.01.2015 12:54:42.532 *INFO* [OBR Bundle Deployer (Apache Felix API)]
org.apache.sling.settings Service [Apache Sling Sling Run Mode Shell
Command,295] ServiceEvent REGISTERED
16.01.2015 12:54:42.541 *INFO* [OBR Bundle Deployer (Apache Felix API)]
org.apache.felix.shell Service [294] ServiceEvent REGISTERED
16.01.2015 12:54:42.558 *INFO* [OBR Bundle Deployer (Apache Felix API)]
org.apache.felix.shell Service [296] ServiceEvent REGISTERED
16.01.2015 12:54:42.580 *INFO* [OBR Bundle Deployer (Apache Felix API)]
org.apache.felix.shell Service [297] ServiceEvent REGISTERED
16.01.2015 12:54:42.594 *INFO* [OBR Bundle Deployer (Apache Felix API)]
org.apache.felix.shell Service [298] ServiceEvent REGISTERED
16.01.2015 12:54:42.598 *INFO* [OBR Bundle Deployer (Apache Felix API)]
org.apache.felix.shell Service [299] ServiceEvent REGISTERED
16.01.2015 12:54:42.601 *INFO* [OBR Bundle Deployer (Apache Felix API)]
org.apache.felix.shell Service [300] ServiceEvent REGISTERED
16.01.2015 12:54:42.612 *INFO* [OBR Bundle Deployer (Apache Felix API)]
org.apache.felix.shell Service [301] ServiceEvent REGISTERED
16.01.2015 12:54:42.643
[jira] [Updated] (SLING-4328) Loading gogo.shell in launchpad fails kills felix framework, won't restart.
[ https://issues.apache.org/jira/browse/SLING-4328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Edge updated SLING-4328: -- Attachment: gogo.log.zip Attaching log file with debug level enabled for 8 seconds after gogo shell is started from OSGi console. (Note, it loads OK, the fun starts when I try to run it) There's a number of concurrent access exceptions: org.apache.jackrabbit.core.session.SessionState Attempt to perform item.getPath() while another thread is concurrently reading from session-system-2. Blocking until the other thread is finished using this session. Please review your code to avoid concurrent use of a session. java.lang.Exception: Stack trace of concurrent access to session-system-2 ending with the following: 17.01.2015 13:30:36.016 *DEBUG* [OsgiInstallerImpl] org.apache.sling.installer.core.impl.OsgiInstallerImpl cleanupInstallableResources returns false 17.01.2015 13:30:36.016 *DEBUG* [OsgiInstallerImpl] org.apache.sling.installer.core.impl.OsgiInstallerImpl No more tasks to process, suspending listener and going idle 17.01.2015 13:30:36.016 *DEBUG* [OsgiInstallerImpl] org.apache.sling.installer.core.impl.OsgiInstallerImpl onEvent(SUSPENDED). 17.01.2015 13:30:36.016 *DEBUG* [OsgiInstallerImpl] org.apache.sling.installer.core.impl.OsgiInstallerImpl wait() on resourcesLock 17.01.2015 13:30:36.128 *INFO* [FelixShutdown] org.apache.felix.framework BundleEvent STOPPING 17.01.2015 13:30:36.129 *INFO* [FelixStartLevel] org.apache.felix.gogo.shell BundleEvent STOPPING Loading gogo.shell in launchpad fails kills felix framework, won't restart. - Key: SLING-4328 URL: https://issues.apache.org/jira/browse/SLING-4328 Project: Sling Issue Type: Bug Components: Console Affects Versions: Launchpad Builder 8 Environment: Ubuntu 14.04 java version 1.7.0_72 Java(TM) SE Runtime Environment (build 1.7.0_72-b14) Java HotSpot(TM) 64-Bit Server VM (build 24.72-b04, mixed mode) Reporter: Bruce Edge Attachments: gogo.log.zip I’m having trouble loading the gogo shell in a default launchpad config. I’m assuming I just need org.apache.felix.gogo.shell and it’s dependencies, which I can find in the with the default OBR config. Using a fresh launchpad installation built from trunk a few days ago, the OBR console search for gogo [1] shows: Resource Name Installed Version Apache Felix Gogo Command (org.apache.felix.gogo.command) Apache Felix Gogo Runtime (org.apache.felix.gogo.runtime) Apache Felix Gogo Shell (org.apache.felix.gogo.shell) 0.10.0 0.6.0 0.6.1 0.8.0 Apache Felix Gogo Shell Commands (org.apache.felix.gogo.commands) Apache Felix Gogo Shell Console (org.apache.felix.gogo.console) Apache Felix Gogo Shell Launcher (org.apache.felix.gogo.launcher) Apache Felix iPOJO Gogo Command (org.apache.felix.ipojo.arch.gogo) I select version 0.10.0 and check deploy optional dependencies” and click on “deploy and start”. In the logs it shows the gogo shell loading starting, but then I get a [FelixShutdown] org.apache.felix.framework BundleEvent STOPPING and everything shuts down: 16.01.2015 12:54:42.335 *INFO* [OBR Bundle Deployer (Apache Felix API)] groovy-all BundleEvent INSTALLED 16.01.2015 12:54:42.392 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.gogo.shell BundleEvent INSTALLED 16.01.2015 12:54:42.406 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.gogo.runtime BundleEvent RESOLVED 16.01.2015 12:54:42.423 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.gogo.runtime BundleEvent STARTING 16.01.2015 12:54:42.444 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.gogo.runtime Service [292] ServiceEvent REGISTERED 16.01.2015 12:54:42.461 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.gogo.runtime Service [293] ServiceEvent REGISTERED 16.01.2015 12:54:42.474 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.gogo.runtime BundleEvent STARTED 16.01.2015 12:54:42.480 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.shell BundleEvent RESOLVED 16.01.2015 12:54:42.492 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.shell BundleEvent STARTING 16.01.2015 12:54:42.532 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.sling.settings Service [Apache Sling Sling Run Mode Shell Command,295] ServiceEvent REGISTERED 16.01.2015 12:54:42.541 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.shell Service [294] ServiceEvent REGISTERED 16.01.2015 12:54:42.558 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.shell Service [296] ServiceEvent REGISTERED 16.01.2015
[jira] [Updated] (SLING-4329) Viewing /libs from sling explorer creates continuous stack dumps
[
https://issues.apache.org/jira/browse/SLING-4329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Edge updated SLING-4329:
--
Attachment: error.log.zip
Full log
Viewing /libs from sling explorer creates continuous stack dumps
Key: SLING-4329
URL: https://issues.apache.org/jira/browse/SLING-4329
Project: Sling
Issue Type: Bug
Components: ResourceResolver
Affects Versions: Launchpad Builder 8
Reporter: Bruce Edge
Priority: Trivial
Labels: explorer
Attachments: error.log.zip
Start a clean standalone.jar instance using:
{code}
/usr/bin/java -Xmx384M
-agentlib:jdwp=transport=dt_socket,address=30303,server=y,suspend=n -jar
/opt/sling/sling/org.apache.sling.launchpad-8-SNAPSHOT-standalone.jar -c
/var/lib/sling -p 8090 -a 0.0.0.0
{code}
then opening the explorer, http://localhost:8090/.explorer.html and clicking
on the /libs node creates an endless stream of exceptions in the sling log.
Full log attached.
Summary log, partial first frame:
{code}
17.01.2015 18:16:24.678 *INFO* [qtp786433993-45] logs/request.log
17/Jan/2015:18:16:24 -0800 [48] - GET /libs.explorer.node.html HTTP/1.1
17.01.2015 18:16:25.478 *ERROR* [10.0.2.2 [1421547384682] GET
/libs.explorer.node.html HTTP/1.1]
org.apache.sling.engine.impl.SlingRequestProcessorImpl service: Uncaught
SlingException
org.mozilla.javascript.WrappedException: Wrapped
org.apache.sling.api.scripting.ScriptEvaluationException: Failure running
script /libs/sling/servlet/default/explorer/node.esp: Wrapped
org.apache.sling.api.scripting.ScriptEvaluationException: Failure running
script /libs/sling
/servlet/default/explorer/node.esp: Wrapped
org.apache.sling.api.scripting.ScriptEvaluationException: Failure running
script /libs/sling/servlet/default/explorer/node.esp: Wrapped
org.apache.sling.api.scripting.ScriptEvaluationException: Failure running
script /libs/sling/serv
let/default/explorer/node.esp: Wrapped
org.apache.sling.api.scripting.ScriptEvaluationException: Failure running
script /libs/sling/servlet/default/explorer/node.esp: Wrapped
org.apache.sling.api.scripting.ScriptEvaluationException: Failure running
script /libs/sling/servlet/d
efault/explorer/node.esp: Wrapped
org.apache.sling.api.scripting.ScriptEvaluationException: Failure running
script /libs/sling/servlet/default/explorer/node.esp: Wrapped
org.apache.sling.api.scripting.ScriptEvaluationException: Failure running
script /libs/sling/servlet/defaul
t/explorer/node.esp: Wrapped
org.apache.sling.api.scripting.ScriptEvaluationException: Failure running
script /libs/sling/servlet/default/explorer/node.esp: Wrapped
org.apache.sling.api.scripting.ScriptEvaluationException: Failure running
script /libs/sling/servlet/default/exp
lorer/node.esp: Wrapped
org.apache.sling.api.scripting.ScriptEvaluationException: Failure running
script /libs/sling/servlet/default/explorer/node.esp: Wrapped
org.apache.sling.api.scripting.ScriptEvaluationException: Failure running
script /libs/sling/servlet/default/explorer
/node.esp: Wrapped org.apache.sling.api.scripting.ScriptEvaluationException:
Failure running script /libs/sling/servlet/default/explorer/node.esp: Wrapped
org.apache.sling.api.scripting.ScriptEvaluationException: Failure running
script /libs/sling/servlet/default/explorer/node
.esp: Wrapped org.apache.sling.api.scripting.ScriptEvaluationException:
Failure running script /libs/sling/servlet/default/explorer/node.esp: Wrapped
org.apache.sling.api.scripting.ScriptEvaluationException: Failure running
script /libs/sling/servlet/default/explorer/node.esp:
Wrapped org.apache.sling.api.scripting.ScriptEvaluationException: Failure
running script /libs/sling/servlet/default/explorer/node.esp: Wrapped
org.apache.sling.api.scripting.ScriptEvaluationException: Failure running
script /libs/sling/servlet/default/explorer/node.esp: Wrap
ped org.apache.sling.api.scripting.ScriptEvaluationException: Failure running
script /libs/sling/servlet/default/explorer/node.esp: Wrapped
org.apache.sling.api.scripting.ScriptEvaluationException: Failure running
script /libs/sling/servlet/default/explorer/node.esp: Wrapped o
rg.apache.sling.api.scripting.ScriptEvaluationException: Failure running
script /libs/sling/servlet/default/explorer/node.esp: Wrapped
org.apache.sling.api.scripting.ScriptEvaluationException: Failure running
script /libs/sling/servlet/default/explorer/node.esp: Wrapped org.ap
ache.sling.api.scripting.ScriptEvaluationException: Failure running script
/libs/sling/servlet/default/explorer/node.esp: Wrapped
org.apache.sling.api.scripting.ScriptEvaluationException: Failure running
script /libs/sling/servlet/default/explorer/node.esp: Wrapped org.apache.
[jira] [Commented] (SLING-4318) Sling resource API does not expose any versioning features - bounty offered.
[ https://issues.apache.org/jira/browse/SLING-4318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14281658#comment-14281658 ] Bruce Edge commented on SLING-4318: --- Regarding the version content diff, agreed, that could be a client side implementation. Sling resource API does not expose any versioning features - bounty offered. Key: SLING-4318 URL: https://issues.apache.org/jira/browse/SLING-4318 Project: Sling Issue Type: New Feature Components: Documentation, JCR, Servlets Affects Versions: Servlets Resolver 2.3.8 Environment: N/A Reporter: Bruce Edge Labels: api, crud, servlet-api, versioning, versions The javax.jcr.version.VersionManager is not exposed in the sling resource API: http://thread.gmane.org/gmane.comp.apache.sling.user/1610 My company is interested in paying for this development. Please contact if interested. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SLING-4328) Loading gogo.shell in launchpad fails kills felix framework, won't restart.
Bruce Edge created SLING-4328: - Summary: Loading gogo.shell in launchpad fails kills felix framework, won't restart. Key: SLING-4328 URL: https://issues.apache.org/jira/browse/SLING-4328 Project: Sling Issue Type: Bug Components: Console Affects Versions: Launchpad Builder 8 Environment: Ubuntu 14.04 java version 1.7.0_72 Java(TM) SE Runtime Environment (build 1.7.0_72-b14) Java HotSpot(TM) 64-Bit Server VM (build 24.72-b04, mixed mode) Reporter: Bruce Edge I’m having trouble loading the gogo shell in a default launchpad config. I’m assuming I just need org.apache.felix.gogo.shell and it’s dependencies, which I can find in the with the default OBR config. Using a fresh launchpad installation built from trunk a few days ago, the OBR console search for gogo [1] shows: Resource Name Installed Version Apache Felix Gogo Command (org.apache.felix.gogo.command) Apache Felix Gogo Runtime (org.apache.felix.gogo.runtime) Apache Felix Gogo Shell (org.apache.felix.gogo.shell) 0.10.0 0.6.0 0.6.1 0.8.0 Apache Felix Gogo Shell Commands (org.apache.felix.gogo.commands) Apache Felix Gogo Shell Console (org.apache.felix.gogo.console) Apache Felix Gogo Shell Launcher (org.apache.felix.gogo.launcher) Apache Felix iPOJO Gogo Command (org.apache.felix.ipojo.arch.gogo) I select version 0.10.0 and check deploy optional dependencies” and click on “deploy and start”. In the logs it shows the gogo shell loading starting, but then I get a [FelixShutdown] org.apache.felix.framework BundleEvent STOPPING and everything shuts down: 16.01.2015 12:54:42.335 *INFO* [OBR Bundle Deployer (Apache Felix API)] groovy-all BundleEvent INSTALLED 16.01.2015 12:54:42.392 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.gogo.shell BundleEvent INSTALLED 16.01.2015 12:54:42.406 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.gogo.runtime BundleEvent RESOLVED 16.01.2015 12:54:42.423 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.gogo.runtime BundleEvent STARTING 16.01.2015 12:54:42.444 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.gogo.runtime Service [292] ServiceEvent REGISTERED 16.01.2015 12:54:42.461 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.gogo.runtime Service [293] ServiceEvent REGISTERED 16.01.2015 12:54:42.474 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.gogo.runtime BundleEvent STARTED 16.01.2015 12:54:42.480 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.shell BundleEvent RESOLVED 16.01.2015 12:54:42.492 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.shell BundleEvent STARTING 16.01.2015 12:54:42.532 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.sling.settings Service [Apache Sling Sling Run Mode Shell Command,295] ServiceEvent REGISTERED 16.01.2015 12:54:42.541 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.shell Service [294] ServiceEvent REGISTERED 16.01.2015 12:54:42.558 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.shell Service [296] ServiceEvent REGISTERED 16.01.2015 12:54:42.580 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.shell Service [297] ServiceEvent REGISTERED 16.01.2015 12:54:42.594 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.shell Service [298] ServiceEvent REGISTERED 16.01.2015 12:54:42.598 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.shell Service [299] ServiceEvent REGISTERED 16.01.2015 12:54:42.601 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.shell Service [300] ServiceEvent REGISTERED 16.01.2015 12:54:42.612 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.shell Service [301] ServiceEvent REGISTERED 16.01.2015 12:54:42.643 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.shell Service [302] ServiceEvent REGISTERED 16.01.2015 12:54:42.655 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.shell Service [303] ServiceEvent REGISTERED 16.01.2015 12:54:42.656 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.shell Service [304] ServiceEvent REGISTERED 16.01.2015 12:54:42.663 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.shell Service [305] ServiceEvent REGISTERED 16.01.2015 12:54:42.686 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.shell Service [306] ServiceEvent REGISTERED 16.01.2015 12:54:42.698 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.shell Service [307] ServiceEvent REGISTERED 16.01.2015 12:54:42.710 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.shell Service [308] ServiceEvent REGISTERED 16.01.2015 12:54:42.724 *INFO* [OBR Bundle Deployer (Apache Felix API)]
[jira] [Commented] (SLING-4318) Sling resource API does not expose any versioning features - bounty offered.
[ https://issues.apache.org/jira/browse/SLING-4318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14281006#comment-14281006 ] Bruce Edge commented on SLING-4318: --- Would it be possible to use nt:activity and/or nt:versionLabels as version specifiers for retrieving content as well as parameters to POST operations such that an automated operations that commit a large number of new files could create an activity and then pass the activity name and/or a versionLabel as parameters to all POST operations which would apply the activity and versionLabel to the JCR update? I expect this would add complexity to the API. Will defer to more experienced members as to whether this is viable. Any mechanism to group sets of changes as well as tag versions would be great. Another use case we have is to get a list of modified content between versions of a base node. Ideally we could get a json array of modified/new content in a tree branch specified by a base path and two versions specified by label. Again, open to suggestions, these are ideas carried over from other domains that may or may not map directly into the sling/JCR world. Sling resource API does not expose any versioning features - bounty offered. Key: SLING-4318 URL: https://issues.apache.org/jira/browse/SLING-4318 Project: Sling Issue Type: New Feature Components: Documentation, JCR, Servlets Affects Versions: Servlets Resolver 2.3.8 Environment: N/A Reporter: Bruce Edge Labels: api, crud, servlet-api, versioning, versions The javax.jcr.version.VersionManager is not exposed in the sling resource API: http://thread.gmane.org/gmane.comp.apache.sling.user/1610 My company is interested in paying for this development. Please contact if interested. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-4328) Loading gogo.shell in launchpad fails kills felix framework, won't restart.
[ https://issues.apache.org/jira/browse/SLING-4328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14281112#comment-14281112 ] Bruce Edge commented on SLING-4328: --- Working from Apache Felix Remote Shell [1], it doesn't seem to matter what version of the dependencies I choose from: org.apache.felix.shell org.apache.felix.shell.remote org.apache.felix.gogo.runtime Once I try to start any version of org.apache.felix.gogo.shell I see these 2 messages in succession: 16.01.2015 17:09:03.965 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.gogo.shell BundleEvent STARTED 16.01.2015 17:09:04.106 *INFO* [FelixShutdown] org.apache.felix.framework BundleEvent STOPPING and sling shuts down completely with basically the same log message as in the original post. The available options I have for the gogo shell are: Apache Felix Gogo Shell (org.apache.felix.gogo.shell) 0.10.0 0.6.0 0.6.1 0.8.0 All result in an immediate shutdown once I try start the gogo shell bundle. I did finally figure out that I can rm -rf the latest $SLING_HOME/felix/bundle* directory to restore operation. [1] http://felix.apache.org/site/apache-felix-remote-shell.html Loading gogo.shell in launchpad fails kills felix framework, won't restart. - Key: SLING-4328 URL: https://issues.apache.org/jira/browse/SLING-4328 Project: Sling Issue Type: Bug Components: Console Affects Versions: Launchpad Builder 8 Environment: Ubuntu 14.04 java version 1.7.0_72 Java(TM) SE Runtime Environment (build 1.7.0_72-b14) Java HotSpot(TM) 64-Bit Server VM (build 24.72-b04, mixed mode) Reporter: Bruce Edge I’m having trouble loading the gogo shell in a default launchpad config. I’m assuming I just need org.apache.felix.gogo.shell and it’s dependencies, which I can find in the with the default OBR config. Using a fresh launchpad installation built from trunk a few days ago, the OBR console search for gogo [1] shows: Resource Name Installed Version Apache Felix Gogo Command (org.apache.felix.gogo.command) Apache Felix Gogo Runtime (org.apache.felix.gogo.runtime) Apache Felix Gogo Shell (org.apache.felix.gogo.shell) 0.10.0 0.6.0 0.6.1 0.8.0 Apache Felix Gogo Shell Commands (org.apache.felix.gogo.commands) Apache Felix Gogo Shell Console (org.apache.felix.gogo.console) Apache Felix Gogo Shell Launcher (org.apache.felix.gogo.launcher) Apache Felix iPOJO Gogo Command (org.apache.felix.ipojo.arch.gogo) I select version 0.10.0 and check deploy optional dependencies” and click on “deploy and start”. In the logs it shows the gogo shell loading starting, but then I get a [FelixShutdown] org.apache.felix.framework BundleEvent STOPPING and everything shuts down: 16.01.2015 12:54:42.335 *INFO* [OBR Bundle Deployer (Apache Felix API)] groovy-all BundleEvent INSTALLED 16.01.2015 12:54:42.392 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.gogo.shell BundleEvent INSTALLED 16.01.2015 12:54:42.406 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.gogo.runtime BundleEvent RESOLVED 16.01.2015 12:54:42.423 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.gogo.runtime BundleEvent STARTING 16.01.2015 12:54:42.444 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.gogo.runtime Service [292] ServiceEvent REGISTERED 16.01.2015 12:54:42.461 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.gogo.runtime Service [293] ServiceEvent REGISTERED 16.01.2015 12:54:42.474 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.gogo.runtime BundleEvent STARTED 16.01.2015 12:54:42.480 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.shell BundleEvent RESOLVED 16.01.2015 12:54:42.492 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.shell BundleEvent STARTING 16.01.2015 12:54:42.532 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.sling.settings Service [Apache Sling Sling Run Mode Shell Command,295] ServiceEvent REGISTERED 16.01.2015 12:54:42.541 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.shell Service [294] ServiceEvent REGISTERED 16.01.2015 12:54:42.558 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.shell Service [296] ServiceEvent REGISTERED 16.01.2015 12:54:42.580 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.shell Service [297] ServiceEvent REGISTERED 16.01.2015 12:54:42.594 *INFO* [OBR Bundle Deployer (Apache Felix API)] org.apache.felix.shell Service [298] ServiceEvent REGISTERED 16.01.2015 12:54:42.598 *INFO* [OBR Bundle Deployer (Apache Felix API)]
[jira] [Created] (SLING-4318) Sling resource API does not expose any versioning features - bounty offered.
Bruce Edge created SLING-4318: - Summary: Sling resource API does not expose any versioning features - bounty offered. Key: SLING-4318 URL: https://issues.apache.org/jira/browse/SLING-4318 Project: Sling Issue Type: New Feature Components: Documentation, JCR, Servlets Affects Versions: Servlets Resolver 2.3.8 Environment: N/A Reporter: Bruce Edge The javax.jcr.version.VersionManager is not exposed in the sling resource API: http://thread.gmane.org/gmane.comp.apache.sling.user/1610 My company is interested in paying for this development. Please contact if interested. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SLING-4222) WebDAV and many javax.jcr.RepositoryException: not a token for an open-scoped JCR lock: opaquelocktoken exceptions
[
https://issues.apache.org/jira/browse/SLING-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Edge resolved SLING-4222.
---
Resolution: Not a Problem
Found the problem. It was the Linux WebDAV driver. Further experimentation from
the shell with a WebDAV mount showed flawless operation from OS X for a variety
of file sizes and load, while the Linux WebDAV driver (davfs2 version
1.4.6-1ubuntu3) mount exhibited the same problems I’ve been having from my OSGI
thread.
I tried switched from using davfs2, e.g.:
mount -t davfs -o gid=sling,rw,uid=sling,username=admin http://localhost:8090
/mnt/jcr
to using fusedav:
fusedav -p=admin -u=admin http://localhost:8090 /mnt/jcr
and the problems ceased, however the fusedav driver lacked many of the options
provided by davfs2. A bit more digging yielded a new davfs2 version based on
the new libneon27 WebDAV API [1]:
Installing the newer davfs2 package, 1.5.2-1, as well as disabling locks in
/etc/davfs2/davfs2.conf also fixed the problem. This is preferable to the
fusedav option as davfs2 has considerably more functionality and options than
fusedav.
WebDAV I/O is now reliable. Have been running load testing for hours now with
no errors.
[1] https://launchpad.net/ubuntu/+source/davfs2
WebDAV and many javax.jcr.RepositoryException: not a token for an open-scoped
JCR lock: opaquelocktoken exceptions
--
Key: SLING-4222
URL: https://issues.apache.org/jira/browse/SLING-4222
Project: Sling
Issue Type: Bug
Components: JCR
Affects Versions: Launchpad Builder 8
Environment: linux
Webdav mounted with davfs using:
{{
mount -t davfs -o gid=sling,rw,uid=sling,username=admin
http://localhost:8090 /mnt/jcr
% mount | grep 8090
http://localhost:8090 on /mnt/jcr type davfs
(rw,nosuid,nodev,_netdev,gid=999,uid=1009)
}}
Reporter: Bruce Edge
Labels: jcr, webdav
I'm importing content into the JCR default workspace using a combination of
sling:folder node creation in a JobConsumer from a bundle thread, then
extracting a zip at that target location through webdav from the same thread.
Re-running the same data import drops different files each time. There are
several thousand files in the zip. Each import differs by several dozen
files. It's not even close to reliable.
I’m seeing this RepositoryException in the logs for each file that’s dropped
in the final output.
I'm creating the node from a sling job consumer, then calling a method to
unpack into the webdav folder:
{quote}
adminResolver =
resolverFactory.getAdministrativeResourceResolver(null);
adminSession = adminResolver.adaptTo(Session.class);
Workspace workspace = adminSession.getWorkspace();
Node destinationNode =
JcrUtils.getOrCreateByPath(destination, JcrResourceConstants.NT_SLING_FOLDER,
adminSession);
adminSession.save();
File destinationFile = new
File(NimJcrConstants.WEBDAV_ROOT + destinationNode.getPath());
unpack(sourceFile, destinationFile);
{quote}
Full trace with some log context.
05.12.2014 12:06:06.313 *DEBUG* [127.0.0.1 [1417809966281] UNLOCK
/content/ZP/2013/2013_01_03/IPAD/1024x76815/Folio.xml HTTP/1.1]
org.apache.sling.servlets.resolver.internal.SlingServletResolver
resolveServlet called for resource NonExistingResource,
path=/content/ZP/2013/2013_01_03/IPAD/1024x76815/Folio.xml
05.12.2014 12:06:06.313 *DEBUG* [127.0.0.1 [1417809966281] UNLOCK
/content/ZP/2013/2013_01_03/IPAD/1024x76815/Folio.xml HTTP/1.1]
org.apache.sling.servlets.resolver.internal.SlingServletResolver Using cached
servlet org.apache.sling.jcr.webdav.impl.servlets.SimpleWebDavServlet
05.12.2014 12:06:06.313 *DEBUG* [127.0.0.1 [1417809966281] UNLOCK
/content/ZP/2013/2013_01_03/IPAD/1024x76815/Folio.xml HTTP/1.1]
org.apache.sling.servlets.resolver.internal.SlingServletResolver
getServletInternal returns servlet
org.apache.sling.jcr.webdav.impl.servlets.SimpleWebDavServlet
05.12.2014 12:06:06.313 *DEBUG* [127.0.0.1 [1417809966281] UNLOCK
/content/ZP/2013/2013_01_03/IPAD/1024x76815/Folio.xml HTTP/1.1]
org.apache.sling.servlets.resolver.internal.SlingServletResolver Servlet
org.apache.sling.jcr.webdav.impl.servlets.SimpleWebDavServlet found for
resource=NonExistingResource,
path=/content/ZP/2013/2013_01_03/IPAD/1024x76815/Folio.xml
05.12.2014 12:06:06.313 *DEBUG* [127.0.0.1 [1417809966281] UNLOCK
/content/ZP/2013/2013_01_03/IPAD/1024x76815/Folio.xml HTTP/1.1]
org.apache.sling.engine.impl.request.RequestData Servlet call counter : 0
05.12.2014 12:06:06.314 *DEBUG* [127.0.0.1 [1417809966281] UNLOCK
[jira] [Created] (SLING-4222) WebDAV and many javax.jcr.RepositoryException: not a token for an open-scoped JCR lock: opaquelocktoken exceptions
Bruce Edge created SLING-4222:
-
Summary: WebDAV and many javax.jcr.RepositoryException: not a
token for an open-scoped JCR lock: opaquelocktoken exceptions
Key: SLING-4222
URL: https://issues.apache.org/jira/browse/SLING-4222
Project: Sling
Issue Type: Bug
Components: JCR
Affects Versions: Launchpad Builder 8
Environment: linux
Webdav mounted with davfs using:
{{
mount -t davfs -o gid=sling,rw,uid=sling,username=admin http://localhost:8090
/mnt/jcr
% mount | grep 8090
http://localhost:8090 on /mnt/jcr type davfs
(rw,nosuid,nodev,_netdev,gid=999,uid=1009)
}}
Reporter: Bruce Edge
I have basic content extraction working with webdav. However the results are
inconsistent. Re-running the same recursive zip extraction drops different
files each time.
I’m seeing this exception in the logs for each file that’s missing in the final
output.
I'm creating the node from a sling job consumer, then calling a method to
unpack into the webdav folder:
{quote}
adminResolver =
resolverFactory.getAdministrativeResourceResolver(null);
adminSession = adminResolver.adaptTo(Session.class);
Workspace workspace = adminSession.getWorkspace();
Node destinationNode =
JcrUtils.getOrCreateByPath(destination, JcrResourceConstants.NT_SLING_FOLDER,
adminSession);
adminSession.save();
File destinationFile = new
File(NimJcrConstants.WEBDAV_ROOT + destinationNode.getPath());
unpack(sourceFile, destinationFile);
{quote}
Full trace:
{{
05.12.2014 12:06:06.313 *DEBUG* [127.0.0.1 [1417809966281] UNLOCK
/content/ZP/2013/2013_01_03/IPAD/1024x76815/Folio.xml HTTP/1.1]
org.apache.sling.servlets.resolver.internal.SlingServletResolver resolveServlet
called for resource NonExistingResource,
path=/content/ZP/2013/2013_01_03/IPAD/1024x76815/Folio.xml
05.12.2014 12:06:06.313 *DEBUG* [127.0.0.1 [1417809966281] UNLOCK
/content/ZP/2013/2013_01_03/IPAD/1024x76815/Folio.xml HTTP/1.1]
org.apache.sling.servlets.resolver.internal.SlingServletResolver Using cached
servlet org.apache.sling.jcr.webdav.impl.servlets.SimpleWebDavServlet
05.12.2014 12:06:06.313 *DEBUG* [127.0.0.1 [1417809966281] UNLOCK
/content/ZP/2013/2013_01_03/IPAD/1024x76815/Folio.xml HTTP/1.1]
org.apache.sling.servlets.resolver.internal.SlingServletResolver
getServletInternal returns servlet
org.apache.sling.jcr.webdav.impl.servlets.SimpleWebDavServlet
05.12.2014 12:06:06.313 *DEBUG* [127.0.0.1 [1417809966281] UNLOCK
/content/ZP/2013/2013_01_03/IPAD/1024x76815/Folio.xml HTTP/1.1]
org.apache.sling.servlets.resolver.internal.SlingServletResolver Servlet
org.apache.sling.jcr.webdav.impl.servlets.SimpleWebDavServlet found for
resource=NonExistingResource,
path=/content/ZP/2013/2013_01_03/IPAD/1024x76815/Folio.xml
05.12.2014 12:06:06.313 *DEBUG* [127.0.0.1 [1417809966281] UNLOCK
/content/ZP/2013/2013_01_03/IPAD/1024x76815/Folio.xml HTTP/1.1]
org.apache.sling.engine.impl.request.RequestData Servlet call counter : 0
05.12.2014 12:06:06.314 *DEBUG* [127.0.0.1 [1417809966281] UNLOCK
/content/ZP/2013/2013_01_03/IPAD/1024x76815/Folio.xml HTTP/1.1]
org.apache.jackrabbit.webdav.header.IfHeader IfHeader: No If header in request
05.12.2014 12:06:06.314 *DEBUG* [127.0.0.1 [1417809966281] UNLOCK
/content/ZP/2013/2013_01_03/IPAD/1024x76815/Folio.xml HTTP/1.1]
org.apache.jackrabbit.webdav.simple.DavSessionProviderImpl Attaching session
'org.apache.jackrabbit.webdav.simple.DavSessionImpl@123f907b' to request
'org.apache.jackrabbit.webdav.WebdavRequestImpl@b268499'
05.12.2014 12:06:06.315 *DEBUG* [127.0.0.1 [1417809966281] UNLOCK
/content/ZP/2013/2013_01_03/IPAD/1024x76815/Folio.xml HTTP/1.1]
org.apache.jackrabbit.webdav.jcr.JcrDavSession trying to add lock token
opaquelocktoken:f1816b43-97d1-481e-b77b-cc96572d3ef8 to session
javax.jcr.RepositoryException: not a token for an open-scoped JCR lock:
opaquelocktoken:f1816b43-97d1-481e-b77b-cc96572d3ef8
at
org.apache.jackrabbit.webdav.jcr.lock.LockTokenMapper.getJcrLockToken(LockTokenMapper.java:67)
at
org.apache.jackrabbit.webdav.jcr.JcrDavSession.addLockToken(JcrDavSession.java:104)
at
org.apache.jackrabbit.webdav.simple.DavSessionImpl.addLockToken(DavSessionImpl.java:61)
at
org.apache.jackrabbit.webdav.WebdavRequestImpl.setDavSession(WebdavRequestImpl.java:137)
at
org.apache.jackrabbit.webdav.simple.DavSessionProviderImpl.attachSession(DavSessionProviderImpl.java:92)
at
org.apache.jackrabbit.webdav.server.AbstractWebdavServlet.service(AbstractWebdavServlet.java:275)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at
org.apache.sling.engine.impl.request.RequestData.service(RequestData.java:533)
at
[jira] [Updated] (SLING-4222) WebDAV and many javax.jcr.RepositoryException: not a token for an open-scoped JCR lock: opaquelocktoken exceptions
[
https://issues.apache.org/jira/browse/SLING-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Edge updated SLING-4222:
--
Description:
I'm importing content using a combination of sling:folder node creation in a
JobConsumer, then extracting a zip at that target location through webdav.
Re-running the same zip extraction drops different files each time. There are
several thousand files in the zip.
I’m seeing this exception in the logs for each file that’s missing in the final
output.
I'm creating the node from a sling job consumer, then calling a method to
unpack into the webdav folder:
{quote}
adminResolver =
resolverFactory.getAdministrativeResourceResolver(null);
adminSession = adminResolver.adaptTo(Session.class);
Workspace workspace = adminSession.getWorkspace();
Node destinationNode =
JcrUtils.getOrCreateByPath(destination, JcrResourceConstants.NT_SLING_FOLDER,
adminSession);
adminSession.save();
File destinationFile = new
File(NimJcrConstants.WEBDAV_ROOT + destinationNode.getPath());
unpack(sourceFile, destinationFile);
{quote}
Full trace:
{{
05.12.2014 12:06:06.313 *DEBUG* [127.0.0.1 [1417809966281] UNLOCK
/content/ZP/2013/2013_01_03/IPAD/1024x76815/Folio.xml HTTP/1.1]
org.apache.sling.servlets.resolver.internal.SlingServletResolver resolveServlet
called for resource NonExistingResource,
path=/content/ZP/2013/2013_01_03/IPAD/1024x76815/Folio.xml
05.12.2014 12:06:06.313 *DEBUG* [127.0.0.1 [1417809966281] UNLOCK
/content/ZP/2013/2013_01_03/IPAD/1024x76815/Folio.xml HTTP/1.1]
org.apache.sling.servlets.resolver.internal.SlingServletResolver Using cached
servlet org.apache.sling.jcr.webdav.impl.servlets.SimpleWebDavServlet
05.12.2014 12:06:06.313 *DEBUG* [127.0.0.1 [1417809966281] UNLOCK
/content/ZP/2013/2013_01_03/IPAD/1024x76815/Folio.xml HTTP/1.1]
org.apache.sling.servlets.resolver.internal.SlingServletResolver
getServletInternal returns servlet
org.apache.sling.jcr.webdav.impl.servlets.SimpleWebDavServlet
05.12.2014 12:06:06.313 *DEBUG* [127.0.0.1 [1417809966281] UNLOCK
/content/ZP/2013/2013_01_03/IPAD/1024x76815/Folio.xml HTTP/1.1]
org.apache.sling.servlets.resolver.internal.SlingServletResolver Servlet
org.apache.sling.jcr.webdav.impl.servlets.SimpleWebDavServlet found for
resource=NonExistingResource,
path=/content/ZP/2013/2013_01_03/IPAD/1024x76815/Folio.xml
05.12.2014 12:06:06.313 *DEBUG* [127.0.0.1 [1417809966281] UNLOCK
/content/ZP/2013/2013_01_03/IPAD/1024x76815/Folio.xml HTTP/1.1]
org.apache.sling.engine.impl.request.RequestData Servlet call counter : 0
05.12.2014 12:06:06.314 *DEBUG* [127.0.0.1 [1417809966281] UNLOCK
/content/ZP/2013/2013_01_03/IPAD/1024x76815/Folio.xml HTTP/1.1]
org.apache.jackrabbit.webdav.header.IfHeader IfHeader: No If header in request
05.12.2014 12:06:06.314 *DEBUG* [127.0.0.1 [1417809966281] UNLOCK
/content/ZP/2013/2013_01_03/IPAD/1024x76815/Folio.xml HTTP/1.1]
org.apache.jackrabbit.webdav.simple.DavSessionProviderImpl Attaching session
'org.apache.jackrabbit.webdav.simple.DavSessionImpl@123f907b' to request
'org.apache.jackrabbit.webdav.WebdavRequestImpl@b268499'
05.12.2014 12:06:06.315 *DEBUG* [127.0.0.1 [1417809966281] UNLOCK
/content/ZP/2013/2013_01_03/IPAD/1024x76815/Folio.xml HTTP/1.1]
org.apache.jackrabbit.webdav.jcr.JcrDavSession trying to add lock token
opaquelocktoken:f1816b43-97d1-481e-b77b-cc96572d3ef8 to session
javax.jcr.RepositoryException: not a token for an open-scoped JCR lock:
opaquelocktoken:f1816b43-97d1-481e-b77b-cc96572d3ef8
at
org.apache.jackrabbit.webdav.jcr.lock.LockTokenMapper.getJcrLockToken(LockTokenMapper.java:67)
at
org.apache.jackrabbit.webdav.jcr.JcrDavSession.addLockToken(JcrDavSession.java:104)
at
org.apache.jackrabbit.webdav.simple.DavSessionImpl.addLockToken(DavSessionImpl.java:61)
at
org.apache.jackrabbit.webdav.WebdavRequestImpl.setDavSession(WebdavRequestImpl.java:137)
at
org.apache.jackrabbit.webdav.simple.DavSessionProviderImpl.attachSession(DavSessionProviderImpl.java:92)
at
org.apache.jackrabbit.webdav.server.AbstractWebdavServlet.service(AbstractWebdavServlet.java:275)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at
org.apache.sling.engine.impl.request.RequestData.service(RequestData.java:533)
at
org.apache.sling.engine.impl.filter.SlingComponentFilterChain.render(SlingComponentFilterChain.java:45)
at
org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:64)
at
org.apache.sling.engine.impl.SlingRequestProcessorImpl.processComponent(SlingRequestProcessorImpl.java:282)
at
org.apache.sling.engine.impl.filter.RequestSlingFilterChain.render(RequestSlingFilterChain.java:49)
at
[jira] [Updated] (SLING-4222) WebDAV and many javax.jcr.RepositoryException: not a token for an open-scoped JCR lock: opaquelocktoken exceptions
[
https://issues.apache.org/jira/browse/SLING-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Edge updated SLING-4222:
--
Description:
I'm importing content into the JCR default workspace using a combination of
sling:folder node creation in a JobConsumer from a bundle thread, then
extracting a zip at that target location through webdav from the same thread.
Re-running the same data import drops different files each time. There are
several thousand files in the zip. Each import differs by several dozen files.
It's not even close to reliable.
I’m seeing this RepositoryException in the logs for each file that’s dropped in
the final output.
I'm creating the node from a sling job consumer, then calling a method to
unpack into the webdav folder:
{quote}
adminResolver =
resolverFactory.getAdministrativeResourceResolver(null);
adminSession = adminResolver.adaptTo(Session.class);
Workspace workspace = adminSession.getWorkspace();
Node destinationNode =
JcrUtils.getOrCreateByPath(destination, JcrResourceConstants.NT_SLING_FOLDER,
adminSession);
adminSession.save();
File destinationFile = new
File(NimJcrConstants.WEBDAV_ROOT + destinationNode.getPath());
unpack(sourceFile, destinationFile);
{quote}
Full trace with some log context.
05.12.2014 12:06:06.313 *DEBUG* [127.0.0.1 [1417809966281] UNLOCK
/content/ZP/2013/2013_01_03/IPAD/1024x76815/Folio.xml HTTP/1.1]
org.apache.sling.servlets.resolver.internal.SlingServletResolver resolveServlet
called for resource NonExistingResource,
path=/content/ZP/2013/2013_01_03/IPAD/1024x76815/Folio.xml
05.12.2014 12:06:06.313 *DEBUG* [127.0.0.1 [1417809966281] UNLOCK
/content/ZP/2013/2013_01_03/IPAD/1024x76815/Folio.xml HTTP/1.1]
org.apache.sling.servlets.resolver.internal.SlingServletResolver Using cached
servlet org.apache.sling.jcr.webdav.impl.servlets.SimpleWebDavServlet
05.12.2014 12:06:06.313 *DEBUG* [127.0.0.1 [1417809966281] UNLOCK
/content/ZP/2013/2013_01_03/IPAD/1024x76815/Folio.xml HTTP/1.1]
org.apache.sling.servlets.resolver.internal.SlingServletResolver
getServletInternal returns servlet
org.apache.sling.jcr.webdav.impl.servlets.SimpleWebDavServlet
05.12.2014 12:06:06.313 *DEBUG* [127.0.0.1 [1417809966281] UNLOCK
/content/ZP/2013/2013_01_03/IPAD/1024x76815/Folio.xml HTTP/1.1]
org.apache.sling.servlets.resolver.internal.SlingServletResolver Servlet
org.apache.sling.jcr.webdav.impl.servlets.SimpleWebDavServlet found for
resource=NonExistingResource,
path=/content/ZP/2013/2013_01_03/IPAD/1024x76815/Folio.xml
05.12.2014 12:06:06.313 *DEBUG* [127.0.0.1 [1417809966281] UNLOCK
/content/ZP/2013/2013_01_03/IPAD/1024x76815/Folio.xml HTTP/1.1]
org.apache.sling.engine.impl.request.RequestData Servlet call counter : 0
05.12.2014 12:06:06.314 *DEBUG* [127.0.0.1 [1417809966281] UNLOCK
/content/ZP/2013/2013_01_03/IPAD/1024x76815/Folio.xml HTTP/1.1]
org.apache.jackrabbit.webdav.header.IfHeader IfHeader: No If header in request
05.12.2014 12:06:06.314 *DEBUG* [127.0.0.1 [1417809966281] UNLOCK
/content/ZP/2013/2013_01_03/IPAD/1024x76815/Folio.xml HTTP/1.1]
org.apache.jackrabbit.webdav.simple.DavSessionProviderImpl Attaching session
'org.apache.jackrabbit.webdav.simple.DavSessionImpl@123f907b' to request
'org.apache.jackrabbit.webdav.WebdavRequestImpl@b268499'
05.12.2014 12:06:06.315 *DEBUG* [127.0.0.1 [1417809966281] UNLOCK
/content/ZP/2013/2013_01_03/IPAD/1024x76815/Folio.xml HTTP/1.1]
org.apache.jackrabbit.webdav.jcr.JcrDavSession trying to add lock token
opaquelocktoken:f1816b43-97d1-481e-b77b-cc96572d3ef8 to session
*javax.jcr.RepositoryException: not a token for an open-scoped JCR lock:
opaquelocktoken:f1816b43-97d1-481e-b77b-cc96572d3ef8*
at
org.apache.jackrabbit.webdav.jcr.lock.LockTokenMapper.getJcrLockToken(LockTokenMapper.java:67)
at
org.apache.jackrabbit.webdav.jcr.JcrDavSession.addLockToken(JcrDavSession.java:104)
at
org.apache.jackrabbit.webdav.simple.DavSessionImpl.addLockToken(DavSessionImpl.java:61)
at
org.apache.jackrabbit.webdav.WebdavRequestImpl.setDavSession(WebdavRequestImpl.java:137)
at
org.apache.jackrabbit.webdav.simple.DavSessionProviderImpl.attachSession(DavSessionProviderImpl.java:92)
at
org.apache.jackrabbit.webdav.server.AbstractWebdavServlet.service(AbstractWebdavServlet.java:275)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at
org.apache.sling.engine.impl.request.RequestData.service(RequestData.java:533)
at
org.apache.sling.engine.impl.filter.SlingComponentFilterChain.render(SlingComponentFilterChain.java:45)
at
org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:64)
at
[jira] [Commented] (SLING-4151) Create debian/.ubuntu package for sling launchpad standalone jar
[ https://issues.apache.org/jira/browse/SLING-4151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14216868#comment-14216868 ] Bruce Edge commented on SLING-4151: --- I didn't re-enable the contrib module in the patch. ie: revert Bertrand's patch to disable it after the regression was discovered. Here's the patch to re-enable the debian package build: diff --git a/contrib/pom.xml b/contrib/pom.xml index e2b5253..1bdeee3 100644 --- a/contrib/pom.xml +++ b/contrib/pom.xml @@ -136,7 +136,7 @@ modulelaunchpad/karaf/module modulelaunchpad/testing/module modulexss/module - modulelaunchpad/debian/module + !-- disabled due to SLING-4151 for now modulelaunchpad/debian/module -- /modules profiles profile Create debian/.ubuntu package for sling launchpad standalone jar Key: SLING-4151 URL: https://issues.apache.org/jira/browse/SLING-4151 Project: Sling Issue Type: New Feature Components: Installer Reporter: Bruce Edge Assignee: Bertrand Delacretaz Priority: Minor Labels: debian, install, package, ubuntu Attachments: sling-dpkg.patch Original Estimate: 168h Remaining Estimate: 168h I’m setting up a development env for a team to work on a sling asset manager app. I wanted to make the env setup simple so I put together a debian/ubuntu package for the org.apache.sling.launchpad-8-SNAPSHOT-standalone.jar. It uses the jdeb maven plugin so it’s cross-platform. Here’s the patch on the off-chance it’s compatible with the upstream policies. If it needs tuning, let me know what it’s missing. Comments from dev list: - Do you mind creating a JIRA - my preference would be to have this in contrib instead of the launchpad folder -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (SLING-4151) Create debian/.ubuntu package for sling launchpad standalone jar
[
https://issues.apache.org/jira/browse/SLING-4151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14216868#comment-14216868
]
Bruce Edge edited comment on SLING-4151 at 11/18/14 9:55 PM:
-
I didn't re-enable the contrib module in the patch. ie: revert Bertrand's patch
to disable it after the regression was discovered.
Here's the patch to re-enable the debian package build:
```
diff --git a/contrib/pom.xml b/contrib/pom.xml
index e2b5253..1bdeee3 100644
--- a/contrib/pom.xml
+++ b/contrib/pom.xml
@@ -136,7 +136,7 @@
modulelaunchpad/karaf/module
modulelaunchpad/testing/module
modulexss/module
- modulelaunchpad/debian/module
+ !-- disabled due to SLING-4151 for now
modulelaunchpad/debian/module --
/modules
profiles
profile
```
was (Author: bruceedge):
I didn't re-enable the contrib module in the patch. ie: revert Bertrand's patch
to disable it after the regression was discovered.
Here's the patch to re-enable the debian package build:
{{{
diff --git a/contrib/pom.xml b/contrib/pom.xml
index e2b5253..1bdeee3 100644
--- a/contrib/pom.xml
+++ b/contrib/pom.xml
@@ -136,7 +136,7 @@
modulelaunchpad/karaf/module
modulelaunchpad/testing/module
modulexss/module
- modulelaunchpad/debian/module
+ !-- disabled due to SLING-4151 for now
modulelaunchpad/debian/module --
/modules
profiles
profile
}}}
Create debian/.ubuntu package for sling launchpad standalone jar
Key: SLING-4151
URL: https://issues.apache.org/jira/browse/SLING-4151
Project: Sling
Issue Type: New Feature
Components: Installer
Reporter: Bruce Edge
Assignee: Bertrand Delacretaz
Priority: Minor
Labels: debian, install, package, ubuntu
Attachments: sling-dpkg.patch
Original Estimate: 168h
Remaining Estimate: 168h
I’m setting up a development env for a team to work on a sling asset manager
app. I wanted to make the env setup simple so I put together a debian/ubuntu
package for the org.apache.sling.launchpad-8-SNAPSHOT-standalone.jar.
It uses the jdeb maven plugin so it’s cross-platform. Here’s the patch on the
off-chance it’s compatible with the upstream policies. If it needs tuning,
let me know what it’s missing.
Comments from dev list:
- Do you mind creating a JIRA
- my preference would be to have this in contrib instead of the launchpad
folder
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (SLING-4151) Create debian/.ubuntu package for sling launchpad standalone jar
[
https://issues.apache.org/jira/browse/SLING-4151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14216868#comment-14216868
]
Bruce Edge edited comment on SLING-4151 at 11/18/14 9:55 PM:
-
I didn't re-enable the contrib module in the patch. ie: revert Bertrand's patch
to disable it after the regression was discovered.
Here's the patch to re-enable the debian package build:
{{{
diff --git a/contrib/pom.xml b/contrib/pom.xml
index e2b5253..1bdeee3 100644
--- a/contrib/pom.xml
+++ b/contrib/pom.xml
@@ -136,7 +136,7 @@
modulelaunchpad/karaf/module
modulelaunchpad/testing/module
modulexss/module
- modulelaunchpad/debian/module
+ !-- disabled due to SLING-4151 for now
modulelaunchpad/debian/module --
/modules
profiles
profile
}}}
was (Author: bruceedge):
I didn't re-enable the contrib module in the patch. ie: revert Bertrand's patch
to disable it after the regression was discovered.
Here's the patch to re-enable the debian package build:
diff --git a/contrib/pom.xml b/contrib/pom.xml
index e2b5253..1bdeee3 100644
--- a/contrib/pom.xml
+++ b/contrib/pom.xml
@@ -136,7 +136,7 @@
modulelaunchpad/karaf/module
modulelaunchpad/testing/module
modulexss/module
- modulelaunchpad/debian/module
+ !-- disabled due to SLING-4151 for now
modulelaunchpad/debian/module --
/modules
profiles
profile
Create debian/.ubuntu package for sling launchpad standalone jar
Key: SLING-4151
URL: https://issues.apache.org/jira/browse/SLING-4151
Project: Sling
Issue Type: New Feature
Components: Installer
Reporter: Bruce Edge
Assignee: Bertrand Delacretaz
Priority: Minor
Labels: debian, install, package, ubuntu
Attachments: sling-dpkg.patch
Original Estimate: 168h
Remaining Estimate: 168h
I’m setting up a development env for a team to work on a sling asset manager
app. I wanted to make the env setup simple so I put together a debian/ubuntu
package for the org.apache.sling.launchpad-8-SNAPSHOT-standalone.jar.
It uses the jdeb maven plugin so it’s cross-platform. Here’s the patch on the
off-chance it’s compatible with the upstream policies. If it needs tuning,
let me know what it’s missing.
Comments from dev list:
- Do you mind creating a JIRA
- my preference would be to have this in contrib instead of the launchpad
folder
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Issue Comment Deleted] (SLING-4151) Create debian/.ubuntu package for sling launchpad standalone jar
[ https://issues.apache.org/jira/browse/SLING-4151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Edge updated SLING-4151: -- Comment: was deleted (was: I didn't re-enable the contrib module in the patch. ie: revert Bertrand's patch to disable it after the regression was discovered. Here's the patch to re-enable the debian package build: ``` diff --git a/contrib/pom.xml b/contrib/pom.xml index e2b5253..1bdeee3 100644 --- a/contrib/pom.xml +++ b/contrib/pom.xml @@ -136,7 +136,7 @@ modulelaunchpad/karaf/module modulelaunchpad/testing/module modulexss/module - modulelaunchpad/debian/module + !-- disabled due to SLING-4151 for now modulelaunchpad/debian/module -- /modules profiles profile ```) Create debian/.ubuntu package for sling launchpad standalone jar Key: SLING-4151 URL: https://issues.apache.org/jira/browse/SLING-4151 Project: Sling Issue Type: New Feature Components: Installer Reporter: Bruce Edge Assignee: Bertrand Delacretaz Priority: Minor Labels: debian, install, package, ubuntu Attachments: sling-dpkg.patch Original Estimate: 168h Remaining Estimate: 168h I’m setting up a development env for a team to work on a sling asset manager app. I wanted to make the env setup simple so I put together a debian/ubuntu package for the org.apache.sling.launchpad-8-SNAPSHOT-standalone.jar. It uses the jdeb maven plugin so it’s cross-platform. Here’s the patch on the off-chance it’s compatible with the upstream policies. If it needs tuning, let me know what it’s missing. Comments from dev list: - Do you mind creating a JIRA - my preference would be to have this in contrib instead of the launchpad folder -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-4151) Create debian/.ubuntu package for sling launchpad standalone jar
[ https://issues.apache.org/jira/browse/SLING-4151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Edge updated SLING-4151: -- Attachment: re-enable-debian.patch Patch to re-enable debian build. Create debian/.ubuntu package for sling launchpad standalone jar Key: SLING-4151 URL: https://issues.apache.org/jira/browse/SLING-4151 Project: Sling Issue Type: New Feature Components: Installer Reporter: Bruce Edge Assignee: Bertrand Delacretaz Priority: Minor Labels: debian, install, package, ubuntu Attachments: re-enable-debian.patch, sling-dpkg.patch Original Estimate: 168h Remaining Estimate: 168h I’m setting up a development env for a team to work on a sling asset manager app. I wanted to make the env setup simple so I put together a debian/ubuntu package for the org.apache.sling.launchpad-8-SNAPSHOT-standalone.jar. It uses the jdeb maven plugin so it’s cross-platform. Here’s the patch on the off-chance it’s compatible with the upstream policies. If it needs tuning, let me know what it’s missing. Comments from dev list: - Do you mind creating a JIRA - my preference would be to have this in contrib instead of the launchpad folder -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-4151) Create debian/.ubuntu package for sling launchpad standalone jar
[ https://issues.apache.org/jira/browse/SLING-4151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14212533#comment-14212533 ] Bruce Edge commented on SLING-4151: --- If the debian package is not built along side a full sling build, how can I get the version number of the org.apache.sling.launchpad jar to copy? I can't use -SNAPSHOT as the apache snapshots repo contains jenkins generated version numbers. Is there a jenkins provided property I can use for the version string? Create debian/.ubuntu package for sling launchpad standalone jar Key: SLING-4151 URL: https://issues.apache.org/jira/browse/SLING-4151 Project: Sling Issue Type: New Feature Components: Installer Reporter: Bruce Edge Assignee: Bertrand Delacretaz Priority: Minor Labels: debian, install, package, ubuntu Attachments: sling-dpkg.patch Original Estimate: 168h Remaining Estimate: 168h I’m setting up a development env for a team to work on a sling asset manager app. I wanted to make the env setup simple so I put together a debian/ubuntu package for the org.apache.sling.launchpad-8-SNAPSHOT-standalone.jar. It uses the jdeb maven plugin so it’s cross-platform. Here’s the patch on the off-chance it’s compatible with the upstream policies. If it needs tuning, let me know what it’s missing. Comments from dev list: - Do you mind creating a JIRA - my preference would be to have this in contrib instead of the launchpad folder -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-4151) Create debian/.ubuntu package for sling launchpad standalone jar
[ https://issues.apache.org/jira/browse/SLING-4151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Edge updated SLING-4151: -- Attachment: (was: sling-dpkg.patch) Create debian/.ubuntu package for sling launchpad standalone jar Key: SLING-4151 URL: https://issues.apache.org/jira/browse/SLING-4151 Project: Sling Issue Type: New Feature Components: Installer Reporter: Bruce Edge Assignee: Bertrand Delacretaz Priority: Minor Labels: debian, install, package, ubuntu Original Estimate: 168h Remaining Estimate: 168h I’m setting up a development env for a team to work on a sling asset manager app. I wanted to make the env setup simple so I put together a debian/ubuntu package for the org.apache.sling.launchpad-8-SNAPSHOT-standalone.jar. It uses the jdeb maven plugin so it’s cross-platform. Here’s the patch on the off-chance it’s compatible with the upstream policies. If it needs tuning, let me know what it’s missing. Comments from dev list: - Do you mind creating a JIRA - my preference would be to have this in contrib instead of the launchpad folder -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-4151) Create debian/.ubuntu package for sling launchpad standalone jar
[ https://issues.apache.org/jira/browse/SLING-4151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Edge updated SLING-4151: -- Attachment: sling-dpkg.patch Patch to fix problematic artifact reference. Use maven dependencies plugin to resolve artifact properly. Create debian/.ubuntu package for sling launchpad standalone jar Key: SLING-4151 URL: https://issues.apache.org/jira/browse/SLING-4151 Project: Sling Issue Type: New Feature Components: Installer Reporter: Bruce Edge Assignee: Bertrand Delacretaz Priority: Minor Labels: debian, install, package, ubuntu Attachments: sling-dpkg.patch Original Estimate: 168h Remaining Estimate: 168h I’m setting up a development env for a team to work on a sling asset manager app. I wanted to make the env setup simple so I put together a debian/ubuntu package for the org.apache.sling.launchpad-8-SNAPSHOT-standalone.jar. It uses the jdeb maven plugin so it’s cross-platform. Here’s the patch on the off-chance it’s compatible with the upstream policies. If it needs tuning, let me know what it’s missing. Comments from dev list: - Do you mind creating a JIRA - my preference would be to have this in contrib instead of the launchpad folder -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-4151) Create debian/.ubuntu package for sling launchpad standalone jar
[ https://issues.apache.org/jira/browse/SLING-4151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14208126#comment-14208126 ] Bruce Edge commented on SLING-4151: --- Patch is ready for review. Create debian/.ubuntu package for sling launchpad standalone jar Key: SLING-4151 URL: https://issues.apache.org/jira/browse/SLING-4151 Project: Sling Issue Type: New Feature Components: Installer Reporter: Bruce Edge Priority: Minor Labels: debian, install, package, ubuntu Attachments: sling-dpkg.patch Original Estimate: 168h Remaining Estimate: 168h I’m setting up a development env for a team to work on a sling asset manager app. I wanted to make the env setup simple so I put together a debian/ubuntu package for the org.apache.sling.launchpad-8-SNAPSHOT-standalone.jar. It uses the jdeb maven plugin so it’s cross-platform. Here’s the patch on the off-chance it’s compatible with the upstream policies. If it needs tuning, let me know what it’s missing. Comments from dev list: - Do you mind creating a JIRA - my preference would be to have this in contrib instead of the launchpad folder -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-4151) Create debian/.ubuntu package for sling launchpad standalone jar
[ https://issues.apache.org/jira/browse/SLING-4151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Edge updated SLING-4151: -- Attachment: (was: sling-dpkg.patch) Create debian/.ubuntu package for sling launchpad standalone jar Key: SLING-4151 URL: https://issues.apache.org/jira/browse/SLING-4151 Project: Sling Issue Type: New Feature Components: Installer Reporter: Bruce Edge Priority: Minor Labels: debian, install, package, ubuntu Attachments: sling-dpkg.patch Original Estimate: 168h Remaining Estimate: 168h I’m setting up a development env for a team to work on a sling asset manager app. I wanted to make the env setup simple so I put together a debian/ubuntu package for the org.apache.sling.launchpad-8-SNAPSHOT-standalone.jar. It uses the jdeb maven plugin so it’s cross-platform. Here’s the patch on the off-chance it’s compatible with the upstream policies. If it needs tuning, let me know what it’s missing. Comments from dev list: - Do you mind creating a JIRA - my preference would be to have this in contrib instead of the launchpad folder -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-4151) Create debian/.ubuntu package for sling launchpad standalone jar
[ https://issues.apache.org/jira/browse/SLING-4151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Edge updated SLING-4151: -- Attachment: sling-dpkg.patch Use SIGTERM rather than KILL to terminate a bit more gently. No more /var/lib/sling/jackrabbit/.lock detected. Repository was not shut down properly. warnings Create debian/.ubuntu package for sling launchpad standalone jar Key: SLING-4151 URL: https://issues.apache.org/jira/browse/SLING-4151 Project: Sling Issue Type: New Feature Components: Installer Reporter: Bruce Edge Priority: Minor Labels: debian, install, package, ubuntu Attachments: sling-dpkg.patch Original Estimate: 168h Remaining Estimate: 168h I’m setting up a development env for a team to work on a sling asset manager app. I wanted to make the env setup simple so I put together a debian/ubuntu package for the org.apache.sling.launchpad-8-SNAPSHOT-standalone.jar. It uses the jdeb maven plugin so it’s cross-platform. Here’s the patch on the off-chance it’s compatible with the upstream policies. If it needs tuning, let me know what it’s missing. Comments from dev list: - Do you mind creating a JIRA - my preference would be to have this in contrib instead of the launchpad folder -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-4151) Create debian/.ubuntu package for sling launchpad standalone jar
[ https://issues.apache.org/jira/browse/SLING-4151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Edge updated SLING-4151: -- Attachment: sling-dpkg.patch Updated patch to include apache license headers. Create debian/.ubuntu package for sling launchpad standalone jar Key: SLING-4151 URL: https://issues.apache.org/jira/browse/SLING-4151 Project: Sling Issue Type: New Feature Components: Installer Reporter: Bruce Edge Priority: Minor Labels: debian, install, package, ubuntu Attachments: sling-dpkg.patch Original Estimate: 168h Remaining Estimate: 168h I’m setting up a development env for a team to work on a sling asset manager app. I wanted to make the env setup simple so I put together a debian/ubuntu package for the org.apache.sling.launchpad-8-SNAPSHOT-standalone.jar. It uses the jdeb maven plugin so it’s cross-platform. Here’s the patch on the off-chance it’s compatible with the upstream policies. If it needs tuning, let me know what it’s missing. Comments from dev list: - Do you mind creating a JIRA - my preference would be to have this in contrib instead of the launchpad folder -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-4151) Create debian/.ubuntu package for sling launchpad standalone jar
[ https://issues.apache.org/jira/browse/SLING-4151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Edge updated SLING-4151: -- Attachment: (was: sling-dpkg.patch) Create debian/.ubuntu package for sling launchpad standalone jar Key: SLING-4151 URL: https://issues.apache.org/jira/browse/SLING-4151 Project: Sling Issue Type: New Feature Components: Installer Reporter: Bruce Edge Priority: Minor Labels: debian, install, package, ubuntu Attachments: sling-dpkg.patch Original Estimate: 168h Remaining Estimate: 168h I’m setting up a development env for a team to work on a sling asset manager app. I wanted to make the env setup simple so I put together a debian/ubuntu package for the org.apache.sling.launchpad-8-SNAPSHOT-standalone.jar. It uses the jdeb maven plugin so it’s cross-platform. Here’s the patch on the off-chance it’s compatible with the upstream policies. If it needs tuning, let me know what it’s missing. Comments from dev list: - Do you mind creating a JIRA - my preference would be to have this in contrib instead of the launchpad folder -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SLING-4151) Create debian/.ubuntu package for sling launchpad standalone jar
Bruce Edge created SLING-4151: - Summary: Create debian/.ubuntu package for sling launchpad standalone jar Key: SLING-4151 URL: https://issues.apache.org/jira/browse/SLING-4151 Project: Sling Issue Type: New Feature Components: Installer Reporter: Bruce Edge Priority: Minor I’m setting up a development env for a team to work on a sling asset manager app. I wanted to make the env setup simple so I put together a debian/ubuntu package for the org.apache.sling.launchpad-8-SNAPSHOT-standalone.jar. It uses the jdeb maven plugin so it’s cross-platform. Here’s the patch on the off-chance it’s compatible with the upstream policies. If it needs tuning, let me know what it’s missing. Comments from dev list: - Do you mind creating a JIRA - my preference would be to have this in contrib instead of the launchpad folder -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-4151) Create debian/.ubuntu package for sling launchpad standalone jar
[ https://issues.apache.org/jira/browse/SLING-4151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Edge updated SLING-4151: -- Attachment: sling-dpkg.patch Moved to contrib/launchpad/debian. Added README.txt Unable to verify full contrib build for other dependency problems, but the package builds as long as the main build completes. Create debian/.ubuntu package for sling launchpad standalone jar Key: SLING-4151 URL: https://issues.apache.org/jira/browse/SLING-4151 Project: Sling Issue Type: New Feature Components: Installer Reporter: Bruce Edge Priority: Minor Labels: debian, install, package, ubuntu Attachments: sling-dpkg.patch Original Estimate: 168h Remaining Estimate: 168h I’m setting up a development env for a team to work on a sling asset manager app. I wanted to make the env setup simple so I put together a debian/ubuntu package for the org.apache.sling.launchpad-8-SNAPSHOT-standalone.jar. It uses the jdeb maven plugin so it’s cross-platform. Here’s the patch on the off-chance it’s compatible with the upstream policies. If it needs tuning, let me know what it’s missing. Comments from dev list: - Do you mind creating a JIRA - my preference would be to have this in contrib instead of the launchpad folder -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SLING-4136) Wrong org.apache.sling.event version dependency in launchpad list.xml
Bruce Edge created SLING-4136: - Summary: Wrong org.apache.sling.event version dependency in launchpad list.xml Key: SLING-4136 URL: https://issues.apache.org/jira/browse/SLING-4136 Project: Sling Issue Type: Bug Components: Launchpad Affects Versions: Launchpad Builder 7 Environment: Apache Maven 3.2.3 (33f8c3e1027c3ddde99d3cdebad2656a31e8fdf4; 2014-08-11T13:58:10-07:00) Maven home: /usr/local/Cellar/maven/3.2.3/libexec Java version: 1.7.0_55, vendor: Oracle Corporation Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_55.jdk/Contents/Home/jre Default locale: en_US, platform encoding: UTF-8 OS name: mac os x, version: 10.10, arch: x86_64, family: mac Reporter: Bruce Edge [INFO] Apache Sling Launchpad Application Builder . FAILURE [ 1.130 s] [INFO] Apache Sling Sample Server-Side Tests .. SKIPPED [INFO] Apache Sling Failing Server-Side Tests . SKIPPED [INFO] Apache Sling Sample Integration Tests .. SKIPPED [INFO] Apache Sling Launchpad Testing Services SKIPPED [INFO] Apache Sling Launchpad Testing Services WAR SKIPPED [INFO] Apache Sling Launchpad Testing Fragment Bundle . SKIPPED [INFO] Apache Sling Launchpad Test Bundles SKIPPED [INFO] Apache Sling Integration Tests . SKIPPED [INFO] Apache Sling Launchpad Testing . SKIPPED [INFO] Apache Sling (Builder) . SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 4.524 s [INFO] Finished at: 2014-11-05T11:25:38-08:00 [INFO] Final Memory: 104M/733M [INFO] [ERROR] Failed to execute goal on project org.apache.sling.launchpad: Could not resolve dependencies for project org.apache.sling:org.apache.sling.launchpad:war:8-SNAPSHOT: Failure to find org.apache.sling:org.apache.sling.event:jar:3.4.3-SNAPSHOT in http://nexus.nim.com:80 81/nexus/content/groups/public was cached in the local repository, resolution will not be reattempted until the update interval of nexus has elapsed or updates are forced - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-4136) Wrong org.apache.sling.event version dependency in launchpad list.xml
[ https://issues.apache.org/jira/browse/SLING-4136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14198975#comment-14198975 ] Bruce Edge commented on SLING-4136: --- This fixes the issue for me, although I don't know what the impact on the version actually is. diff --git a/launchpad/builder/src/main/bundles/list.xml b/launchpad/builder/src/main/bundles/list.xml index 82dcf68..71c9643 100644 --- a/launchpad/builder/src/main/bundles/list.xml +++ b/launchpad/builder/src/main/bundles/list.xml @@ -174,7 +174,7 @@ bundle groupIdorg.apache.sling/groupId artifactIdorg.apache.sling.event/artifactId -version3.4.3-SNAPSHOT/version +version3.4.5-SNAPSHOT/version /bundle bundle groupIdorg.apache.sling/groupId Wrong org.apache.sling.event version dependency in launchpad list.xml - Key: SLING-4136 URL: https://issues.apache.org/jira/browse/SLING-4136 Project: Sling Issue Type: Bug Components: Launchpad Affects Versions: Launchpad Builder 7 Environment: Apache Maven 3.2.3 (33f8c3e1027c3ddde99d3cdebad2656a31e8fdf4; 2014-08-11T13:58:10-07:00) Maven home: /usr/local/Cellar/maven/3.2.3/libexec Java version: 1.7.0_55, vendor: Oracle Corporation Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_55.jdk/Contents/Home/jre Default locale: en_US, platform encoding: UTF-8 OS name: mac os x, version: 10.10, arch: x86_64, family: mac Reporter: Bruce Edge [INFO] Apache Sling Launchpad Application Builder . FAILURE [ 1.130 s] [INFO] Apache Sling Sample Server-Side Tests .. SKIPPED [INFO] Apache Sling Failing Server-Side Tests . SKIPPED [INFO] Apache Sling Sample Integration Tests .. SKIPPED [INFO] Apache Sling Launchpad Testing Services SKIPPED [INFO] Apache Sling Launchpad Testing Services WAR SKIPPED [INFO] Apache Sling Launchpad Testing Fragment Bundle . SKIPPED [INFO] Apache Sling Launchpad Test Bundles SKIPPED [INFO] Apache Sling Integration Tests . SKIPPED [INFO] Apache Sling Launchpad Testing . SKIPPED [INFO] Apache Sling (Builder) . SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 4.524 s [INFO] Finished at: 2014-11-05T11:25:38-08:00 [INFO] Final Memory: 104M/733M [INFO] [ERROR] Failed to execute goal on project org.apache.sling.launchpad: Could not resolve dependencies for project org.apache.sling:org.apache.sling.launchpad:war:8-SNAPSHOT: Failure to find org.apache.sling:org.apache.sling.event:jar:3.4.3-SNAPSHOT in http://nexus.nim.com:80 81/nexus/content/groups/public was cached in the local repository, resolution will not be reattempted until the update interval of nexus has elapsed or updates are forced - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SLING-4137) Unit test errors: Could not find artifact org.apache.sling:org.apache.sling.jcr.resource:jar:2.3.11-SNAPSHOT
Bruce Edge created SLING-4137: - Summary: Unit test errors: Could not find artifact org.apache.sling:org.apache.sling.jcr.resource:jar:2.3.11-SNAPSHOT Key: SLING-4137 URL: https://issues.apache.org/jira/browse/SLING-4137 Project: Sling Issue Type: Bug Components: JCR Affects Versions: Launchpad Builder 8 Environment: Apache Maven 3.2.3 (33f8c3e1027c3ddde99d3cdebad2656a31e8fdf4; 2014-08-11T13:58:10-07:00) Maven home: /usr/local/Cellar/maven/3.2.3/libexec Java version: 1.7.0_55, vendor: Oracle Corporation Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_55.jdk/Contents/Home/jre Default locale: en_US, platform encoding: UTF-8 OS name: mac os x, version: 10.10, arch: x86_64, family: mac Reporter: Bruce Edge Priority: Minor Not sure where the 2.3.11 version of org.apache.sling.jcr.resource is defined. 2867 [main] WARN org.ops4j.pax.url.mvn.internal.AetherBasedResolver - Error resolving artifactorg.apache.sling:org.apache.sling.jcr.resource:jar:2.3.11-SNAPSHOT:Could not find artifact org.apache.sling:org.apache.sling.jcr.resource:jar:2.3.11-SNAPSHOT shaded.org.eclipse.aether.resolution.ArtifactResolutionException: Could not find artifact org.apache.sling:org.apache.sling.jcr.resource:jar:2.3.11-SNAPSHOT at shaded.org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:444) at shaded.org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:246) at shaded.org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:223) at shaded.org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveArtifact(DefaultRepositorySystem.java:294) at org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:343) at org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolveFile(AetherBasedResolver.java:312) at org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:296) at org.ops4j.pax.url.mvn.internal.Connection.getInputStream(Connection.java:131) at java.net.URL.openStream(URL.java:1037) at org.ops4j.pax.exam.forked.provision.StreamUtils.streamCopy(StreamUtils.java:103) at org.ops4j.pax.exam.forked.provision.PlatformImpl.download(PlatformImpl.java:133) at org.ops4j.pax.exam.forked.ForkedTestContainer.downloadBundle(ForkedTestContainer.java:352) at org.ops4j.pax.exam.forked.ForkedTestContainer.installAndStartBundles(ForkedTestContainer.java:281) at org.ops4j.pax.exam.forked.ForkedTestContainer.start(ForkedTestContainer.java:150) at org.ops4j.pax.exam.spi.reactors.EagerSingleStagedReactor.setUp(EagerSingleStagedReactor.java:86) at org.ops4j.pax.exam.spi.reactors.EagerSingleStagedReactor.beforeClass(EagerSingleStagedReactor.java:136) at org.ops4j.pax.exam.spi.reactors.ReactorManager.beforeClass(ReactorManager.java:452) at org.ops4j.pax.exam.junit.impl.ProbeRunner.run(ProbeRunner.java:111) at org.ops4j.pax.exam.junit.PaxExam.run(PaxExam.java:93) at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124) at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) Caused by: shaded.org.eclipse.aether.transfer.ArtifactNotFoundException: Could not find artifact org.apache.sling:org.apache.sling.jcr.resource:jar:2.3.11-SNAPSHOT at shaded.org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:434) ... 24 more 2870 [main] WARN org.ops4j.pax.exam.spi.DefaultExamSystem - Option org.ops4j.pax.exam.options.FrameworkStartLevelOption has not been recognized. 2890 [main] INFO org.ops4j.exec.DefaultJavaRunner - Platform has been shutdown. 2890 [main] WARN org.ops4j.pax.exam.spi.DefaultExamSystem - Option org.ops4j.pax.exam.options.FrameworkStartLevelOption has not been recognized. 2890 [main] INFO org.ops4j.pax.exam.spi.reactors.ReactorManager - suite finished Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.808 sec FAILURE! - in org.apache.sling.jcr.repository.it.OakRepositoryIT org.apache.sling.jcr.repository.it.OakRepositoryIT Time elapsed: 0.786 sec ERROR! org.ops4j.pax.exam.TestContainerException: [mvn:org.apache.sling/org.apache.sling.jcr.resource/2.3.11-SNAPSHOT] could not be downloaded
[jira] [Commented] (SLING-2760) org.apache.sling.auth.openid bundle has dependencies not available on Maven central
[
https://issues.apache.org/jira/browse/SLING-2760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14120662#comment-14120662
]
Bruce Edge commented on SLING-2760:
---
Following the current readme on building sling
http://sling.apache.org/documentation/development/getting-and-building-sling.html,
this problem still exists.
[ERROR] Failed to execute goal on project org.apache.sling.auth.openid: Could
not resolve dependencies for project
org.apache.sling:org.apache.sling.auth.openid:bundle:1.0.5-SNAPSHOT: The
following artifacts could not be resolved:
com.dyuproject:dyuproject-openid:jar:1.1.7,
com.dyuproject:dyuproject-util:jar:1.1.7,
com.dyuproject:dyuproject-json:jar:1.1.7: Failure to find
com.dyuproject:dyuproject-openid:jar:1.1.7
What's the workaround?
org.apache.sling.auth.openid bundle has dependencies not available on Maven
central
---
Key: SLING-2760
URL: https://issues.apache.org/jira/browse/SLING-2760
Project: Sling
Issue Type: Bug
Components: Authentication
Affects Versions: OpenID Authentication 1.0.2
Reporter: Robert Munteanu
Priority: Minor
The org.apache.sling.auth.openid bundle includes the following repository
definition in its pom.xml file
{code}repositories
repository
releases
enabledtrue/enabled
/releases
iddyuproject-repo/id
namedyuproject-repo/name
urlhttp://dyuproject.googlecode.com/svn/repos/maven2/url
/repository
/repositories
{code}
and the following dependencies
{code}
dependency
groupIdcom.dyuproject/groupId
artifactIddyuproject-openid/artifactId
version1.1.7/version
/dependency
dependency
groupIdcom.dyuproject/groupId
artifactIddyuproject-util/artifactId
version1.1.7/version
/dependency
dependency
groupIdcom.dyuproject/groupId
artifactIddyuproject-json/artifactId
version1.1.7/version
/dependency
{code}
Since we sync/upload these artifacts to maven central [1] we should consider
following the recommendation of not adding repositories to POMs [2] . There
is an open request in the dyuproject tracker [3] to upload the openid
artifacts to Maven Central, but it's been there for almost two years, and the
project hasn't seen much activity ( no commits since June 2011 ).
I see two ways around this issue:
- Use the sonatype service for uploading 3rd party bundles to Maven Central
[4]
- Replace the com.dyuproject dependency with something different
Thoughts?
[1]: http://search.maven.org/#search|ga|1|org.apache.sling.auth.openid
[2]:
https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide#SonatypeOSSMavenRepositoryUsageGuide-6.CentralSyncRequirement
[3]: http://code.google.com/p/dyuproject/issues/detail?id=32
[4]:
https://docs.sonatype.org/display/Repository/Uploading+3rd-party+Artifacts+to+The+Central+Repository
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Issue Comment Deleted] (SLING-2760) org.apache.sling.auth.openid bundle has dependencies not available on Maven central
[
https://issues.apache.org/jira/browse/SLING-2760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Edge updated SLING-2760:
--
Comment: was deleted
(was: Following the current readme on building sling
http://sling.apache.org/documentation/development/getting-and-building-sling.html,
this problem still exists.
[ERROR] Failed to execute goal on project org.apache.sling.auth.openid: Could
not resolve dependencies for project
org.apache.sling:org.apache.sling.auth.openid:bundle:1.0.5-SNAPSHOT: The
following artifacts could not be resolved:
com.dyuproject:dyuproject-openid:jar:1.1.7,
com.dyuproject:dyuproject-util:jar:1.1.7,
com.dyuproject:dyuproject-json:jar:1.1.7: Failure to find
com.dyuproject:dyuproject-openid:jar:1.1.7
What's the workaround?
)
org.apache.sling.auth.openid bundle has dependencies not available on Maven
central
---
Key: SLING-2760
URL: https://issues.apache.org/jira/browse/SLING-2760
Project: Sling
Issue Type: Bug
Components: Authentication
Affects Versions: OpenID Authentication 1.0.2
Reporter: Robert Munteanu
Priority: Minor
The org.apache.sling.auth.openid bundle includes the following repository
definition in its pom.xml file
{code}repositories
repository
releases
enabledtrue/enabled
/releases
iddyuproject-repo/id
namedyuproject-repo/name
urlhttp://dyuproject.googlecode.com/svn/repos/maven2/url
/repository
/repositories
{code}
and the following dependencies
{code}
dependency
groupIdcom.dyuproject/groupId
artifactIddyuproject-openid/artifactId
version1.1.7/version
/dependency
dependency
groupIdcom.dyuproject/groupId
artifactIddyuproject-util/artifactId
version1.1.7/version
/dependency
dependency
groupIdcom.dyuproject/groupId
artifactIddyuproject-json/artifactId
version1.1.7/version
/dependency
{code}
Since we sync/upload these artifacts to maven central [1] we should consider
following the recommendation of not adding repositories to POMs [2] . There
is an open request in the dyuproject tracker [3] to upload the openid
artifacts to Maven Central, but it's been there for almost two years, and the
project hasn't seen much activity ( no commits since June 2011 ).
I see two ways around this issue:
- Use the sonatype service for uploading 3rd party bundles to Maven Central
[4]
- Replace the com.dyuproject dependency with something different
Thoughts?
[1]: http://search.maven.org/#search|ga|1|org.apache.sling.auth.openid
[2]:
https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide#SonatypeOSSMavenRepositoryUsageGuide-6.CentralSyncRequirement
[3]: http://code.google.com/p/dyuproject/issues/detail?id=32
[4]:
https://docs.sonatype.org/display/Repository/Uploading+3rd-party+Artifacts+to+The+Central+Repository
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
