You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Robert Munteanu (JIRA)" <ji...@apache.org> on 2016/12/05 16:30:58 UTC

[jira] [Updated] (SLING-6365) JcrInstaller incorrectly uses loginService arguments

     [ https://issues.apache.org/jira/browse/SLING-6365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Munteanu updated SLING-6365:
-----------------------------------
    Description: 
As [~andrei.dulvac] pointed out on SLING-5228, my changes use the 'subsystem name' and 'workspace' parameters inconsistently. This works because the arguments are always (null, null), as we no longer have workspaces with Oak.

However, we should make sure the arguments are always used correctly.

  was:
As [~andrei.dulvac] pointed on out SLING-5228, my changes use the 'subsystem name' and 'workspace' parameters inconsistently. This works because the arguments are always (null, null), as we no longer have workspaces with Oak.

However, we should make sure the arguments are always used correctly.


> JcrInstaller incorrectly uses loginService arguments
> ----------------------------------------------------
>
>                 Key: SLING-6365
>                 URL: https://issues.apache.org/jira/browse/SLING-6365
>             Project: Sling
>          Issue Type: Bug
>          Components: Installer
>    Affects Versions: JCR Installer 3.1.20
>            Reporter: Robert Munteanu
>            Assignee: Robert Munteanu
>            Priority: Minor
>             Fix For: JCR Installer 3.1.22
>
>
> As [~andrei.dulvac] pointed out on SLING-5228, my changes use the 'subsystem name' and 'workspace' parameters inconsistently. This works because the arguments are always (null, null), as we no longer have workspaces with Oak.
> However, we should make sure the arguments are always used correctly.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)