I've replaced ${project.version} with 1.1-SNAPSHOT. The Release plugin
replaces this with 1.1 during release:prepare and fails with
the same message.
I think the release plugin should first trigger a install on the ejb and
then run the servlet target.2009/3/24 Jörg Schaible <[email protected]> > Martin Eigenbrodt wrote at Dienstag, 24. März 2009 10:16: > > > This may be a beginner question, but I haven't found any hints.. > > I've got a project that contains a servlet and an ejb. The Servlet > depends > > on the ejb. I've trouble releasing that as complete project. > > > > My directory Layout is like: > > > > pom.xml <- package type pom > > servlet > > pom.xml > > ejb > > pom.xml > > > > the parent pom has version 1.1-SNAPSHOT. The Servlet an ejb pom don't > > specify a version (inherit them). > > The Servlet defines a dependecy on the ejb without specifing a version. > > The dependencyMangement section from the parent pom contains: > > <dependencies> > > <dependency> > > <groupId>myGroup<groupId> > > <artifactId>ejb<artifactId> > > <version>${project.version}</version> > > </dependency> > > > > If I try release:prepare the build fails with "Failed to resolve > > artifacts: myGroup:ejb:1.1 > > > > I understand why this happens but is there a obvious solution? How do you > > release multimodule projects with interdependent childs? > > Do not use that property and write the corretc version. The release plugin > will then handle it and adjust it automatically. > > - Jörg > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
