On 21 Aug 2012, at 1:40 PM, Anders Hammar wrote: > What I found when working on this plugin before summer, was that its > ITs were in a terrible state. Also, I ran into a bunch of issues > related to my platform (Mac OS). It seems as the plugin has some > really bad bugs related to some platforms. The ticket I'm thinking of > is MRPM-107. > > The plugin being in an "alpha" state, I guess creating a new release > without having all ITs sorted out could be acceptable. It's just that > I have a hard time doing a release which I can't trust/verify the > outcome.
The latest version of the plugin is 2.1-alpha-1, we should keep releasing it until all the issues are resolved. Trying to delay releases causes all sorts of knock on problems, starting with the maven-release-plugin preventing you on making releases of your projects (quite rightly). If a release could be made, it would be a huge help. 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). Regards, Graham --
smime.p7s
Description: S/MIME cryptographic signature
