[GitHub] maven pull request #145: [MNG-6112] Central repository in the 4.0.0 super PO...

GitHub user ChristianSchulte opened a pull request: https://github.com/apache/maven/pull/145 [MNG-6112] Central repository in the 4.0.0 super POM should declare u… …pdate policy 'never'. You can merge this pull request into a Git repository by running: $ git pull https://gi

[GitHub] maven pull request #144: [MNG-2893] Update the DefaultPluginManager to not u...

GitHub user ChristianSchulte opened a pull request: https://github.com/apache/maven/pull/144 [MNG-2893] Update the DefaultPluginManager to not use a project depMa… …n for controlling it's transitive dependencies You can merge this pull request into a Git repository by running:

[GitHub] maven pull request #143: [MNG-5359] Declared execution in PluginMgmt gets bo...

GitHub user ChristianSchulte opened a pull request: https://github.com/apache/maven/pull/143 [MNG-5359] Declared execution in PluginMgmt gets bound to lifecycle (… …regression) You can merge this pull request into a Git repository by running: $ git pull https://github.com/C

[GitHub] maven pull request #142: [MNG-6114] Profiles from the global settings should...

GitHub user ChristianSchulte opened a pull request: https://github.com/apache/maven/pull/142 [MNG-6114] Profiles from the global settings should be ordered before… … profiles from the user settings. You can merge this pull request into a Git repository by running: $ git pul

[GitHub] maven pull request #141: [MNG-6164] Collections inconsistently immutable.

GitHub user ChristianSchulte opened a pull request: https://github.com/apache/maven/pull/141 [MNG-6164] Collections inconsistently immutable. You can merge this pull request into a Git repository by running: $ git pull https://github.com/ChristianSchulte/maven MNG-6164 Altern

Re: [IMPORTANT] Re: Git migration next steps

I did the assumption that you can isolate all maven-javadoc-plugin commits. If it is for all maven-plugins or nothing, then it is a different story. On Sun, 24 Dec 2017 10:54:16 +0100, wrote: I'd suggest to try the process to a personal personal repo on GitHub to see if you're able to get a b

Re: [IMPORTANT] Re: Git migration next steps

Depending on the changes, may not be any need to involve infra. You should be able to delete tags (and then recreate them): $ git push origin :borked-tag-name Presumably master will still have the same hash (as only the tags need fixup) We’d only need infra *if* the branches need a force update

Re: [IMPORTANT] Re: Git migration next steps

I'd suggest to try the process to a personal personal repo on GitHub to see if you're able to get a better result before involving manual work from INFRA (on more than 60 repos...) (it's sad to see nobody try to explain what's happenning or improve the documented commands, just get to a conclus

Re: [IMPORTANT] Re: Git migration next steps

Hi, On 24/12/17 10:40, Robert Scholte wrote: How about a hard reset or dropping the repo and doing it all over again? If I correctly seen that ..there had no commit yet on the new git repos.. So I think it would be the easiest way to do as Robert suggest ...to redo migration for those repos.

Re: [IMPORTANT] Re: Git migration next steps

How about a hard reset or dropping the repo and doing it all over again? On Wed, 20 Dec 2017 10:42:36 +0100, Hervé BOUTEMY wrote: INFRA-15679 fixed by infra team then I re-run migrate-plugins.sh script to split the svn2git mirror to per- plugin git repo and I pushed "master2" branches fo