Hi Bob,
We are trying to do the following :
-- Install ${basedir}/src/main/bin/* at /usr/local/amf/bin
${basedir}/src/main/bin/* --> /usr/local/amf/bin
-- Install ${basedir}/target/*.jar at /usr/local/amf/plugin/core/lib
${basedir}/target/*.jar --> /usr/local/amf/plugin/core/lib
We are using the following mappings fragment having looked at your
suggestions regarding the filename elemnt and still the contents of
the first mapping turn when copying the contents for the second
mapping.
<mappings>
<mapping>
<directory>/usr/local/amf/bin</directory>
<filemode>755</filemode>
<username>root</username>
<groupname>system</groupname>
<sources>
<source>
<location>src/main/bin</location>
<includes>
<include>*</include>
</includes>
<excludes>
<exclude>CVS</exclude>
<exclude>CVS/*</exclude>
</excludes>
</source>
</sources>
</mapping>
<mapping>
<directory>/usr/local/amf/plugin/core/lib</directory>
<filemode>755</filemode>
<username>root</username>
<groupname>system</groupname>
<sources>
<source>
<location>target</location>
<includes>
<include>*.jar</include>
</includes>
<excludes>
<exclude>CVS</exclude>
<exclude>CVS/*</exclude>
<exclude>*/*</exclude>
</excludes>
</source>
</sources>
</mapping>
Any ideas?
Thanks in advance
Regards
On 23/11/05, Allison, Bob <[EMAIL PROTECTED]> wrote:
> Well, I see a couple problems with your configuration. As I read the
> two mappings, they should do the following:
>
> -- Install ${basedir}/src/main/bin/* at /usr/local (for example,
> ${basedir}/src/main/bin/myprog will be installed at /usr/local/myprog)
>
> -- Install ${basedir}/target/*.jar at /usr/local (for example,
> ${basedir}/target/myprog.jar will be installed at /usr/local/myprog.jar)
>
> You are getting the two mappings muddled because they specify the same
> destination. You will probably almost never need to specify the
> filename parameter. Instead, the directory parameters should be
> specified as /usr/local/amf/bin and /usr/local/amf/plugin/core/lib.
>
> -----Original Message-----
> From: Sena Gbeckor-Kove [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, November 23, 2005 08:38
> To: [email protected]
> Subject: RPM Plugin not cleaning its includes
>
>
> Hi Bob,
>
> It appears that the RPM plugin cumulatively includes the contents of
> includes when dealing wiith mappings. For example, the following 2
> mappings cause thhe contents of the first ampping, a bunch of scripts
> from the bin directory, to be copied into the next <filename/>
> specified "amf/plugin/core/lib".
>
> Any ideas would be appreciated.
>
> Regards
>
> <mappings>
> <mapping>
> <directory>/usr/local</directory>
> <filename>amf/bin</filename>
> <filemode>755</filemode>
> <username>root</username>
> <groupname>system</groupname>
> <sources>
> <source>
> <location>src/main/bin</location>
> <includes>
> <include>*</include>
> </includes>
> <excludes>
> <exclude>CVS</exclude>
> <exclude>CVS/*</exclude>
> </excludes>
> </source>
> </sources>
> </mapping>
> <mapping>
> <directory>/usr/local</directory>
> <filename>amf/plugin/core/lib</filename>
> <filemode>755</filemode>
> <username>root</username>
> <groupname>system</groupname>
> <sources>
> <source>
> <location>target</location>
> <includes>
> <include>*.jar</include>
> </includes>
> <excludes>
> <exclude>CVS</exclude>
> <exclude>CVS/*</exclude>
> </excludes>
> </source>
> </sources>
> </mapping>
>
> ---------------------------------------------------------------------
> 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]
