May I add, that when maven already downloaded a poor/invalid pom, even
after fixing the pom in the repository, maven won't know that it's
changed (unless the version changed) and it will not download it. So
you end up still using your local repo copy.
To re-download a pom, you have to delet
> -Original Message-
> From: Kenney Westerhof [mailto:[EMAIL PROTECTED]
> Sent: Saturday, July 01, 2006 2:59 PM
> To: Maven Developers List
> Subject: RE: [RANT] This Maven thing is killing us
>
>
> > Perhaps we can have a rule that every dependency MUST have
> a declared
> > and
On Fri, 30 Jun 2006, Mike Perham wrote:
> Maybe we need a much harsher line around the quality of accepted POMs.
Maybe that's wise.
> Perhaps we can have a rule that every dependency MUST have a declared
> and element so that we know the developer has thought
> about the correct values for t
Hi all,
unfortunately [MWAR-38] is not fully fixed - It still does not work in a
multi-module build.
We do have here the following structure:
root
jarmodule
ejb
webapp
Running a "mvn package" inside the webapp module, the EJB-Client jar from
the ejb module is resolved correctl
On 6/30/06, Mike Perham <[EMAIL PROTECTED]> wrote:
"I'll spare you the details on that one"
This does nothing to solve the problem. We can't fix what we don't know
about...
Sorry about that, if was meaning to write to the Maven list with more
precise information later, my email was meant for
