Hello everyone, (Didn't intend to release those two together, but overlooked to close the staging repo before releasing the next one, so only one repo and I didn't think that would be an issue, given in the end extra-enforcer-rules:1.0 has no change. It's the last release just renamed for finally clarifying this is actually usable as explained in the previous email).
Staging repository: https://oss.sonatype.org/content/repositories/orgcodehausmojo-1130/ 1. mojo-parent: - https://github.com/mojohaus/mojo-parent/compare/mojo-parent-40...mojo-parent-50 2. extra-enforcer-rules: 1. No change from 1.0-beta-9, as you can see https://github.com/mojohaus/extra-enforcer-rules/compare/extra-enforcer-rules-1.0-beta-9...extra-enforcer-rules-1.0 2. (you could see I screwed up a few beta- releases after beta-9. It was me getting back my credentials and mvn deploy issues ironed out :-|) Please vote [ ] +1 [ ] +0 [ ] -1 *If nobody disagrees, I would like to leave this vote open slightly less long than usual, say 24 hours so that I can push the button tomorrow evening or so.* It's just to allow me to move forward on other tasks, given also the specific case here, which I think requires less review than usually: an internal artifact for us (mojo-parent), and a version bump without actual content (extra-enforcer-rules). Thanks! -- Baptiste -- You received this message because you are subscribed to the Google Groups "mojohaus-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/mojohaus-dev/CANWgJS6L%3Diqq0KC5L1%2Bih7EJWHOUGVA7_f86ny2SW9OXo9DBZQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
