Re: [VOTE] Revert Surefire and commit to branches

Git revert hash produces an inverse commit to hash. If from the 11 only one is bad, revert is your friend. If you want to get back to the same state, my options previously are required, not a single revert operation with just a hash supplied. man git revert && man git reset # :-) On Wed, Jan 18,

Re: [VOTE] Revert Surefire and commit to branches

For me it is useful to still see the history because we want to be motivated and open branches which fix the reverted commits. There are only 11 commits to revert. Few days ago, unlike in Maven. So pure git revert is fine. On Wed, Jan 18, 2017 at 6:01 AM, Fred Cooke wrote:

Re: [VOTE] Revert Surefire and commit to branches

By revert do you mean reset --hard or keep the full history and rest the contents then re commit and verify with a diff to that hash? Or did you mean revert, each commit, in reverse order, back to that base? On Wed, Jan 18, 2017 at 5:43 PM, Tibor Digana wrote: > Hi, >

[VOTE] Revert Surefire and commit to branches

Hi, We have messed up Surefire codeline and we want to revert to [1] where CI was stable. This enables us to continue with development. [1] 66bc4c0839ba11af7a8915930f76abf3cd58ee53 Vote open for at least 72 hours. [ ] +1 [ ] +0 [ ] -1

[GitHub] maven-surefire issue #140: 退回2.19.1

Github user Tibor17 commented on the issue: https://github.com/apache/maven-surefire/pull/140 Sorry but what you mean by this PR? On Wed, Jan 18, 2017 at 3:37 AM, xiaoguangma wrote: > 退回2.19.1 > --

[GitHub] maven-surefire pull request #140: 退回2.19.1

GitHub user xiaoguangma opened a pull request: https://github.com/apache/maven-surefire/pull/140 退回2.19.1 退回2.19.1 You can merge this pull request into a Git repository by running: $ git pull https://github.com/xiaoguangma/maven-surefire master Alternatively you can

Re: Shade plugin release

Hi Olivier, that's good. Let me work on the usage of maven-artifact-transfer and remove the maven-compat dependency at compile time. thanks, Robert On Tue, 17 Jan 2017 21:03:42 +0100, Olivier Lamy wrote: Hi I'd like to release the shade plugin next week. Let me know if

[GitHub] maven-plugins pull request #96: Groovy extension module transformer

Github user vietj closed the pull request at: https://github.com/apache/maven-plugins/pull/96 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

Shade plugin release

Hi I'd like to release the shade plugin next week. Let me know if someone has any concerns with that? Cheers -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy

[GitHub] maven-enforcer pull request #21: Add rule: banProfiles

GitHub user mikkoi opened a pull request: https://github.com/apache/maven-enforcer/pull/21 Add rule: banProfiles Same patch as in https://issues.apache.org/jira/browse/MENFORCER-261 Signed-off-by: Mikko Johannes Koivunalho You can merge this pull

Re: reviewing Maven Artifact Resolver MNG-6007 branch

http://www.apache.org/dev/licensing-howto.html#source-tree-location bq. LICENSE and NOTICE belong at the top level of the source tree. They may be named LICENSE.txt and NOTICE.txt, but the bare names are preferred. http://www.apache.org/dev/licensing-howto.html#binary bq. What applies to