RE: [mojo-user] rpm-maven-plugin 2.1-alpha-4

unsubscribe From: Rickard von Essen [mailto:rickard.von.es...@gmail.com] Sent: Tuesday, April 29, 2014 8:22 AM To: user@mojo.codehaus.org Subject: Re: [mojo-user] rpm-maven-plugin 2.1-alpha-4 Hi, The Codehaus Mojo (maven plugins) procedure for release is a bit confusing. Since the site is

Re: [mojo-user] rpm-maven-plugin 2.1-alpha-4

kard von Essen [mailto:rickard.von.es...@gmail.com] > *Sent:* dinsdag 29 april 2014 14:07 > *To:* user@mojo.codehaus.org > *Subject:* Re: [mojo-user] rpm-maven-plugin 2.1-alpha-4 > > > > Hi, > > > > The Codehaus Mojo (maven plugins) procedure for release is a bit >

RE: [mojo-user] rpm-maven-plugin 2.1-alpha-4

Thanks Heikki Doeleman From: Rickard von Essen [mailto:rickard.von.es...@gmail.com] Sent: dinsdag 29 april 2014 14:07 To: user@mojo.codehaus.org Subject: Re: [mojo-user] rpm-maven-plugin 2.1-alpha-4 Hi, The Codehaus Mojo (maven plugins) procedure for release is a bit confusing. Since the site

Re: [mojo-user] rpm-maven-plugin 2.1-alpha-4

No, it is being voted on currently. If you want to try it out during voting time (much appreciated!), you need to use the staging repo. Unfortunately I don't think we have an instruction how to do this, but you need to add the staging repo to your settings.xml. Look for repo with id 'codehaus-nexus

Re: [mojo-user] rpm-maven-plugin 2.1-alpha-4

Hi, The Codehaus Mojo (maven plugins) procedure for release is a bit confusing. Since the site is deployed at the time when the plugin is staged for release, at the same time there is a vote if the release should released. The vote takes 72 hours after that the staged release is promoted to Maven

Re: [mojo-user] rpm-maven-plugin 2.1-alpha-4

Hi, The release is currently being voted on (that's why maybe you're looking for the version exposed in the website). See http://mojo.10943.n7.nabble.com/VOTE-Release-rpm-maven-plugin-version-2-1-alpha-4-td44412.htmlif you want to give it a try, anyone is allowed to give +1/0/-1 vote, and the more

[mojo-user] rpm-maven-plugin 2.1-alpha-4

Hello, I tried searching the mailing list archives but somehow couldn't find a searchable archive. So I'm just asking: is the rpm-maven-plugin version 2.1-alpha-4 available from some maven repository ? E.g. http://mvnrepository.com/artifact/org.codehaus.mojo/rpm-maven-plugin doesn't have it ye

RE: [mojo-user] [rpm-maven-plugin] rpm artifact filename changed

stian Andersson A [mailto:christian.a.anders...@ericsson.com] Sent: 14 March 2014 08:33 To: user@mojo.codehaus.org Subject: [mojo-user] [rpm-maven-plugin] rpm artifact filename changed hi, Why is the name of the rpm changed from noarch.rpm to -rpm.rpm? And how can I stop it to be changed, when ru

[mojo-user] [rpm-maven-plugin] rpm artifact filename changed

hi, Why is the name of the rpm changed from noarch.rpm to -rpm.rpm? And how can I stop it to be changed, when running install or deploy. --- from log output: [INFO] Installing ..workspace../com.comp.art/target/rpm/art/RPMS/noarch/art-0.0.1-SNAPSHOT20140314074613*.noarch.rpm* to .../.m2/repo

[mojo-user] rpm-maven-plugin - problem with applying to other mappings

I'm having trouble with the directive in a parent POM being applied to other mappings in the child project. Here's a snippet from the parent POM org.codehaus.mojo rpm-maven-plugin 2.1-alpha-2 true true> /app/root/dir

[mojo-user] RPM Maven plugin, Recursive chown in mapping directory configuration

Hi list, I'm needing some help with the plugin. I could one map a directory changing the username and groupname for all files/directories but keeping their original permissions? Here's a snippet of my configuration: ... ${install.base.dir}/dir/subdir tomcat tomcat ${project.build.directory}/

