You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2010/05/04 07:12:12 UTC

[jira] Created: (MRM-1382) migrate repository converter to new repository API

migrate repository converter to new repository API
--------------------------------------------------

                 Key: MRM-1382
                 URL: http://jira.codehaus.org/browse/MRM-1382
             Project: Archiva
          Issue Type: Task
          Components: repository converter
    Affects Versions: 1.4
            Reporter: Brett Porter


the use of repository-layer and model need to be removed.

In the process, the role of the repository converter module may need to be revisited. Currently it is only for maven 1 -> maven 2 conversion. This may be of limited utility to retain, depending on the complexity of retaining it. It may also be better stored in maven 1.x plugin (ie, it would be 1.x -> metadata repository rather than a specific 1.x -> 2.x conversion to support other formats), or there may be a desire to have a more generalised conversion utility with hooks for repository specifics.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (MRM-1382) migrate repository converter to new repository API

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MRM-1382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=219815#action_219815 ] 

Brett Porter commented on MRM-1382:
-----------------------------------

uses of the old APIs are limited but used a lot:
- ManagedRepositoryContent / RepositoryContentFactory is used to get the comparative layouts and can be migrated to the new API
- ArtifactRefence for paths in LCAC

> migrate repository converter to new repository API
> --------------------------------------------------
>
>                 Key: MRM-1382
>                 URL: http://jira.codehaus.org/browse/MRM-1382
>             Project: Archiva
>          Issue Type: Task
>          Components: repository converter
>    Affects Versions: 1.4
>            Reporter: Brett Porter
>             Fix For: Backlog
>
>
> the use of repository-layer and model need to be removed.
> In the process, the role of the repository converter module may need to be revisited. Currently it is only for maven 1 -> maven 2 conversion. This may be of limited utility to retain, depending on the complexity of retaining it. It may also be better stored in maven 1.x plugin (ie, it would be 1.x -> metadata repository rather than a specific 1.x -> 2.x conversion to support other formats), or there may be a desire to have a more generalised conversion utility with hooks for repository specifics.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Updated: (MRM-1382) migrate repository converter to new repository API

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MRM-1382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated MRM-1382:
------------------------------

    Fix Version/s: Backlog

> migrate repository converter to new repository API
> --------------------------------------------------
>
>                 Key: MRM-1382
>                 URL: http://jira.codehaus.org/browse/MRM-1382
>             Project: Archiva
>          Issue Type: Task
>          Components: repository converter
>    Affects Versions: 1.4
>            Reporter: Brett Porter
>             Fix For: Backlog
>
>
> the use of repository-layer and model need to be removed.
> In the process, the role of the repository converter module may need to be revisited. Currently it is only for maven 1 -> maven 2 conversion. This may be of limited utility to retain, depending on the complexity of retaining it. It may also be better stored in maven 1.x plugin (ie, it would be 1.x -> metadata repository rather than a specific 1.x -> 2.x conversion to support other formats), or there may be a desire to have a more generalised conversion utility with hooks for repository specifics.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira