You can try running maven with the -X option an you'll see the
dependency resolution. If you don't find the problem just paste here
the output
On 3/13/06, Mario Ivankovits <[EMAIL PROTECTED]> wrote:
> Hi!
>
> I started using maven 2 to build our project and maybe hit a bug now.
>
> The project layout is:
>
> project
> +-project-app
> +-project-web
>
> where "project-web" depends on "project-app".
>
> One of the dependency is jfreechart which itself depends on e.g. "gnujaxp".
> Now I dont want to package the gnujaxp and so I though I override its
> scope to "provided" in "project-app".
> But "project-web" still package it. Other dependencies defined as
> "provided" work, it looks like its only a problem if a dependency
> declares it.
>
> I worked around this problem by defining the dependency "gnujaxp" in
> "project-web" too as "provided" and not its not packaged any more.
> I think this should not be necessary, no?
>
> Is it my or mavens fault?
>
> Thanks!
> Ciao,
> Mario
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
