Use <relativePath>../pom/pom.xml</relativePath> in your parent
element of POM if this parent POM is somewhere in you checked out source
tree.
- markku
Kristian Nordal wrote:
On 3/14/07, olivier jacob <[EMAIL PROTECTED]> wrote:
On 3/14/07, Kristian Nordal <[EMAIL PROTECTED]> wrote:
>
> Hi
>
> I've noticed that Maven2 uses a file system reference to the parent
POM
-
> if
> the parent POM is located in the directory above. This is causing
problems
> when someone in the team is working on a specific module, but at some
> point
> did a check out of the complete source tree / module hierarchy. New
> snapshots of the parent pom are deployed by Continuum. Is it
possible to
> force maven to always use the snapshots found in the repository
(running
> with -U didn't help) / disabling file system reference to parent?
I think you can deploy your parent POM in your repository. This way, you
won't have to specify the file system reference.
Yes, and Continuum deploys snapshots of the parent. If you only do a
check
out of the single module, it works fine. The problem is when you actually
have the complete source tree / module hierarchy, but is only working
on one
specific module. If the parent pom is in the directory above, it uses
that
POM (which isn't necessarily up-to-date) instead of the one in the
repository. This isn't a major issue, but the developers generally
want to
have the complete source tree - even if they're only working on parts
of it.
--
Cheers,
Kristian
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
