RE: RPM Plugin not cleaning its includes
The first line of output tells me that you didn't run mvn rpm:rpm,
since it was looking for a prefix of jar instead of rpm. If you did
try to run mvn rpm:rpm, please send me a copy of your pom.xml so I can
see what is wrong.
You probably don't want to try to build the pieces, since there are a
couple different projects extracted from various places that you need to
build. Since these are updates to the current release, they (and a few
of their dependencies) have versions ending in SNAPSHOT; this is why the
checks for updates, I believe.
-Original Message-
From: Sena Gbeckor-Kove [mailto:[EMAIL PROTECTED]
Sent: Friday, November 25, 2005 07:02
To: Maven Users List
Subject: Re: RPM Plugin not cleaning its includes
After unipping to my directory I am getting :
Searching repository for plugin with prefix: 'jar'.
[INFO] org.apache.maven.plugins: checking for updates from central
[INFO] org.codehaus.mojo: checking for updates from central
[INFO] artifact org.apache.maven.plugins:maven-jar-plugin: checking
for updates from central
[INFO] artifact org.codehaus.mojo:rpm-maven-plugin: checking for
updates from central
Could you zip the project for me and I'll build and install it locally?
Thx
On 24/11/05, Allison, Bob [EMAIL PROTECTED] wrote:
I think I have the problem with the RPM plugin solved and I updated
the
ZIP file[1]. Could you please download the current version, unpack
the
ZIP file at the top of your Maven 2 repository, and let me know if
this
solves the problem for you?
[1] http://beaver.codehaus.org/~boba/rpm-plugin.zip
-Original Message-
From: Allison, Bob [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 23, 2005 13:36
To: Maven Users List
Subject: RE: RPM Plugin not cleaning its includes
I found the problem. Now I just need to figure out a solution. I'll
let you know when I get this figured out (probably over the weekend).
-Original Message-
From: Sena Gbeckor-Kove [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 23, 2005 11:07
To: Maven Users List
Subject: Re: RPM Plugin not cleaning its includes
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
filemode755/filemode
usernameroot/username
groupnamesystem/groupname
sources
source
locationsrc/main/bin/location
includes
include*/include
/includes
excludes
excludeCVS/exclude
excludeCVS/*/exclude
/excludes
/source
/sources
/mapping
mapping
directory/usr/local/amf/plugin/core/lib/directory
filemode755/filemode
usernameroot/username
groupnamesystem/groupname
sources
source
locationtarget/location
includes
include*.jar/include
/includes
excludes
excludeCVS/exclude
excludeCVS/*/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
Re: RPM Plugin not cleaning its includes
Hi Bob,
No problem, do you want to tell me where you think the problem is and
I can see if I can fix it for you? Can't promise anything as I won't
havea huge amount of time, but just in case.
Regards
On 23/11/05, Allison, Bob [EMAIL PROTECTED] wrote:
I found the problem. Now I just need to figure out a solution. I'll
let you know when I get this figured out (probably over the weekend).
-Original Message-
From: Sena Gbeckor-Kove [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 23, 2005 11:07
To: Maven Users List
Subject: Re: RPM Plugin not cleaning its includes
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
filemode755/filemode
usernameroot/username
groupnamesystem/groupname
sources
source
locationsrc/main/bin/location
includes
include*/include
/includes
excludes
excludeCVS/exclude
excludeCVS/*/exclude
/excludes
/source
/sources
/mapping
mapping
directory/usr/local/amf/plugin/core/lib/directory
filemode755/filemode
usernameroot/username
groupnamesystem/groupname
sources
source
locationtarget/location
includes
include*.jar/include
/includes
excludes
excludeCVS/exclude
excludeCVS/*/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: users@maven.apache.org
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
filenameamf/bin/filename
filemode755/filemode
usernameroot/username
groupnamesystem/groupname
sources
source
locationsrc/main/bin/location
includes
include*/include
/includes
excludes
RE: RPM Plugin not cleaning its includes
I think I have the problem with the RPM plugin solved and I updated the
ZIP file[1]. Could you please download the current version, unpack the
ZIP file at the top of your Maven 2 repository, and let me know if this
solves the problem for you?
[1] http://beaver.codehaus.org/~boba/rpm-plugin.zip
-Original Message-
From: Allison, Bob [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 23, 2005 13:36
To: Maven Users List
Subject: RE: RPM Plugin not cleaning its includes
I found the problem. Now I just need to figure out a solution. I'll
let you know when I get this figured out (probably over the weekend).
-Original Message-
From: Sena Gbeckor-Kove [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 23, 2005 11:07
To: Maven Users List
Subject: Re: RPM Plugin not cleaning its includes
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
filemode755/filemode
usernameroot/username
groupnamesystem/groupname
sources
source
locationsrc/main/bin/location
includes
include*/include
/includes
excludes
excludeCVS/exclude
excludeCVS/*/exclude
/excludes
/source
/sources
/mapping
mapping
directory/usr/local/amf/plugin/core/lib/directory
filemode755/filemode
usernameroot/username
groupnamesystem/groupname
sources
source
locationtarget/location
includes
include*.jar/include
/includes
excludes
excludeCVS/exclude
excludeCVS/*/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: users@maven.apache.org
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
filenameamf/bin/filename
filemode755/filemode
usernameroot/username
groupnamesystem/groupname
sources
source
locationsrc/main/bin/location
includes
Re: RPM Plugin not cleaning its includes
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
filemode755/filemode
usernameroot/username
groupnamesystem/groupname
sources
source
locationsrc/main/bin/location
includes
include*/include
/includes
excludes
excludeCVS/exclude
excludeCVS/*/exclude
/excludes
/source
/sources
/mapping
mapping
directory/usr/local/amf/plugin/core/lib/directory
filemode755/filemode
usernameroot/username
groupnamesystem/groupname
sources
source
locationtarget/location
includes
include*.jar/include
/includes
excludes
excludeCVS/exclude
excludeCVS/*/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: users@maven.apache.org
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
filenameamf/bin/filename
filemode755/filemode
usernameroot/username
groupnamesystem/groupname
sources
source
locationsrc/main/bin/location
includes
include*/include
/includes
excludes
excludeCVS/exclude
excludeCVS/*/exclude
/excludes
/source
/sources
/mapping
mapping
directory/usr/local/directory
filenameamf/plugin/core/lib/filename
filemode755/filemode
usernameroot/username
groupnamesystem/groupname
sources
source
RE: RPM Plugin not cleaning its includes
I found the problem. Now I just need to figure out a solution. I'll
let you know when I get this figured out (probably over the weekend).
-Original Message-
From: Sena Gbeckor-Kove [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 23, 2005 11:07
To: Maven Users List
Subject: Re: RPM Plugin not cleaning its includes
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
filemode755/filemode
usernameroot/username
groupnamesystem/groupname
sources
source
locationsrc/main/bin/location
includes
include*/include
/includes
excludes
excludeCVS/exclude
excludeCVS/*/exclude
/excludes
/source
/sources
/mapping
mapping
directory/usr/local/amf/plugin/core/lib/directory
filemode755/filemode
usernameroot/username
groupnamesystem/groupname
sources
source
locationtarget/location
includes
include*.jar/include
/includes
excludes
excludeCVS/exclude
excludeCVS/*/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: users@maven.apache.org
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
filenameamf/bin/filename
filemode755/filemode
usernameroot/username
groupnamesystem/groupname
sources
source
locationsrc/main/bin/location
includes
include*/include
/includes
excludes
excludeCVS/exclude
excludeCVS/*/exclude
/excludes
/source
/sources
/mapping
mapping
directory/usr
