You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2010/08/16 15:46:16 UTC

[jira] Resolved: (SLING-1650) Move commons auth to another location

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

Felix Meschberger resolved SLING-1650.
--------------------------------------

    Resolution: Fixed

I consider this move complete, integration tests pass, forms render. All looks nice and cozy.

> Move commons auth to another location
> -------------------------------------
>
>                 Key: SLING-1650
>                 URL: https://issues.apache.org/jira/browse/SLING-1650
>             Project: Sling
>          Issue Type: Task
>          Components: Commons
>    Affects Versions: Auth Core 1.0.0
>            Reporter: Carsten Ziegeler
>            Assignee: Felix Meschberger
>             Fix For: OpenID Authentication 1.0.0, Form Based Authentication 1.0.0, Auth Core 1.0.0
>
>
> As the commons auth uses the Sling API it is by definition no commons module :)
> To move the different authentication related parts together, the following structure is created:
>     bundles/auth -- New Component, reflected in JIRA as the "Authentication" component
>     commons/auth -- moved to bundles/auth/core and then the core authentication bundle
>     extensions/formauth -- moved to bundles/auth/form
>     extensions/openidauth -- moved to bundles/auth/openid

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.