You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Luc Willems (JIRA)" <ji...@codehaus.org> on 2008/11/25 11:49:19 UTC

[jira] Created: (MDEP-190) add useProjectArtifact option like assembly plugin during copy-dependency goal

add useProjectArtifact option like assembly plugin during copy-dependency goal
------------------------------------------------------------------------------

                 Key: MDEP-190
                 URL: http://jira.codehaus.org/browse/MDEP-190
             Project: Maven 2.x Dependency Plugin
          Issue Type: Improvement
          Components: copy-dependencies
         Environment: Linux / Mavane2.0.9
            Reporter: Luc Willems
            Assignee: Brian Fox


I'm using copy-dependency goal to copy all depenencies to  target/lib to have them available for Jruby scripts.
the jar files are stripped from there version numbers.

The project is a mix Java/Ruby project. the build Java artifact is NOT copy by the copy dependencies.

The assembly plugin has a useProjectArtifact options that will also copy the build artifact into the assembly.
copy-depenencies should also be able to copy the project build jar so that the list of jars is complete.

note : i tried using this config with a second copy goal but this will not include the LATEST build jar but the LATEST in my local repository
because install is run after package and this copy goal was run during package

           <configuration>
                 <stripVersion>true</stripVersion>
                 <outputDirectory>target/lib</outputDirectory>
                 <artifactItems>
                         <artifactItem>
                                 <groupId>${project.groupId}</groupId>
                                 <artifactId>${project.artifactId}</artifactId>
                         </artifactItem>
              </artifactItems>
             </configuration>



-- 
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: (MDEP-190) add useProjectArtifact option like assembly plugin during copy-dependency goal

Posted by "Luc Willems (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MDEP-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=155343#action_155343 ] 

Luc Willems commented on MDEP-190:
----------------------------------

additional notes :
according to http://maven.apache.org/plugins/maven-dependency-plugin/examples/copying-artifacts.html
we can use copy goal. but this is run during the install phaze (after the artifact is installed in local repo).

I' can't use this because after copy-dependencies , we use assembly to create a zip file with all libraries and scripts for distribution.
this zip file must include all jar files , version stripped from the filename , so that the script can use these jar files

the assembly plugin doesn't strip versions, so we use copy-dependencies to do that. the zip file must include the latest build artifact.






> add useProjectArtifact option like assembly plugin during copy-dependency goal
> ------------------------------------------------------------------------------
>
>                 Key: MDEP-190
>                 URL: http://jira.codehaus.org/browse/MDEP-190
>             Project: Maven 2.x Dependency Plugin
>          Issue Type: Improvement
>          Components: copy-dependencies
>         Environment: Linux / Mavane2.0.9
>            Reporter: Luc Willems
>            Assignee: Brian Fox
>
> I'm using copy-dependency goal to copy all depenencies to  target/lib to have them available for Jruby scripts.
> the jar files are stripped from there version numbers.
> The project is a mix Java/Ruby project. the build Java artifact is NOT copy by the copy dependencies.
> The assembly plugin has a useProjectArtifact options that will also copy the build artifact into the assembly.
> copy-depenencies should also be able to copy the project build jar so that the list of jars is complete.
> note : i tried using this config with a second copy goal but this will not include the LATEST build jar but the LATEST in my local repository
> because install is run after package and this copy goal was run during package
>            <configuration>
>                  <stripVersion>true</stripVersion>
>                  <outputDirectory>target/lib</outputDirectory>
>                  <artifactItems>
>                          <artifactItem>
>                                  <groupId>${project.groupId}</groupId>
>                                  <artifactId>${project.artifactId}</artifactId>
>                          </artifactItem>
>               </artifactItems>
>              </configuration>

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