I actually solved my 3 questions, so I will give my solutions hereunder
if anyone is also interested:
1) See this page from maven-war-plugin:
http://maven.apache.org/plugins/maven-war-plugin/examples/skinny-wars.html
If config element doesn't work, just use
as indicated for deprecated vers
> 3) I tried to set the "inherited" element to 'false', but it seems
> assembly for modules still occurs... any idea why this is the case?
Never mind that, I actually set the element at the
level, and now the assembly won't occur for modules, as desired...
BR,
Olivier
--
Thanks Samuel,
>> 1) How to prevent WAR plugin from putting each war's dependent JARs
into the
>> myappX.war:WEB-INF/lib ?
>
> 1 - Use the "provided" scope for all your war dependencies, see
>
http://maven.apache.org/ref/current/maven-model/maven.html#class_dependency
> and
http://maven.apach
Hi Olivier,
I don't have the answer to all your questions but I believe I can help
with questions 1 & 2:
1 - Use the "provided" scope for all your war dependencies, see
http://maven.apache.org/ref/current/maven-model/maven.html#class_dependency
and
http://maven.apache.org/guides/introduction/int
Hi everyone,
I have a multi-module project as follows:
my_project
|
+- myapp1 (war)
|
+- myapp2 (war)
|
+- myutils (jar)
I want to assemble "my_project" as follows:
my_project.zip
|
+- applications/
| |
| +- myapp1.war
| |
| +- myapp2.war
|
+- lib/
|
+- myutils.jar
|
+- *.jar (JAR
