You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Michael Mallete (JIRA)" <ji...@codehaus.org> on 2008/04/08 09:54:58 UTC

[jira] Created: (MRM-768) Cannot configure Legacy Artifact Path Resolution of Non-standard Maven Plugins Path

Cannot configure Legacy Artifact Path Resolution of Non-standard Maven Plugins Path
-----------------------------------------------------------------------------------

                 Key: MRM-768
                 URL: http://jira.codehaus.org/browse/MRM-768
             Project: Archiva
          Issue Type: Bug
         Environment: Linux
            Reporter: Michael Mallete
            Priority: Minor


Legacy Artifact Path Resolution returns error message when configuring a Maven plugin in a Maven 1 repo if direcotry is not under "plugins."

Example:

Artifact location: http://download.java.net/maven/1/com.sun.tools.xjc.maven2/maven-plugins/maven-jaxb-plugin-1.1.jar

Configuration:

Path: com.sun.tools.xjc.maven2/maven-plugins/maven-jaxb-plugin-1.1.jar
GroupId: com.sun.tools.xjc.maven2
ArtifactId: maven-jaxb-plugin
Version: 1.1
Classifier:
Type: maven-plugin

Error message:

artifact reference does not match the initial path : com.sun.tools.xjc.maven2/plugins/maven-jaxb-plugin-1.1.jar


Also, the auto complete feature does not correctly slice the input initially:

ArtifactId: maven
Version: jaxb-plugin-1.1

-- 
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-768) Cannot proxy maven2 plugin (jaxb) from a maven1 repository (http://download.java.net/maven/1)

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

Brett Porter updated MRM-768:
-----------------------------

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

> Cannot proxy maven2 plugin (jaxb) from a maven1 repository (http://download.java.net/maven/1)
> ---------------------------------------------------------------------------------------------
>
>                 Key: MRM-768
>                 URL: http://jira.codehaus.org/browse/MRM-768
>             Project: Archiva
>          Issue Type: Bug
>         Environment: Linux
>            Reporter: Michael Mallete
>            Assignee: nicolas de loof
>            Priority: Minor
>             Fix For: 1.1
>
>
> Legacy Artifact Path Resolution returns error message when configuring a Maven plugin in a Maven 1 repo if direcotry is not under "plugins."
> Example:
> Artifact location: http://download.java.net/maven/1/com.sun.tools.xjc.maven2/maven-plugins/maven-jaxb-plugin-1.1.jar
> Configuration:
> Path: com.sun.tools.xjc.maven2/maven-plugins/maven-jaxb-plugin-1.1.jar
> GroupId: com.sun.tools.xjc.maven2
> ArtifactId: maven-jaxb-plugin
> Version: 1.1
> Classifier:
> Type: maven-plugin
> Error message:
> artifact reference does not match the initial path : com.sun.tools.xjc.maven2/plugins/maven-jaxb-plugin-1.1.jar
> Also, the auto complete feature does not correctly slice the input initially:
> ArtifactId: maven
> Version: jaxb-plugin-1.1

-- 
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-768) Cannot configure Legacy Artifact Path Resolution of Non-standard Maven Plugins Path

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

Brett Porter updated MRM-768:
-----------------------------

    Fix Version/s: 1.0.x

> Cannot configure Legacy Artifact Path Resolution of Non-standard Maven Plugins Path
> -----------------------------------------------------------------------------------
>
>                 Key: MRM-768
>                 URL: http://jira.codehaus.org/browse/MRM-768
>             Project: Archiva
>          Issue Type: Bug
>         Environment: Linux
>            Reporter: Michael Mallete
>            Priority: Minor
>             Fix For: 1.0.x
>
>
> Legacy Artifact Path Resolution returns error message when configuring a Maven plugin in a Maven 1 repo if direcotry is not under "plugins."
> Example:
> Artifact location: http://download.java.net/maven/1/com.sun.tools.xjc.maven2/maven-plugins/maven-jaxb-plugin-1.1.jar
> Configuration:
> Path: com.sun.tools.xjc.maven2/maven-plugins/maven-jaxb-plugin-1.1.jar
> GroupId: com.sun.tools.xjc.maven2
> ArtifactId: maven-jaxb-plugin
> Version: 1.1
> Classifier:
> Type: maven-plugin
> Error message:
> artifact reference does not match the initial path : com.sun.tools.xjc.maven2/plugins/maven-jaxb-plugin-1.1.jar
> Also, the auto complete feature does not correctly slice the input initially:
> ArtifactId: maven
> Version: jaxb-plugin-1.1

-- 
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] Closed: (MRM-768) Cannot configure Legacy Artifact Path Resolution of Non-standard Maven Plugins Path

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

