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 2008/02/22 03:36:28 UTC

[jira] Created: (MRM-712) path and filename parsing is unnecessarily complicated

path and filename parsing is unnecessarily complicated
------------------------------------------------------

                 Key: MRM-712
                 URL: http://jira.codehaus.org/browse/MRM-712
             Project: Archiva
          Issue Type: Bug
          Components: repository interface
    Affects Versions: 1.0.2
            Reporter: Brett Porter


The path, filename and version parsing uses a complicated structure to be able to appropriately guess which part of a filename is a version, artifactId, and classifier.

This is needed to be able to effectively proxy and serve maven1 requests where the information is unclear.

However, this code is also used for m2 requests where the format of the filename can be clearly derived from the rest of the path.

I suggest the code be separated into different handlers based on the layout so that the m2 requests can be simplified.

-- 
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-712) path and filename parsing is unnecessarily complicated

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

Brett Porter updated MRM-712:
-----------------------------

    Fix Version/s: 1.1

> path and filename parsing is unnecessarily complicated
> ------------------------------------------------------
>
>                 Key: MRM-712
>                 URL: http://jira.codehaus.org/browse/MRM-712
>             Project: Archiva
>          Issue Type: Bug
>          Components: repository interface
>    Affects Versions: 1.0.2
>            Reporter: Brett Porter
>             Fix For: 1.1
>
>
> The path, filename and version parsing uses a complicated structure to be able to appropriately guess which part of a filename is a version, artifactId, and classifier.
> This is needed to be able to effectively proxy and serve maven1 requests where the information is unclear.
> However, this code is also used for m2 requests where the format of the filename can be clearly derived from the rest of the path.
> I suggest the code be separated into different handlers based on the layout so that the m2 requests can be simplified.

-- 
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-712) path and filename parsing is unnecessarily complicated

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

James William Dumay updated MRM-712:
------------------------------------

    Fix Version/s:     (was: 1.1)
                   1.1.x

Moving to 1.1.x

> path and filename parsing is unnecessarily complicated
> ------------------------------------------------------
>
>                 Key: MRM-712
>                 URL: http://jira.codehaus.org/browse/MRM-712
>             Project: Archiva
>          Issue Type: Bug
>          Components: repository interface
>    Affects Versions: 1.0.2
>            Reporter: Brett Porter
>             Fix For: 1.1.x
>
>
> The path, filename and version parsing uses a complicated structure to be able to appropriately guess which part of a filename is a version, artifactId, and classifier.
> This is needed to be able to effectively proxy and serve maven1 requests where the information is unclear.
> However, this code is also used for m2 requests where the format of the filename can be clearly derived from the rest of the path.
> I suggest the code be separated into different handlers based on the layout so that the m2 requests can be simplified.

-- 
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