On 21 Aug 2012, at 2:31 PM, Anders Hammar wrote: >> The latest version of the plugin is 2.1-alpha-1, we should keep releasing it >> until all the issues are resolved. > > My main problem right now is that close to all ITs fail on my Mac. I > just had a new look at this and just fell into tears. I simply can't > work on something where I can't verify my work with test cases. And > the problem is that I'm not too familiar with rpms so I *really* need > those ITs. > I have no other platform to work on at the moment.
The trouble with rpm is that rpm is an application that largely works on machines with a Redhat heritage, like RHEL, Fedora, etc. I also use MacOSX as a development environment, however I just don't build the rpms on that platform. If the rpm plugin can be made to work on MacOSX it would be really useful, but it shouldn't stop an effort to get it working on Redhat based systems. Maven best practice says that people should be pinning the version number of their plugins, so releasing a new plugin should be a low risk exercise - it won't break any properly configured maven projects. >> If a release could be made, it would be a huge help. > > I appreciate this, but I don't like doing releases which I don't trust myself. > >> Something else I picked up was that JIRA doesn't let an ordinary user like >> me set the "path submitted" flag - I could post a patch, I just couldn't >> mark the ticket as having a patch. (Or I am missing where in JIRA you set >> that). > > I think you can set this when you initially create the ticket. I > marked a few of your tickets as patch included. The trouble was when I created the ticket, I didn't yet have the patch, that came later. Regards, Graham --
smime.p7s
Description: S/MIME cryptographic signature
