IIUC The assembly plugin is used to build distributable artifacts, such as zips containing your project, documentation, installation scripts, run scripts etc. It is not intended to be put into a repository.
Maven only allows one artifact (the result of building your module) per project/module. This is either a jar, war, ejb-jar, or ear. A project/module cannot produce both a jar and a war. That is why the packaging element is in your pom. Now the second part of your question: what /is/ your second artifact used for? Why do you want to produce a second artifact type from your project/module? Martijn On 7/11/06, Jörg Schaible <[EMAIL PROTECTED]> wrote:
Hi folks, even after reading available docs (mini-howto's and plugin docs) I still don't know awhat I am missing: In a module I've created a second artifact with a different classifier usilizing the assembly plugin. The artifact's type seems to be the assembly's id and the file extension (zip) is also defined in the assembly.xml. Now, how can I refer this artifact in another module? Basically I wanna unpack the zip file and add it as resource to my module. But if I add this artifact as dependency with its type, the artifact cannot be found. Somehow I must still miss something in the picture what the assembly plugin produces and the differences between a classifier and type with extension. Can someone enlighten me? - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Download Wicket 1.2 now! Write Ajax applications without touching JavaScript! -- http://wicketframework.org --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
