Well, if maven can't do what you really need and you don't have time to
customized plugins, you can always use maven + ant (via antrun plugin)
to get what you need.
I suggest that you use ant scripts on simple stuffs like maybe rename
your final packages and such.
Wojciech Biela wrote:
No suggestions? really? anybody? :)
Best regards
Wojtek Biela
2006/6/23, Wojciech Biela <[EMAIL PROTECTED]>:
Hi!
My case was supposed to be simple but it turned out to be quite
complicated, at least for my limited maven abilities, I've used Ant
for the last few years, so I'm new to maven, I've spent a few days
with it, I like it very much, I'm very much convinced that it will
help my project, but I really am starting to loose ground.
I came to this project in it's late stage, so the directory structure
and stuff is not as you would suggest, I am responsible for having a
CI environment, so I'm using luntbuild and would like to use maven to
do the rest...
there are 3 base subprojects and a number of modules:
base1
base2
base3
module1
module2
...
moduleN
each of there subprojects has it's own src,lib,test,resources
structure, and each of them produces one final file. The base modules
produce JAR files, the modules are also compiled (with dep to the
base1-3) and tested and all that's fine and that's fine.
So far I did this by adding another folder let's call it MasterProject
and putting there a pom.xml with packaging type pom, listing all
subprojects as modules, and putting there the common dependencies as
well as configuring the src,test,resources paths as all the
subprojects have it the same way (though not according to your
convention). And all that's fine with a single command from the master
project all the subprojects are compiled, the base projects jars are
installed into the
local repo, modules are unit tested and compiled ..
but the project as a whole is not yet assembled into the structure it
need to have, and I lost the clue of how to do it using maven with the
least effort ... what I have to accomplish is to:
1. take all the jars (external deps, and base subprojects) and put
them into lib folder in the master project - ok I can so that with
assemble plugin AFAIC
2. out of each module make a zip file named XX-moduleN.mod, where XX
is an arbitrary number assigned to the module (eg. in the pom property
element) - that will allow us to sort them in some way - the
application needs that
3. put all the *.mod files into a folder in the master project
4. move the whole thing somewhere (maybe zip and unzip to the dest
location) and lift the whole system (execute some main() from a class
and fork to leave the
I assume that maven wont help me in (4) so I plan to use a custom Ant
script and invoke it after everything is done (bind it to some phase).
But my main question is how to accomplish steps (1)-(3)? I would like
not to build the damn thing all the time and use the Maven repository
as a placeholder for the *.mod files.
But AFAIC I can't force maven to give the jars that he builds a
different extension (.mod) and use the files with that extension as
dependencies for the main project, if I could do that I would simply
use the assembly plugin and tell him to place all the dependencies in
the lib folder, then I would move from the lib folder all the .mod
files to the custom one, I know it isn't flawless but I can't think of
anything else
please enlighten me if I'm wrong or help me if you see any way to do
this
Best regards
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]
