And is it possible to automatically trigger a profile based on the requested goal (like jetty:run) ? Let's say, I would have different profiles for different goals. (just to avoid explicitly specifying the profile to use)
On Jan 10, 2008 9:51 PM, simon <[EMAIL PROTECTED]> wrote: > > On Thu, 2008-01-10 at 21:42 +0100, Filipe David Manana wrote: > > Hi, > > > > is it possible to specify that a dependency is always needed for > > compilation, unit testing and plugin execution (jetty plugin) only? That > is, > > it should only not be included in my final WAR archive. > > No. > > But I think you can define it as scope=provided, and then have a > separate profile for running jetty, where it is declared with > scope=runtime. You would then need to run jetty via > mvn -PtheProfileName jetty:run > > Regards, > Simon > > -- Filipe David Manana, [EMAIL PROTECTED] Obvious facts are like secrets to those not trained to see them.
