Are plugin configurations inherited/cumulative? E.g., given
project 'A' descriptor containing

   <build>
     <plugins>
       <plugin>
         <artifactId>P</artifactId>
           <configuration>
             blah-1

and sub-project/module 'B', with descriptor containing

   <build>
     <plugins>
       <plugin>
         <artifactId>P</artifactId>
           <configuration>
             blah-2
             blah-3

Does plugin 'P' see 'blah-1' in its configuration?

Thanks.

Brad

-----Original Message-----
From: Julien Henry [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 27, 2006 9:48 AM
To: Maven Users List
Subject: Building custom assembly



Hi,

My project is a multi-module project :

jwebunit/
|->pom.xml
|->jwebunit-commons-tests
    |->pom.xml
    |->src/...
|->jwebunit-core
    |->pom.xml
    |->src/...
|->jwebunit-htmlunit-plugin
    |->pom.xml
    |->src/...


I would like to create 3 packages :
 - jwebunit-source.zip (easy)
 - jwebunit-javadoc.zip : contains aggregate Javadoc from jwebunit-core
and jwebunit-htmlunit-plugin
 - jwebunit-bin.zip : contains jwebunit-htmlunit-plugin.jar,
jwebunit-core.jar and all htmlunit dependencies (only runtime scope)

I think know how to do the first package. Concerning the aggregated
javadoc, perhaps after mvn site can I take the file in target/site/javadoc
Concerning the last package, I read the example on assembly plugin
website, but I don't know how to keep only runtime dependencies in a
multi-module project.

Thanks

Julien

This message contains information that may be privileged or confidential and
is the property of the Capgemini Group. It is intended only for the person
to whom it is addressed. If you are not the intended recipient,  you are not
authorized to read, print, retain, copy, disseminate,  distribute, or use
this message or any part thereof. If you receive this  message in error,
please notify the sender immediately and delete all  copies of this message.


---------------------------------------------------------------------
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]

Reply via email to