[mojo-user] RPM Maven Plugin classifier

My projects creates 3 RPM. * The main gui * The devel * The Java Web Start The latter two have classifiers, devel and jws. The main RPM does not have a classifier, but the rpm file name still gets one. These RPMs is what I get when building the project: myapp-1.0-devel-rpm myapp-1.0-jws-rpm my

Re: [mojo-user] RPM Maven Plugin not using defined prefix

I can't help much, but just want to let you know that the development effort on this plugin is currently very low. I did the last release but I'm far from an RPM expert and have just stepped in to do the release, not much further development. So if you have any problems, please file tickets. But do

[mojo-user] RPM Maven Plugin not using defined prefix

Using the RPM Maven plugin I have found which I'm not sure is, bugs, missing features or wrong configuration. Setting prefix is useless. I cannot use the defined RPM macros in mapping locations. %_prefix/usr %_exec_prefix %{_prefix} %_bindir%{_exec_prefix}/bin If

Re: [mojo-user] rpm-maven-plugin: failed to resolve artifact mapping

Could you please file a ticket for this? http://mojo.codehaus.org/rpm-maven-plugin/issue-tracking.html /Anders On Tue, Mar 5, 2013 at 8:35 AM, Андрей Хитрин wrote: > I think, it would be useful to provide more informative message in such > case. Please take a look at the attached patch! It thro

Re: [mojo-user] rpm-maven-plugin: failed to resolve artifact mapping

I think, it would be useful to provide more informative message in such case. Please take a look at the attached patch! It throws exception with (as I hope) helpful message when the artifact cannot be resolved. I think it's slightly better than NPE (which may be treated as failure in the plugin its

Re: [mojo-user] rpm-maven-plugin: failed to resolve artifact mapping

Thank you for help! 2013/3/4 Anders Hammar > A quick guess is that you need to execute > mvn install > first ot get the artifact installed into the local repo. Then you can > execute > mvn rpm:rpm > > DOn't understand why you want to execute rpm:rpm separately though... > > /Anders > > > On Mon

Re: [mojo-user] rpm-maven-plugin: failed to resolve artifact mapping

