maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Bentmann (JIRA)" <>
Subject [jira] Closed: (MDEPLOY-88) Artifacts with invalid id can be deployed with deploy:deploy-file.
Date Thu, 19 Mar 2009 22:59:12 GMT


Benjamin Bentmann closed MDEPLOY-88.

         Assignee: Benjamin Bentmann
       Resolution: Fixed
    Fix Version/s: 2.5

Fixed in [r756247|].

> Artifacts with invalid id can be deployed with deploy:deploy-file.
> ------------------------------------------------------------------
>                 Key: MDEPLOY-88
>                 URL:
>             Project: Maven 2.x Deploy Plugin
>          Issue Type: Bug
>          Components: deploy:deploy-file
>    Affects Versions: 2.4
>            Reporter: Joerg Schaible
>            Assignee: Benjamin Bentmann
>             Fix For: 2.5
> Real world example: WebLogic delivers webserviceclient+ssl.jar.
> It is no problem to create a POM file for this artifact with as "weblogic:webserviceclient+ssl:"
and deploy this with the prepared POM into the repository. It is also no problem to deploy
artifacts with a prepared POM that declare a dependency to this artifact. However, if this
artifact is declared as direct dependency to a project the build fails immediately with :
> {noformat}
> Validation Messages:
>     [0]  'dependencies.dependency.artifactId' with value 'webserviceclient+ssl' does
not match a valid id pattern.
> {noformat}
> and worse, if the artifact is a transitive dep, you only get a non-explaining warning
and all other dependencies of the "transitive artifact" are dropped:
> {noformat}
> [WARNING] POM for '' is invalid. It will be
ignored for artifact resolution. Reason: F
> ailed to validate POM for project at Artifact []
> {noformat}
> The deploy plugin has to validate the (also a generated) POM before deploying an artifact
with deploy:deploy-file.
> BTW: I suppose the install plugin has the same issue with install:install-file. However,
I also suppose the code is shared ;-)

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message