I don't understand the question. If you didn't define a version in the pom for lawnet-web-core, then there's no version defined. This is invalid and the response you got was what I would expect.
You need to define a version in your modules. They're not definitively tied to the parent project in any way other than by reference. On 7/10/06, Alex Shneyderman <[EMAIL PROTECTED]> wrote:
> Do the module lawnet-web-core's pom.xml defines a parent ? > if no, it must define a version. the question is why? Say I have a bunch of modules, that always get built and versioned together, hence the aggregator. The aggregator assigns version to all the modules at a the time of build. I would think it is a valid use case, no? > PS : i haven't find a link to a doc explaining the multi modules builds with > parents. well there is an example in BBWM book, but details are sketchy I agree. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Never wear anything that panics the cat. -- P. J. O'Rourke
