wow, great accomplishement!
thank you Karl for pushing this with so much patience
and of course, thanks to everybody who helped too: Karl was not completely
alone on this task, even if he did a good part of it
Now we can work on plugins cleanup after pushing them to Maven 3 prerequisite.
And d
+1 on git vs svn question (now I learned git sufficiently)
Le samedi 30 mai 2015 08:39:58 Olivier Lamy a écrit :
> +1
> I believe we already agreed so many times on that.
> We just need volunteers to do the job.
+1
and the work don't stop on git repo migration: there is Jenkins configuration
too
+1
I believe we already agreed so many times on that.
We just need volunteers to do the job.
So thanks Jason to be the volunteer! :-)
--
Olivier
On 30 May 2015 06:20, "Arnaud Héritier" wrote:
> +1 for git
>
> On Fri, May 29, 2015 at 9:11 PM, Tibor Digana
> wrote:
>
> > +1 Git/Hub
> >
> >
> >
>
+1 for git
On Fri, May 29, 2015 at 9:11 PM, Tibor Digana
wrote:
> +1 Git/Hub
>
>
>
> --
> View this message in context:
> http://maven.40175.n5.nabble.com/Full-migration-to-Git-tp5836121p5836214.html
> Sent from the Maven Developers mailing list archive at Nabble.com.
>
> ---
+1 Git/Hub
--
View this message in context:
http://maven.40175.n5.nabble.com/Full-migration-to-Git-tp5836121p5836214.html
Sent from the Maven Developers mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: dev-unsubsc
Known for its immensely agreeable traffic levels, this is the new google
group for plexus :)
https://groups.google.com/forum/#!forum/codehaus-plexus
Kristian
I really dont even know how to use svn any more, so it's just irritating.
All git is the way to go.
K
2015-05-29 19:08 GMT+02:00 Manfred Moser :
> I would love that... if I can avoid relearning more SVN I am all for it ;-)
>
> manfred
>
> Stephen Connolly wrote on 29.05.2015 07:56:
>
> > +1 for
+1 git
On Fri, May 29, 2015 at 2:08 PM, Manfred Moser wrote:
> I would love that... if I can avoid relearning more SVN I am all for it ;-)
>
> manfred
>
> Stephen Connolly wrote on 29.05.2015 07:56:
>
>> +1 for full GIT
>>
>> On 29 May 2015 at 15:28, Tamas Cservenak wrote:
>>
>>> +1 for full git
I would love that... if I can avoid relearning more SVN I am all for it ;-)
manfred
Stephen Connolly wrote on 29.05.2015 07:56:
> +1 for full GIT
>
> On 29 May 2015 at 15:28, Tamas Cservenak wrote:
>
>> +1 for full git
>>
>> --
>> Thanks,
>> ~t~
>>
>> On 29 May 2015 at 13:23:41, Jason van Zy
Github user ctrueden closed the pull request at:
https://github.com/apache/maven-plugins/pull/52
---
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
+1 for full GIT
On 29 May 2015 at 15:28, Tamas Cservenak wrote:
> +1 for full git
>
> --
> Thanks,
> ~t~
>
> On 29 May 2015 at 13:23:41, Jason van Zyl (ja...@takari.io) wrote:
>
> I think it's time for a full migration of all our repositories to Git. I
> just see the email with Dennis struggling
+1 for full git
--
Thanks,
~t~
On 29 May 2015 at 13:23:41, Jason van Zyl (ja...@takari.io) wrote:
I think it's time for a full migration of all our repositories to Git. I just
see the email with Dennis struggling to merge a simple pull request and I think
it's just time to switch completely.
+1
On Fri, May 29, 2015, 07:23 Jason van Zyl wrote:
> I think it's time for a full migration of all our repositories to Git. I
> just see the email with Dennis struggling to merge a simple pull request
> and I think it's just time to switch completely. I think someone already
> started a list an
My solution to use SmartGit seems to be working fine. Source code
changes are moving nicely from my local disk to svn, and then on to
the GitHub mirror. Pull requests in GitHub are closed automatically.
Thanks for the help!
On Fri, May 29, 2015 at 2:47 PM, Dennis Lundberg wrote:
> Thanks again T
Github user asfgit closed the pull request at:
https://github.com/apache/maven-plugins/pull/46
---
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 i
Thanks Olivier,
I found something similar here:
https://wiki.apache.org/general/GitAtApache
But those instructions doesn't include the clever handling of
pr-branches that you suggested.
On Fri, May 29, 2015 at 1:49 PM, Olivier Lamy wrote:
> something not complicated which is convenient with pr
Github user asfgit closed the pull request at:
https://github.com/apache/maven-plugins/pull/48
---
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 i
Thanks again Tamas,
I have already tried that, but neither the patch nor diff would apply
cleanly to my svn working copy.
Trying another approach checking out from svn using SmartGit, which
keeps a local git repo of sources that come from a remote svn repo.
That way I was able to apply the patch
something not complicated which is convenient with pr
git clone https://github.com/apache/maven-plugins.git
now you have to setup git-svn (see the script here:
https://gist.github.com/olamy/836acac9a113c7830918)
Now setup you git config to have all pr as branch
in .git/config add the last line
Sry, I sent the “resolved” URL, here is the real one:
https://github.com/apache/maven-plugins/pull/48.diff
--
Thanks,
~t~
On 29 May 2015 at 13:27:47, Tamas Cservenak (ta...@cservenak.net) wrote:
Dennis,
you can take PRs as patches from GH by appending “.patch” or “.diff” to PR URL,
here is y
Dennis,
you can take PRs as patches from GH by appending “.patch” or “.diff” to PR URL,
here is your example:
https://patch-diff.githubusercontent.com/raw/apache/maven-plugins/pull/48.diff
Then, apply that patch “manually” to sources and then commit. Is a bit
hassle but that’s all to it. Having
Thanks Tibor,
This will not work in my case, because maven-plugin does not have a
git repo at git-wip-us.apache.org.
On Fri, May 29, 2015 at 12:49 PM, Tibor Digana wrote:
> These are my commands for surefire plugin. Use your login and pmd project
> links instead.
> Suppose their branch is "s2"
I think it's time for a full migration of all our repositories to Git. I just
see the email with Dennis struggling to merge a simple pull request and I think
it's just time to switch completely. I think someone already started a list and
we should just move through it. Personally I find SVN is j
These are my commands for surefire plugin. Use your login and pmd project
links instead.
Suppose their branch is "s2" and master is on git-wip-us-apache.org.
If you want to push from master to master, freely avoid s2:master.
You should have RSA key in your user home.
$ git remote add apache
https:
workflow is:
contributor branch@github and submitts PR to --> Apache GitHub mirror -->
committer merges PR in clone @ local and push to --> git-wip-us.apache.org
--> changes are synced to Apache GitHub mirror with all side-effects
(issue/PR closed) because of comment in merge commit message
On Fr
Thanks Stevo,
Interesting read for me that is less than fluent in git. In this case
I unfortunatelly cannot use those instructions as maven-plugins does
not have a git repo at Apache. It is versioned in svn and is probably
using some svn->git mirroring software to end up on the GitHub mirror
at
ht
Github user trohovsky closed the pull request at:
https://github.com/apache/maven-surefire/pull/88
---
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 featu
On Apache Mahout project we have nice docs on the workflow to merge or
reject PRs submitted to github mirror. Maybe it works for you too.
Kind regards,
Stevo Slavic.
On Fri, May 29, 2015 at 9:27 AM, Dennis Lundberg wrote:
> Hi
>
> I'm going through the issue list in JIRA for maven-pmd-plugin an
https://mahout.apache.org/developers/github.html
On Fri, May 29, 2015 at 9:38 AM, Stevo Slavić wrote:
> On Apache Mahout project we have nice docs on the workflow to merge or
> reject PRs submitted to github mirror. Maybe it works for you too.
>
> Kind regards,
> Stevo Slavic.
>
> On Fri, May 29
Hi
I'm going through the issue list in JIRA for maven-pmd-plugin and want
to apply some patches that have been submitted as pull requests to our
GitHub mirror. But I cannot find a way to merge the pull requests. On
the page of the pull request it says:
This pull request can be automatically mer
30 matches
Mail list logo