> A quick guess is that you need to execute > mvn install My bad! This definitely helps. Sorry for panic :( > DOn't understand why you want to execute rpm:rpm separately though... Just did it "for easier log reading", nothing more. 2013/3/4 Anders Hammar > A quick guess is that you need to e

Re: [mojo-user] rpm-maven-plugin: failed to resolve artifact mapping

A quick guess is that you need to execute mvn install first ot get the artifact installed into the local repo. Then you can execute mvn rpm:rpm DOn't understand why you want to execute rpm:rpm separately though... /Anders On Mon, Mar 4, 2013 at 5:44 PM, Андрей Хитрин wrote: > Hi all! > > We've

[mojo-user] rpm-maven-plugin: packages built with noarch are failing on /bin/sh dependency

I've been trying to build some noarch packages and trying to install them on Mac OS X 10.7.5 using RPM 4.4.9 (which was installed via MacPorts). However the install fails, saying error: Failed dependencies: /bin/sh is needed by ... Of course /bin/sh exists but RPM doesn't seem to know it.

Re: [mojo-user] rpm-maven-plugin: building multiple rpms in the same build?

Yes, but the "Maven way" is to only produce one artifact per project. I strongly suggest you follow this idea. But if you really want to produce several rpms you need to do so as secondary artifacts. There's a small section in the Usage page about this and you can have a look in the ITs of the plug

[mojo-user] rpm-maven-plugin: building multiple rpms in the same build?

Hi, is there a way to build more than 1 rpm in the same build? --Steffen -- View this message in context: http://mojo.10943.n7.nabble.com/rpm-maven-plugin-building-multiple-rpms-in-the-same-build-tp39009.html Sent from the User mailing list archive at Nabble.com.

[mojo-user] RPM Maven Plugin

Hi all, I tried to use rpm-maven-plugin 2.1-alpha-2, but I didn't find any reasonable way how to push the License line: License: GPL into the .spec file, is there something I missed ? Without this line rpmbuild fails (Fedora 18 - RPM version 4.10.3.1) Nice day, Miro -

Re: [mojo-user] rpm-maven-plugin: Build of SNAPSHOT fails with 2.1-alpha-2

http://mojo.codehaus.org/build-helper-maven-plugin/usage.html#Set_a_property_by_applying_a_regex_replacement_to_a_value(though note that the example has suffered some remaining \'s due to trying to escape velocity's processing of property expansion On 31 October 2012 13:03, Stephen Connolly wrote:

Re: [mojo-user] rpm-maven-plugin: Build of SNAPSHOT fails with 2.1-alpha-2

http://mojo.codehaus.org/build-helper-maven-plugin/regex-property-mojo.html you can have the passed through property based on a regex replacement of ${project.version} On 31 October 2012 12:54, Sandy McPherson wrote: > The 2.1-alpha-1 version used to strip the 'SNAPSHOT" from the maven > versio

[mojo-user] rpm-maven-plugin: Build of SNAPSHOT fails with 2.1-alpha-2

The 2.1-alpha-1 version used to strip the 'SNAPSHOT" from the maven version and add this to the revision. 2.1-alpha-2 (quite correctly from an RPM point of view) does not build the RPM as it complains about the illegal '-' character in the version (i am passing ${project.version} as the parameter.

Re: [mojo-user] RPM Maven plugin config element question

It sets the prefix tag in the rpm spec file, for building relocatable rpms. More information about relocatable rpms can be found in the Maximum RPM book at http://www.rpm.org/max-rpm/s1-rpm-reloc-building-relocatable.html On Wed, May 23, 2012 at 1:24 PM, Jeff wrote: > In the sample shown at > h

[mojo-user] RPM Maven plugin config element question

In the sample shown at http://mojo.codehaus.org/rpm-maven-plugin/example1.html there is a element defined in the but I am not seeing it described in the http://mojo.codehaus.org/rpm-maven-plugin/params.html document. What is the element used for? -- Jeff Vincent predato...@gmail.com See my Li

Re: [mojo-user] rpm-maven-plugin: wildcard within source-location

Hi, could you give the use pom.xml here to see how you configured the rpm-maven-plugin? Kind regards Karl-Heinz Marbaise -- SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893 Dipl.Ing.(FH) Karl-Heinz MarbaiseICQ#: 135949029 Hauptstrasse 177 US

Re: [mojo-user] rpm-maven-plugin: wildcard within source-location

Split this into two projects. One that produces the jar and one that produces the rpm. Maven golden rule: One project -> one artifact. On Fri, May 11, 2012 at 2:26 PM, Dominik Lehnen wrote: > Hi, > > i made my first steps with the rpm-maven-plugin and have the problem, > that the jar of my proje

[mojo-user] rpm-maven-plugin: wildcard within source-location

Hi, i made my first steps with the rpm-maven-plugin and have the problem, that the jar of my project, as well as the rpm i want to create, end up in the same folder "target". the build is not possible, because "the destination directory cannot include itself". Makes sense ... My idea was to use

Re: [mojo-user] rpm-maven-plugin roadmap

http://jira.codehaus.org/browse/MRPM-107 /Anders On Thu, May 3, 2012 at 2:24 AM, Mike Drob wrote: > Is there a JIRA associated with the failing tests? > > On May 2, 2012 2:26 AM, "Anders Hammar" wrote: >> >> One main problem with that plugin is that the ITs don't pass. Problem seen >> on both M

Re: [mojo-user] rpm-maven-plugin roadmap

Is there a JIRA associated with the failing tests? On May 2, 2012 2:26 AM, "Anders Hammar" wrote: > One main problem with that plugin is that the ITs don't pass. Problem seen > on both Mac OS and Ubuntu. > I'd like to get that fixed, but I don't know rpm well enough to know how > to fix. > > /And

Re: [mojo-user] rpm-maven-plugin roadmap

One main problem with that plugin is that the ITs don't pass. Problem seen on both Mac OS and Ubuntu. I'd like to get that fixed, but I don't know rpm well enough to know how to fix. /Anders (mobile) Den 1 maj 2012 20.10 skrev "Mike Drob" : > Hello, > > Is there a planned release date for version

[mojo-user] rpm-maven-plugin roadmap

Hello, Is there a planned release date for version 2.1 of the rpm-maven-plugin? Or at least a 2.1-alpha-2? I would really like to be able to take advantage of the fix in http://jira.codehaus.org/browse/MRPM-102 without having to build the plugin from source. Thanks, Mike

Re: [mojo-user] rpm-maven-plugin

s guys for all the help > >> The following may be what you are requesting. >> >> >> software_name mySoftwareName >> >> >> >> /James >> >>> -Original Message- >>> From: Sandy McPherson [mailto:alls...@xs4all.nl]

RE: [mojo-user] rpm-maven-plugin

ing. > > > software_name mySoftwareName > > > > /James > >> -Original Message- >> From: Sandy McPherson [mailto:alls...@xs4all.nl] >> Sent: 25 April 2012 14:52 >> To: user@mojo.codehaus.org >> Subject: Re: [mojo-user] rpm-maven-plugin &

RE: [mojo-user] rpm-maven-plugin

Great thanks a lot... > The following may be what you are requesting. > > > software_name mySoftwareName > > > > /James > >> -Original Message- >> From: Sandy McPherson [mailto:alls...@xs4all.nl] >> Sent: 25 April 2012 14:52 >> To: use

RE: [mojo-user] rpm-maven-plugin

The following may be what you are requesting. software_name mySoftwareName /James > -Original Message- > From: Sandy McPherson [mailto:alls...@xs4all.nl] > Sent: 25 April 2012 14:52 > To: user@mojo.codehaus.org > Subject: Re: [mojo-user] rpm-maven-plugin > > Hi

Re: [mojo-user] rpm-maven-plugin

Hi Anders, Thanks for the quick reply I am not so much interested in the filename as such, but the name encoded in the RPM, this is because the standards-nazis at my present employer have come up with some bizarre naming scheme for RPMs and I am trying to bolt the RPM build onto long existing maven

Re: [mojo-user] rpm-maven-plugin

The name of the artifact deployed to the repo is standardized by the repo layout. However, I agree that the file produced under target could use project.build.finalName (although is see little benefit of this as it is IMHO what is deployed to the repo that matters). If it's important, please file a

[mojo-user] rpm-maven-plugin

Hi, This is a great plugin, only drawback would seem to be that the name of the rpm is the project.artifactId and it is not configurable. This is a great pity. I would have thought it more natural to use the project.build.finalName as the default value of the RPM name, but still have name configura

[mojo-user] rpm-maven-plugin writes to the wrong RPM file ?

Here is the section of my pom.xml: org.codehaus.mojo rpm-maven-plugin attached-rpm prepare-package bin fubar-${buildNumber} ${project.version}

Re: [mojo-user] rpm-maven-plugin 2.1-alpha-1 fails when running on Solaris

Hi, the first thing would be to file in an issue or i can take that if you like...and may be you can produce a patch... But we have to think about the consequences changing from -e to -f cause the meaning is different... -f means file exists and is an regular file whereas -e means file exists..

[mojo-user] rpm-maven-plugin 2.1-alpha-1 fails when running on Solaris

Hi, I am running rpm-maven-plugin 2.1-alpha-1 on Solaris. It fails with this message [WARNING] + umask 022 [WARNING] + cd /app/home/relmascm/mpo_masterbuild/07Dec11/migrated-scripts/batch_jobs/target/rpm/batch_jobs/BUILD [WARNING] + /usr/bin/rm -rf /app/home/relmascm/mpo_masterbuild/07Dec11/migr

[mojo-user] rpm-maven-plugin - is there any way to specify the dirmode other than the defaultDirmode attribute?

Hi, Looking at the documentation on specifying parameters in the mapping of the RPM spec file, it sounds as if the only way to specify a value for the dirmode of any files in the RPM is to use the setting: If none of the file attributes (filemode, username, and groupname) are populated, t

[mojo-user] [rpm-maven-plugin] What is the directory where the pre/post install scripts run?

Hi, what is the directory where the pre and post install scripts run? Is there a setting in the of the plugin that influences it? regards, Wim

Re: [mojo-user] [rpm-maven-plugin] How to adjust the name used for the RPM package?

Thank you, I have created an improvement request for updating the docs: http://jira.codehaus.org/browse/MRPM-81 regards, Wim 2010/7/12 Chris Bredesen > On 07/12/2010 02:36 AM, Wim Deblauwe wrote: > >> Hi, >> >> I just started using the rpm-maven-plugin

Re: [mojo-user] [rpm-maven-plugin] How to adjust the name used for the RPM package?

On 07/12/2010 02:36 AM, Wim Deblauwe wrote: Hi, I just started using the rpm-maven-plugin and it works great so far. However, as also noted in the documentation, the 'artifactId' is used as name for the RPM package. For me, this is not what I want, I would like to override this name. I cannot ch

[mojo-user] [rpm-maven-plugin] Error loading class 'org.codehaus.mojo.rpm.PreinstallScriptlet'

Hi, I tried to add a preinstallScriptlet to the configuration of the rpm-maven-plugin, but this does not seem to work. I get the following exception: [INFO] [ERROR] BUILD ERROR [INFO]

[mojo-user] [rpm-maven-plugin] How to adjust the name used for the RPM package?

Hi, I just started using the rpm-maven-plugin and it works great so far. However, as also noted in the documentation, the 'artifactId' is used as name for the RPM package. For me, this is not what I want, I would like to override this name. I cannot change my artifactId. Is this possible currentl

[mojo-user] [rpm-maven-plugin] Directory conflicts with other RPM packages already installed

Hi, I'm trying to build an RPM that installs a file in /etc/init.d, my configuration is: --snippet-- /etc/init.d 500 user user ${project.build.directory}/etc/init.d file --snippet-- This creates th

[mojo-user] rpm-maven-plugin with scripts for running as a daemon

Hi! I have an application which production environment is Redhat. To simplify deployment I want to generate a rpm package and have it set up start/stop scripts. Is it appropriate to use the appassembler plugin to generate the scripts? If so, which goals? (generate-daemons and jsw? assemble?)

RE: [mojo-user] [rpm-maven-plugin] Spec file generation problems

rigine- De : Bob Allison [mailto:[EMAIL PROTECTED] Envoyé : mercredi 14 février 2007 11:59 À : user@mojo.codehaus.org Objet : Re: [mojo-user] [rpm-maven-plugin] Spec file generation problems That's not a bad idea, but I need to be careful with it. The syntax allows for you to specify somet

Re: [mojo-user] [rpm-maven-plugin] Spec file generation problems

ce include. - Original Message - From: "DROILLARD Vincent Ext ROSI/DPS" <[EMAIL PROTECTED]> To: Sent: Wednesday, February 14, 2007 5:15 AM Subject: RE: [mojo-user] [rpm-maven-plugin] Spec file generation problems Thanks for your answer. I put the Case1 because it was the onl

RE: [mojo-user] [rpm-maven-plugin] Spec file generation problems

27;origine- De : Bob Allison [mailto:[EMAIL PROTECTED] Envoyé : mardi 13 février 2007 19:14 À : user@mojo.codehaus.org Objet : Re: [mojo-user] [rpm-maven-plugin] Spec file generation problems Sorry, I missed this message the first time around... Case 1: That would be the expected result. You s

Re: [mojo-user] [rpm-maven-plugin] Spec file generation problems

packaging. I will try to look to see if there is some way I can improve how the spec file is being generated. - Original Message - From: "DROILLARD Vincent Ext ROSI/DPS" <[EMAIL PROTECTED]> To: Sent: Tuesday, February 13, 2007 12:08 PM Subject: RE: [mojo-user] [r

RE: [mojo-user] [rpm-maven-plugin] Spec file generation problems

Nobody has comment ? -Message d'origine- De : DROILLARD Vincent Ext ROSI/DPS [mailto:[EMAIL PROTECTED] Envoyé : mercredi 17 janvier 2007 15:01 À : user@mojo.codehaus.org Objet : [mojo-user] [rpm-maven-plugin] Spec file generation problems Hi, I want to set rights on files with th

[mojo-user] [rpm-maven-plugin] Spec file generation problems

Hi, I want to set rights on files with the rpm plugin but I only can do that for directories. Example : I want to set rights 444 to the file /tmp/mine/hi.csv Case 1 : Pom.xml : /tmp/mine/hi.csv 444 src/mine/hi.csv Spec file : %attr(444,-,-) /tmp/mine/hi.csv Spec file is OK but the