nicolas de loof closed MRM-768.
-------------------------------

      Assignee: nicolas de loof
    Resolution: Fixed

Fixed :
use a distinct "type" for MAVEN_PLUGIN and MAVEN_ONE_PLUGIN
testCase included


> Cannot configure Legacy Artifact Path Resolution of Non-standard Maven Plugins Path
> -----------------------------------------------------------------------------------
>
>                 Key: MRM-768
>                 URL: http://jira.codehaus.org/browse/MRM-768
>             Project: Archiva
>          Issue Type: Bug
>         Environment: Linux
>            Reporter: Michael Mallete
>            Assignee: nicolas de loof
>            Priority: Minor
>             Fix For: 1.0.x
>
>
> Legacy Artifact Path Resolution returns error message when configuring a Maven plugin in a Maven 1 repo if direcotry is not under "plugins."
> Example:
> Artifact location: http://download.java.net/maven/1/com.sun.tools.xjc.maven2/maven-plugins/maven-jaxb-plugin-1.1.jar
> Configuration:
> Path: com.sun.tools.xjc.maven2/maven-plugins/maven-jaxb-plugin-1.1.jar
> GroupId: com.sun.tools.xjc.maven2
> ArtifactId: maven-jaxb-plugin
> Version: 1.1
> Classifier:
> Type: maven-plugin
> Error message:
> artifact reference does not match the initial path : com.sun.tools.xjc.maven2/plugins/maven-jaxb-plugin-1.1.jar
> Also, the auto complete feature does not correctly slice the input initially:
> ArtifactId: maven
> Version: jaxb-plugin-1.1

-- 
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-768) Cannot configure Legacy Artifact Path Resolution of Non-standard Maven Plugins Path

Posted by "nicolas de loof (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MRM-768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=130119#action_130119 ] 

nicolas de loof commented on MRM-768:
-------------------------------------

The issue is not about legacy artifact path support but about legacy-layout support from proxyConnectors.

The requested ArtifactReference is of type "maven-plugin" as we could expect for a m2 plugin request. This is converted in M1 layout to "/plugins/" according to AbstractLegacyRepositoryContent.typeToDirectoryMap

But a m2 maven-plugin project deployed on a legacy-layout repository will use "/maven-plugins/" as configured by maven ArtifactHandler (maven-artifact).

I think we must split the "plugin" type into maven-plugin for M2 plugins and "maven-one-plugin" for M1 plugins (as specified by ArtifactHandler in maven-one-plugin) to avoid such conflicts.

> Cannot configure Legacy Artifact Path Resolution of Non-standard Maven Plugins Path
> -----------------------------------------------------------------------------------
>
>                 Key: MRM-768
>                 URL: http://jira.codehaus.org/browse/MRM-768
>             Project: Archiva
>          Issue Type: Bug
>         Environment: Linux
>            Reporter: Michael Mallete
>            Priority: Minor
>
> Legacy Artifact Path Resolution returns error message when configuring a Maven plugin in a Maven 1 repo if direcotry is not under "plugins."
> Example:
> Artifact location: http://download.java.net/maven/1/com.sun.tools.xjc.maven2/maven-plugins/maven-jaxb-plugin-1.1.jar
> Configuration:
> Path: com.sun.tools.xjc.maven2/maven-plugins/maven-jaxb-plugin-1.1.jar
> GroupId: com.sun.tools.xjc.maven2
> ArtifactId: maven-jaxb-plugin
> Version: 1.1
> Classifier:
> Type: maven-plugin
> Error message:
> artifact reference does not match the initial path : com.sun.tools.xjc.maven2/plugins/maven-jaxb-plugin-1.1.jar
> Also, the auto complete feature does not correctly slice the input initially:
> ArtifactId: maven
> Version: jaxb-plugin-1.1

