Message:

   The following issue has been closed.

   Resolver: Brett Porter
       Date: Wed, 23 Jun 2004 9:59 AM

this is now fixed - you can provide a custom handler to map to a different path. See 
the dist plugin for an example.
---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/browse/MPARTIFACT-7

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MPARTIFACT-7
    Summary: Deploy an special artifact  (like maven plugins)
       Type: Improvement

     Status: Closed
   Priority: Major
 Resolution: DUPLICATE

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: maven-artifact-plugin
   Versions:
             1.1

   Assignee: 
   Reporter: Emmanuel Boudrant

    Created: Tue, 6 Jan 2004 7:34 AM
    Updated: Wed, 23 Jun 2004 9:59 AM

Description:
When we want deploy a maven plugin with artifact:deploy there is a problem. The type 
compute the directory (jars) and the archive extension. The problem appear when the 
directory is different from the extendion, typically for a maven plugin : type is 
"plugin" but extension is "jar".

I think it will be usefull to add an optionnal attribute in artifact tags like :

<artifact:deploy 
        artifact="${maven.build.dir}/${maven.final.name}.jar" 
        project="${pom}" 
        type="plugin"
        extension="jar"/>

Thx,
-emmanuel


---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to