[jira] [Commented] (SLING-7502) Resource Digest Calculation returns different values for the same data
[ https://issues.apache.org/jira/browse/SLING-7502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16368820#comment-16368820 ] Konrad Windszus commented on SLING-7502: Release vote is ongoing: http://apache-sling.73963.n3.nabble.com/VOTE-Release-Apache-Sling-Installer-version-3-8-12-td4081006.html > Resource Digest Calculation returns different values for the same data > -- > > Key: SLING-7502 > URL: https://issues.apache.org/jira/browse/SLING-7502 > Project: Sling > Issue Type: Bug > Components: Installer >Affects Versions: Installer Core 3.8.10 >Reporter: David Bosschaert >Assignee: Carsten Ziegeler >Priority: Major > Fix For: Installer Core 3.8.14 > > > This causes issues that sometimes resources are internally seen as different > versions of the same resource which messes up the bookkeeping of resources in > the installer. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SLING-7502) Resource Digest Calculation returns different values for the same data
[ https://issues.apache.org/jira/browse/SLING-7502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16368818#comment-16368818 ] Carsten Ziegeler commented on SLING-7502: - [~kwin] , [~rombert] I don't see a 3.8.12 release in [1] and it's not marked as released [1]http://repo1.maven.org/maven2/org/apache/sling/org.apache.sling.installer.core/ > Resource Digest Calculation returns different values for the same data > -- > > Key: SLING-7502 > URL: https://issues.apache.org/jira/browse/SLING-7502 > Project: Sling > Issue Type: Bug > Components: Installer >Affects Versions: Installer Core 3.8.10 >Reporter: David Bosschaert >Assignee: Carsten Ziegeler >Priority: Major > Fix For: Installer Core 3.8.14 > > > This causes issues that sometimes resources are internally seen as different > versions of the same resource which messes up the bookkeeping of resources in > the installer. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SLING-7505) Installer: Set error message also for overwritten resources
[ https://issues.apache.org/jira/browse/SLING-7505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus resolved SLING-7505. Resolution: Fixed Fix Version/s: Installer Core 3.8.14 > Installer: Set error message also for overwritten resources > --- > > Key: SLING-7505 > URL: https://issues.apache.org/jira/browse/SLING-7505 > Project: Sling > Issue Type: Improvement > Components: Installer >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > Fix For: Installer Core 3.8.14 > > > In case the OSGi installer gets a resource with the same entity id as an > existing one but a lower version/priority/digest it remains in status > "INSTALL". To improve the readability in the OSGi Installer web console, that > state should be accompanied by an according error message (to make it clearer > why this is not considered). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SLING-7502) Resource Digest Calculation returns different values for the same data
[ https://issues.apache.org/jira/browse/SLING-7502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-7502: --- Fix Version/s: (was: Installer Core 3.8.12) Installer Core 3.8.14 > Resource Digest Calculation returns different values for the same data > -- > > Key: SLING-7502 > URL: https://issues.apache.org/jira/browse/SLING-7502 > Project: Sling > Issue Type: Bug > Components: Installer >Affects Versions: Installer Core 3.8.10 >Reporter: David Bosschaert >Assignee: Carsten Ziegeler >Priority: Major > Fix For: Installer Core 3.8.14 > > > This causes issues that sometimes resources are internally seen as different > versions of the same resource which messes up the bookkeeping of resources in > the installer. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SLING-7505) Installer: Set error message also for overwritten resources
[ https://issues.apache.org/jira/browse/SLING-7505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16368604#comment-16368604 ] Konrad Windszus commented on SLING-7505: Fixed in https://github.com/apache/sling-org-apache-sling-installer-core/commit/22434982726f0198402be4ca682dae5b5a268586. > Installer: Set error message also for overwritten resources > --- > > Key: SLING-7505 > URL: https://issues.apache.org/jira/browse/SLING-7505 > Project: Sling > Issue Type: Improvement > Components: Installer >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > > In case the OSGi installer gets a resource with the same entity id as an > existing one but a lower version/priority/digest it remains in status > "INSTALL". To improve the readability in the OSGi Installer web console, that > state should be accompanied by an according error message (to make it clearer > why this is not considered). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SLING-7505) Installer: Set error message also for overwritten resources
[ https://issues.apache.org/jira/browse/SLING-7505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus reassigned SLING-7505: -- Assignee: Konrad Windszus > Installer: Set error message also for overwritten resources > --- > > Key: SLING-7505 > URL: https://issues.apache.org/jira/browse/SLING-7505 > Project: Sling > Issue Type: Improvement > Components: Installer >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > > In case the OSGi installer gets a resource with the same entity id as an > existing one but a lower version/priority/digest it remains in status > "INSTALL". To improve the readability in the OSGi Installer web console, that > state should be accompanied by an according error message (to make it clearer > why this is not considered). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SLING-7505) Installer: Set error message also for overwritten resources
Konrad Windszus created SLING-7505: -- Summary: Installer: Set error message also for overwritten resources Key: SLING-7505 URL: https://issues.apache.org/jira/browse/SLING-7505 Project: Sling Issue Type: Improvement Components: Installer Reporter: Konrad Windszus In case the OSGi installer gets a resource with the same entity id as an existing one but a lower version/priority/digest it remains in status "INSTALL". To improve the readability in the OSGi Installer web console, that state should be accompanied by an according error message (to make it clearer why this is not considered). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SLING-7503) OSGi Installer Web Console: Error not exposed
[ https://issues.apache.org/jira/browse/SLING-7503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus resolved SLING-7503. Resolution: Fixed > OSGi Installer Web Console: Error not exposed > - > > Key: SLING-7503 > URL: https://issues.apache.org/jira/browse/SLING-7503 > Project: Sling > Issue Type: Bug > Components: Installer >Affects Versions: Installer Console 1.0.2 >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > Fix For: Installer Console 1.0.4 > > > The fix from SLING-6176 was supposed to expose the error string of each > resource (in case one was set). Unfortunately the column is empty under > certain circumstances. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SLING-7503) OSGi Installer Web Console: Error not exposed
[ https://issues.apache.org/jira/browse/SLING-7503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16368531#comment-16368531 ] Konrad Windszus commented on SLING-7503: Fixed in https://github.com/apache/sling-org-apache-sling-installer-console/commit/8081c7363ff427280e5ed6c36014b83237b75b9d. > OSGi Installer Web Console: Error not exposed > - > > Key: SLING-7503 > URL: https://issues.apache.org/jira/browse/SLING-7503 > Project: Sling > Issue Type: Bug > Components: Installer >Affects Versions: Installer Console 1.0.2 >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > Fix For: Installer Console 1.0.4 > > > The fix from SLING-6176 was supposed to expose the error string of each > resource (in case one was set). Unfortunately the column is empty under > certain circumstances. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SLING-7503) OSGi Installer Web Console: Error not exposed
[ https://issues.apache.org/jira/browse/SLING-7503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-7503: --- Description: The fix from SLING-6176 was supposed to expose the error string of each resource (in case one was set). Unfortunately the column is empty under certain circumstances. (was: The fix from SLING-6176 was supposed to expose the error string of each resource (in case one was set). Unfortunately the column is always empty.) > OSGi Installer Web Console: Error not exposed > - > > Key: SLING-7503 > URL: https://issues.apache.org/jira/browse/SLING-7503 > Project: Sling > Issue Type: Bug > Components: Installer >Affects Versions: Installer Console 1.0.2 >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > Fix For: Installer Console 1.0.4 > > > The fix from SLING-6176 was supposed to expose the error string of each > resource (in case one was set). Unfortunately the column is empty under > certain circumstances. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SLING-7504) Sling File Installer Provider inactive in Sling Starter
[
https://issues.apache.org/jira/browse/SLING-7504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-7504:
---
Description: Even in the newest Starter 11 the framework property for the
Sling File Installer is not set by default. This should be fixed. The relevant
framework property is {{sling.fileinstall.dir}}. I propose to set this to
{{${sling.launchpad}/install}} (was: Even in the newest Starter 11 the
framework property for the Sling File Installer is not set by default. This
should be fixed. The relevant framework property is {{sling.fileinstall.dir}}.
I propose to set this to {{${sling.launchpad}/installer}})
> Sling File Installer Provider inactive in Sling Starter
> ---
>
> Key: SLING-7504
> URL: https://issues.apache.org/jira/browse/SLING-7504
> Project: Sling
> Issue Type: Improvement
> Components: Launchpad
>Reporter: Konrad Windszus
>Priority: Major
> Fix For: Starter 11
>
>
> Even in the newest Starter 11 the framework property for the Sling File
> Installer is not set by default. This should be fixed. The relevant framework
> property is {{sling.fileinstall.dir}}. I propose to set this to
> {{${sling.launchpad}/install}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (SLING-7504) Sling File Installer Provider inactive in Sling Starter
Konrad Windszus created SLING-7504:
--
Summary: Sling File Installer Provider inactive in Sling Starter
Key: SLING-7504
URL: https://issues.apache.org/jira/browse/SLING-7504
Project: Sling
Issue Type: Improvement
Components: Launchpad
Reporter: Konrad Windszus
Fix For: Starter 11
Even in the newest Starter 11 the framework property for the Sling File
Installer is not set by default. This should be fixed. The relevant framework
property is {{sling.fileinstall.dir}}. I propose to set this to
{{${sling.launchpad}/installer}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (SLING-7503) OSGi Installer Web Console: Error not exposed
Konrad Windszus created SLING-7503: -- Summary: OSGi Installer Web Console: Error not exposed Key: SLING-7503 URL: https://issues.apache.org/jira/browse/SLING-7503 Project: Sling Issue Type: Bug Components: Installer Affects Versions: Installer Console 1.0.2 Reporter: Konrad Windszus Assignee: Konrad Windszus Fix For: Installer Console 1.0.4 The fix from SLING-6176 was supposed to expose the error string of each resource (in case one was set). Unfortunately the column is always empty. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