-- 
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-768) Cannot configure Legacy Artifact Path Resolution of Non-standard Maven Plugins Path

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

Brett Porter commented on MRM-768:
----------------------------------

agreed. Notice this will suffer the same problems as ejbs in that you won't be able to proxy this plugin via an m2 request, you'll have to use the legacy layout the whole way through.

> Cannot configure Legacy Artifact Path Resolution of Non-standard Maven Plugins Path
> -----------------------------------------------------------------------------------
>
>                 Key: MRM-768
>                 URL: http://jira.codehaus.org/browse/MRM-768
>             Project: Archiva
>          Issue Type: Bug
>         Environment: Linux
>            Reporter: Michael Mallete
>            Priority: Minor
>
> Legacy Artifact Path Resolution returns error message when configuring a Maven plugin in a Maven 1 repo if direcotry is not under "plugins."
> Example:
> Artifact location: http://download.java.net/maven/1/com.sun.tools.xjc.maven2/maven-plugins/maven-jaxb-plugin-1.1.jar
> Configuration:
> Path: com.sun.tools.xjc.maven2/maven-plugins/maven-jaxb-plugin-1.1.jar
> GroupId: com.sun.tools.xjc.maven2
> ArtifactId: maven-jaxb-plugin
> Version: 1.1
> Classifier:
> Type: maven-plugin
> Error message:
> artifact reference does not match the initial path : com.sun.tools.xjc.maven2/plugins/maven-jaxb-plugin-1.1.jar
> Also, the auto complete feature does not correctly slice the input initially:
> ArtifactId: maven
> Version: jaxb-plugin-1.1

-- 
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-768) Cannot proxy maven2 plugin (jaxb) from a maven1 repository (http://download.java.net/maven/1)

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

nicolas de loof updated MRM-768:
--------------------------------

    Summary: Cannot proxy maven2 plugin (jaxb) from a maven1 repository (http://download.java.net/maven/1)  (was: Cannot configure Legacy Artifact Path Resolution of Non-standard Maven Plugins Path)

> Cannot proxy maven2 plugin (jaxb) from a maven1 repository (http://download.java.net/maven/1)
> ---------------------------------------------------------------------------------------------
>
>                 Key: MRM-768
>                 URL: http://jira.codehaus.org/browse/MRM-768
>             Project: Archiva
>          Issue Type: Bug
>         Environment: Linux
>            Reporter: Michael Mallete
>            Assignee: nicolas de loof
>            Priority: Minor
>             Fix For: 1.0.x
>
>
> Legacy Artifact Path Resolution returns error message when configuring a Maven plugin in a Maven 1 repo if direcotry is not under "plugins."
> Example:
> Artifact location: http://download.java.net/maven/1/com.sun.tools.xjc.maven2/maven-plugins/maven-jaxb-plugin-1.1.jar
> Configuration:
> Path: com.sun.tools.xjc.maven2/maven-plugins/maven-jaxb-plugin-1.1.jar
> GroupId: com.sun.tools.xjc.maven2
> ArtifactId: maven-jaxb-plugin
> Version: 1.1
> Classifier:
> Type: maven-plugin
> Error message:
> artifact reference does not match the initial path : com.sun.tools.xjc.maven2/plugins/maven-jaxb-plugin-1.1.jar
> Also, the auto complete feature does not correctly slice the input initially:
> ArtifactId: maven
> Version: jaxb-plugin-1.1

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