On Mon, May 3, 2010 at 12:37 PM, Frank Maritato <
fmarit...@attinteractive.com> wrote:
> Hi,
>
> I have a multi module project and in my top level pom I am using a property
> to define the version number like this:
>
> <version>${myproject.version}</version>
>
> <properties>
> <myproject.version>0.1</myproject.version>
> </properties>
>
> All my submodules inherit from this pom and all define <version> the same
> way. Within the context of this project it all works and everything is cool.
> The problem I have is when I try to import one of these libraries into
> another project I get an error that it can't resolve the parent of my
> dependency because it isn't resolving that property value.
> When I look in my .m2/repository directory at the pom for that project it
> still has the unresolved ${myproject.version} string in there. I have tried
> defining that property in the other project that is importing that
> dependency but it still doesn't work.
>
> Is this not the way we should define our project? Should we just use
> explicit version numbers in our pom's?
>
Yes.
>
> --
> Frank Maritato
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
