You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by ji...@codehaus.org on 2004/09/09 21:05:44 UTC

[jira] Commented: (MPARTIFACT-35) artifact goals should allow different names

The following comment has been added to this issue:

     Author: Neil Crow
    Created: Thu, 9 Sep 2004 7:42 AM
       Body:
There is a similar problem with ejb:client-install,
that name of the client-artifact generated in the target directory is changed when the client-artifact is installed.
And I assume that the problem will be the same with
ejb:client-deploy.

I would be wary of using "jar" for the override,
as this implies type which would already have been set by the goal being called. i.e. jar:install / war:install / ejb:install etc.

The types are being set correctly, it is only the name of the artifact that is being overridden by the ${pom.artifactId}.
---------------------------------------------------------------------
View this comment:
  http://jira.codehaus.org/browse/MPARTIFACT-35?page=comments#action_23925

---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/browse/MPARTIFACT-35

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MPARTIFACT-35
    Summary: artifact goals should allow different names
       Type: Improvement

     Status: Unassigned
   Priority: Major

 Original Estimate: 3 hours
 Time Spent: Unknown
  Remaining: 3 hours

    Project: maven-artifact-plugin
   Versions:
             1.5

   Assignee: 
   Reporter: Felipe Leme

    Created: Sun, 1 Aug 2004 9:22 PM
    Updated: Thu, 9 Sep 2004 7:42 AM

Description:
It would be nice it <artifact> tags allows us to change the name of the artifact being installed/deployed. That wuold be really helpful when your project has 'secondary artifacts', like javadoc, zip files or a simple war with documents.

For instance, when you call javadoc:install, a jar file is created at target (PROJECT-version_javadoc.jar) but that file is installed as a .javadoc, even though the call to <artifact:install> uses the same name as the existing article on target:


<artifact:install
        artifact="${maven.javadoc.final.name}"
        type="javadoc"
        project="${pom}"/> 

In other, it would be nice if artifact:install (and deploy, deploysnaspshot, etc...) used the name passed on the artifact attribute (instead of always using ${pom.artifactId}-version.${type}.

Felipe



---------------------------------------------------------------------
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org