I understand that I need to have a dependency to make sure that the
modules are processed in the proper order. I need to refer to the actual
artifact FILE in the Jetty plugin configuration in order to run the WAR.
This would be the plugin config:
<plugin>
<groupId>org.mortbay.jetty</groupId>
<artifactId>maven-jetty-plugin</artifactId>
<version>6.1.11</version>
<configuration>
<webApp>
<<something refering to the sibling artifact WAR file goes here>>
</webApp>
</configuration>
I guess I can use something like: ../<sibling module
name>/target/<sibling module name>-${project.version}.war
I just figured there must be something better than "hard-coding" that
value in that way.
Thanks,
Dave
Todd Thiessen wrote:
Just added it as a dependency. ie:
<dependency>
<groupId>${project.groupId}</groupId>
<artifactId><sibling artifact ID></artifactId>
<version>${project.version}</version>
<type>jar</type>
<scope>compile</scope>
</dependency>
---
Todd Thiessen
-----Original Message-----
From: David C. Hicks [mailto:[email protected]]
Sent: Friday, February 06, 2009 12:11 PM
To: Maven Users
Subject: Referring to another module's artifact?
I'm sure I'm going to feel stupid when someone tells me how,
but I can't find a way to refer to another module's artifact
from within the same multi-module pom. Specifically, I have
an "integration test" module in which I want to use the Jetty
plugin to run the WAR created by a prior module's build. I
just don't know how to refer to that artifact from one of its
sibling modules. Anyone?
Thanks,
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
