OK, I looked into the docs for the dependency-maven-plugin and
unfortunately didn't find anything of use in my situation.
Dan if you would be so kind and elaborate a little on how I could do
it with this plugin I would be truly grateful.
I don't see how the dependency:copy-dependencies or dependency:copy
goal may help me change the names of those artifacts, the only thing
that they allow me to do is strip the version number. I need to change
the destination file name, and assign a prefix different, arbitrary
and characteristic for each submodule.
Maybe I need to write my own Mojo for that task, but I'm still not
sure whether I'll be able to reach the dependencies' pom definition
from the point just before assembly of the master project. In the pom
I wanted to place the arbitrary prefix characteristic for each of the
submodules.
Maybe the only way I can do this is by repeating the dependencies in
some other file and assigning there the prefixes and then reach that
file from my Mojo, or Ant task or something of that sort .. ?
please help, I'm lost
Wojtek
2006/7/5, dan tran <[EMAIL PROTECTED]>:
You need the help form maven-dependency-plugin to prep the work
before assembly started.
-D
On 7/5/06, Wojciech Biela <[EMAIL PROTECTED]> wrote:
>
> Hello,
>
> I refined my problem and now it comes down to this:
>
> I have my submodules installed in the repository as my custom type
> "mod", I did this through "attach-artifacts" and added
> <artifact>
> <file>${project.build.directory}/${project.build.finalName}.jar</file>
> <type>mod</type>
> </artifact>
>
> now in the main project I set the dependencies to those modules with
> the type "mod". There are two issues however:
>
> 1. (major) I would like to assign an arbitrary prefix to every "mod"
> type dependency. I figured already that I can't change the name of the
> file in the repository to anything else than artifactId-version, so I
> wonder what else can I do to achieve it. I would like not to duplicate
> any information anywhere, so I thought I would put a parameter in
> every module's pom file and I would access it through ${} during
> assembly and then use the outputFileNameMapping to change the name of
> every mod file. But the problem as I see it is that I can't access the
> dependencies pom file at the moment of assembly.
>
> Do you have any insight into how to do it in a clean way? if not clean
> then maybe the least messy way?
>
> 2. (minor) I would like to assemble all "jar" type dependencies into
> one folder, and "mod" type dependencies to another. currently
> <dependencySets>
> <dependencySet>
> <outputDirectory>lib</outputDirectory>
> </dependencySet>
> <dependencySet>
> <outputDirectory>modules</outputDirectory>
> </dependencySet>
> </dependencySets>
> puts all dependencies into both dirs
>
> any insight is welcome
>
> Best regards,
> --
> Wojtek Biela
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Wojtek Biela
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
