Anders, that was the first thing that comes on my mind, but I'm afraid I don't have a jira access, would you be so kind and could you please create a ticket for me ? :-D
here are the options: 1. slightly change the copyright property description 2. change 'copyright' to 'license' + 1. 3. get the license information from project, if the information is not available then 2. (+ 1.) Bye, M. ----- Original Message ----- From: "Anders Hammar" <and...@hammar.net> To: "Mojo Users List" <user@mojo.codehaus.org> Sent: Tuesday, March 5, 2013 9:55:58 AM Subject: Re: [mojo-user] Re: RPM Maven Plugin A JIRA ticket with a patch could fix that...:-) /Anders On Tue, Mar 5, 2013 at 9:30 AM, Miroslav Mikluš <miroslav.mik...@pantheon.sk > wrote: > I already found it. > The 'License:' line is trasformed from the 'copyright' property. > Must say a bit confusing without proper description in the documentation > :-( > > M. > > > ----- Original Message ----- > From: "Miroslav Mikluš" <miroslav.mik...@pantheon.sk> > To: user@mojo.codehaus.org > Sent: Tuesday, February 26, 2013 1:52:02 PM > Subject: 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 > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
