[ 
http://jira.codehaus.org/browse/MASSEMBLY-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

John Casey closed MASSEMBLY-136.
--------------------------------

         Assignee: John Casey
       Resolution: Won't Fix
    Fix Version/s: 2.2-beta-2

This use case isn't really a part of the assembly plugin's goals. Maybe you'd 
be better off with a custom plugin to copy files from dependencies, etc. into 
your tests...

Actually, such a plugin might be really useful. I'm not sure whether the 
maven-remote-resources-plugin could be made to accomplish this (dependencies 
would be remote resources for your tests, after all), but something like that 
would be a nice addition to the mojo.codehaus.org suite of plugins, I'd imagine.

> outputDirectory to support absolute paths
> -----------------------------------------
>
>                 Key: MASSEMBLY-136
>                 URL: http://jira.codehaus.org/browse/MASSEMBLY-136
>             Project: Maven 2.x Assembly Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.0.1
>         Environment: Linux
>            Reporter: Kalle Korhonen
>            Assignee: John Casey
>            Priority: Minor
>             Fix For: 2.2-beta-2
>
>
> Can you please make the assembly parameter "outputDirectory" support absolute 
> paths, just like "directory" in fileSets. Currently all paths are relative to 
> the root directory of the assembly, whether or not you specify the path 
> separator in the beginning or not.  I see no reason why it should only 
> support relative paths.
> I'm using assembly:directory to deploy some resources for my unit/integration 
> tests that are normally available on a production environment. I realize I'm 
> using the plugin "the wrong way", but the directory goal and format isn't 
> suitable for deploying to the repository anyways.
> Also, either I don't know how to use appendAssemblyId correctly or it doesn't 
> work for directory format.

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

        

Reply via email to