The following comment has been added to this issue:

     Author: Sean Timm
    Created: Fri, 17 Oct 2003 4:48 PM
       Body:
I'm new around here, too, but from what I can tell Shaposhnikov Konstantin is 
absolutely correct.  This needs to be addressed via utilizing the 
maven-artifact-plugin and its deployment mechanism.  That way people can take 
advantage of other ways of deploying the JARs besides just scp.  I'm surprised this 
issue is going to wait until 1.1...guess I'll have to try and fix it myself.
---------------------------------------------------------------------
View the issue:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-373


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MAVEN-373
    Summary: Incorrect arguments in jar:deploy and jar:deploy-snapshot
       Type: Bug

     Status: Unassigned
   Priority: Major

 Time Spent: Unknown
  Remaining: Unknown

    Project: maven
 Components: 
             plugin-java
   Fix Fors:
             1.1
   Versions:
             1.0-beta-9

   Assignee: 
   Reporter: Aslak Hellesoy

    Created: Fri, 4 Apr 2003 6:31 AM
    Updated: Mon, 4 Aug 2003 11:26 AM

Description:
The jar:deploy and jar:deploy-snapshot goals are doing some fancy and unnecessary 
string manipulations to find the relative file name of the jar file to deploy.

This is unnecessary (the file name of the jars can be absolute), and furhter, it 
doesn't work when ${maven.build.dir} is overridden to point outside the project.

Further, the jar:deploy-snapshot could just call the jar:deploy goal (and avoid 
copy-paste of identical logic).

The mentioned goals should be simplified as follows:

  <!-- ================================================================== -->
  <!-- D E P L O Y  S N A P S H O T                                       -->
  <!-- ================================================================== -->

  <goal
    name="jar:deploy-snapshot"
    description="Deploy a snapshot jar to the remote repository">

    <m:user-check user="${maven.username}"/>
    <attainGoal name="jar:snapshot"/>
    <attainGoal name="jar:deploy"/>
                    
  </goal>

  <!-- ================================================================== -->
  <!-- D E P L O Y  J A R                                                 -->
  <!-- ================================================================== -->

  <goal
    name="jar:deploy"
    description="Deploy a jar to the remote repository">

    <m:user-check user="${maven.username}"/>
    <attainGoal name="java:jar"/>
    <ant:property name="maven.jar.to.deploy" value="${maven.final.name}.jar"/>
    <deploy:artifact
      artifact="${maven.final.name}.jar"
      type="jars"
      assureDirectoryCommand="mkdir -p"
      siteCommand="cd @deployDirectory@; chmod g+w ${maven.jar.to.deploy}; chgrp maven 
${maven.jar.to.deploy}"
    />

  </goal>



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