Re: assembly - renaming files
I just found time to get back to that.
I think you misunderstood. I already do package the submodules and
install them to the local repository and would like to reach them from
the master module. At that point I don't have to use the dependency
plugin, the default package phase suffices. My problem is that as soon
as I install the package (or attached artifact) I loose the prefix I
added to it's name.
That's why I said I feel there is no such way and I just have to use
in the master module the dependency:copy and repeat the artifactItem
element for every submodule's artifact I need to download and assign
those prefixes in the master module pom (instead from the submodule's
poms)
any insight into that? or am I missing something?
-Wojtek
2006/7/5, dan tran [EMAIL PROTECTED]:
I you need to repeating bunch of dependecy:copy execution in a submodules,
I's suggest that
delegate a maven to prepare that stagement area and aother other projects
can directly reference
it via relative path, or via local repository ( get that maven project to
assemable a zip file that
other modules can unpack )
-Dan
On 7/5/06, Wojciech Biela [EMAIL PROTECTED] wrote:
hmmm, true, true, thank you Dan!, I missed that, I feel I must go home
and take a rest ;) ... , anyway still that leaves me with the question
of how to reach that arbitrary prefix assigned in the pom file of that
dependency?
I feel there is no such way and I just have to use the dependency:copy
and repeat the artifactItem element for every submodule and assign
those prefixes in the master module pom (instead from the submodule's
poms)
sorry if all this is basic stuff, but I'm very new to maven
best regards
Wojtek
2006/7/5, dan tran [EMAIL PROTECTED]:
dependency:copy allows you to rename the artifact, check out
ArtifactItem
javadoc
-D
On 7/5/06, Wojciech Biela [EMAIL PROTECTED] wrote:
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
typemod/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
outputDirectorylib/outputDirectory
/dependencySet
dependencySet
outputDirectorymodules/outputDirectory
/dependencySet
/dependencySets
puts all dependencies into both dirs
any insight is welcome
Best regards,
--
Wojtek Biela
Re: assembly - renaming files
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
typemod/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
outputDirectorylib/outputDirectory
/dependencySet
dependencySet
outputDirectorymodules/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]
Re: assembly - renaming files
Regarding my first and major problem, at first I thought that changing
the finalName to finalName123-${artifactId}-${version}/finalName
would add the prefix, but I see that this only controlls the name of
the *local* artifact, not the artifact that is installed in the
repository, and then at a later step downloaded as a dependency by the
master module. Anyway I struggle to add this prefix before installing
to the repo, or just after the dependencies download, but I can't seem
to find a way to do it.
Wojtek
2006/7/5, Wojciech Biela [EMAIL PROTECTED]:
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
typemod/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
outputDirectorylib/outputDirectory
/dependencySet
dependencySet
outputDirectorymodules/outputDirectory
/dependencySet
/dependencySets
puts all dependencies into both dirs
any insight is welcome
Best regards,
--
Wojtek Biela
--
Wojtek Biela
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: assembly - renaming files
Dan, Could you please point me to a location of any documentation on
this matter or tell me how to use it to prep the work? Because a quick
google for maven-dependency-plugin didn't reveal *any* insight in
this matter ...
TIA!
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
typemod/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
outputDirectorylib/outputDirectory
/dependencySet
dependencySet
outputDirectorymodules/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]
RE: assembly - renaming files
Here's a link -
http://mojo.codehaus.org/dependency-maven-plugin/introduction.html
Unfortunately, I haven't used it yet myself, so I can't offer any tips.
Ian
| -Original Message-
| From: Wojciech Biela [mailto:[EMAIL PROTECTED]
| Sent: Wednesday, July 05, 2006 11:08 AM
| To: Maven Users List
| Subject: Re: assembly - renaming files
|
| Dan, Could you please point me to a location of any documentation on
| this matter or tell me how to use it to prep the work? Because a quick
| google for maven-dependency-plugin didn't reveal *any* insight in
| this matter ...
|
| TIA!
| 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
| typemod/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
| outputDirectorylib/outputDirectory
| /dependencySet
| dependencySet
| outputDirectorymodules/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]
|
|
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: assembly - renaming files
Ha! I know why google didn't find anything googling for
dependency-maven-plugin truly finds this link you mention, thank you
very much Ian, I'll look into it
any tips are still more than welcome
Wojtek
2006/7/5, Ian Springer [EMAIL PROTECTED]:
Here's a link -
http://mojo.codehaus.org/dependency-maven-plugin/introduction.html
Unfortunately, I haven't used it yet myself, so I can't offer any tips.
Ian
| -Original Message-
| From: Wojciech Biela [mailto:[EMAIL PROTECTED]
| Sent: Wednesday, July 05, 2006 11:08 AM
| To: Maven Users List
| Subject: Re: assembly - renaming files
|
| Dan, Could you please point me to a location of any documentation on
| this matter or tell me how to use it to prep the work? Because a quick
| google for maven-dependency-plugin didn't reveal *any* insight in
| this matter ...
|
| TIA!
| 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
| typemod/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
| outputDirectorylib/outputDirectory
| /dependencySet
| dependencySet
| outputDirectorymodules/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]
|
|
-
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]
Re: assembly - renaming files
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
typemod/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
outputDirectorylib/outputDirectory
/dependencySet
dependencySet
outputDirectorymodules/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]
Re: assembly - renaming files
dependency:copy allows you to rename the artifact, check out ArtifactItem
javadoc
-D
On 7/5/06, Wojciech Biela [EMAIL PROTECTED] wrote:
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
typemod/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
outputDirectorylib/outputDirectory
/dependencySet
dependencySet
outputDirectorymodules/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]
Re: assembly - renaming files
hmmm, true, true, thank you Dan!, I missed that, I feel I must go home
and take a rest ;) ... , anyway still that leaves me with the question
of how to reach that arbitrary prefix assigned in the pom file of that
dependency?
I feel there is no such way and I just have to use the dependency:copy
and repeat the artifactItem element for every submodule and assign
those prefixes in the master module pom (instead from the submodule's
poms)
sorry if all this is basic stuff, but I'm very new to maven
best regards
Wojtek
2006/7/5, dan tran [EMAIL PROTECTED]:
dependency:copy allows you to rename the artifact, check out ArtifactItem
javadoc
-D
On 7/5/06, Wojciech Biela [EMAIL PROTECTED] wrote:
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
typemod/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
outputDirectorylib/outputDirectory
/dependencySet
dependencySet
outputDirectorymodules/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]
--
Wojtek Biela
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: assembly - renaming files
I you need to repeating bunch of dependecy:copy execution in a submodules,
I's suggest that
delegate a maven to prepare that stagement area and aother other projects
can directly reference
it via relative path, or via local repository ( get that maven project to
assemable a zip file that
other modules can unpack )
-Dan
On 7/5/06, Wojciech Biela [EMAIL PROTECTED] wrote:
hmmm, true, true, thank you Dan!, I missed that, I feel I must go home
and take a rest ;) ... , anyway still that leaves me with the question
of how to reach that arbitrary prefix assigned in the pom file of that
dependency?
I feel there is no such way and I just have to use the dependency:copy
and repeat the artifactItem element for every submodule and assign
those prefixes in the master module pom (instead from the submodule's
poms)
sorry if all this is basic stuff, but I'm very new to maven
best regards
Wojtek
2006/7/5, dan tran [EMAIL PROTECTED]:
dependency:copy allows you to rename the artifact, check out
ArtifactItem
javadoc
-D
On 7/5/06, Wojciech Biela [EMAIL PROTECTED] wrote:
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
typemod/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
outputDirectorylib/outputDirectory
/dependencySet
dependencySet
outputDirectorymodules/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]
--
Wojtek Biela
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
