Mick Knutson wrote:
You could define another <distributionManagement> in your children. Otherwise, just hard-code your parent artifactId then reference:
I'd really like to understand why this is happening. As I see it, one of the points of parent POMs and parameters is the ability to configure this sort of thing in one place.
in Parent: M:\public_html\maven\project-parent Then reference your children from your Parent as: ./project-1 ./project-2
I've separated aggregation from inheritance, so the parent doesn't refer to children at all. I build them all from within another project, which also inherits the same parent, but declares all of the others as modules.
On Tue, Sep 8, 2009 at 8:40 AM, Sam Barnett-Cormack < [email protected]> wrote:Hi all, I'm a bit confused about the deployment paths used by site:deploy. I have the following in my parent POM: <distributionManagement> <site> <id>mnementh</id> <url>file://M:\public_html\maven\${project.artifactId}</url> </site> </distributionManagement> Now, when the parent POM's site is being generated, it puts it at M:\public_html\maven\parent-name, which is intended. However, for the inheritors (which we'll call project-1 and project-2), I get them at M:\public_html\maven\project-1\project-1 and M:\public_html\maven\project-2\project-2. This is far from handy, and spoils my attempts to define the URLs in the parent using <url>http://shed.geekworld.co.uk/~sdb/maven/${project.artifactId}<http://shed.geekworld.co.uk/%7Esdb/maven/$%7Bproject.artifactId%7D> </url> I'm confused. Can anyone explain? -- Sam Barnett-Cormack --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
-- Sam Barnett-Cormack --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
