Personally, I would just change the artifactId. Perhaps name them module1_app and modules2_app or something.
Wayne On 3/1/07, Thorsten Heit <[EMAIL PROTECTED]> wrote:
Hello Maven experts, I'm trying to create a Jar that depends on a couple of internally generated modules. All dependencies have different groupId, but some of them come from multi-module build and have the same artifactId. Example: * <module1>/main +-- app +-- resources * <module2>/main +-- app +-- resources ... I'm referencing them in my main application the normal way, i.e. <dependency> <groupId>module1</groupId> <artifactId>app</groupId> <version>1.0-SNAPSHOT</version> </dependency> <dependency> <groupId>module2</groupId> <artifactId>app</groupId> <version>1.0-SNAPSHOT</version> </dependency> Compiling the code and generating reports works as expected; I only have one issue with the jar: Maven creates duplicate entries "app-1.0-SNAPSHOT.jar" in the "Class-Path" section in the manifest file because it obviously only uses the artifact names without their group Id. Is there a way to avoid this? Or do I have to change these artifactId's? Cheers Thorsten --------------------------------------------------------------------- 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]
