Well, okay, I read that instruction.
But I may also need to have a WAR artifact including all dependent EJBs in
case I want to deploy it as WAR only, no EAR.
In this case I still need to preserve original WAR dependencies.
And I need m-ear-p to strip them if they're a listed as EAR dependencies
(when I configure m-ear-p to produce "skinnyWar" modules).
This doesn't really work.
Whatever jar dependencies I have in my EAR artifact get
stripped from the WAR.
But no ejb EAR dependencies get stripped from WAR.
And I can't do a jar on them because I will loose the
capability (to generate proper application.xml).
I guess, there was something in mind when making m-ear-p to skip those
ejb dependencies when stripping down WAR artifact.
--
View this message in context:
http://maven.40175.n5.nabble.com/Ear-Plugin-skinnyWars-EJB-problem-tp563p5723616.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
