Re: plugin-testing release for 3.1.1

2013-10-18 Thread Manfred Moser
Jason already applied my patches to master in svn. It just needs to be released/voted on by someone.. manfred > I believe there is github fork mirror here: > https://github.com/apache/maven-plugin-testing/tree/trunk > So you can certainly create a pull request. > > > On 17 October 2013 04:36, Man

Re: plugin-testing release for 3.1.1

2013-10-18 Thread Olivier Lamy
I believe there is github fork mirror here: https://github.com/apache/maven-plugin-testing/tree/trunk So you can certainly create a pull request. On 17 October 2013 04:36, Manfred Moser wrote: > Given its all in the git repo already.. do you want me to create a patch > for whatever is in svn the

Re: plugin-testing release for 3.1.1

2013-10-16 Thread Manfred Moser
Given its all in the git repo already.. do you want me to create a patch for whatever is in svn then? And maybe attach it to some jira issue or something? manfred > Any work that gets patches applied is valid work. You don't get commit > access if you are in the school, only a bunch of mentors wh

Re: plugin-testing release for 3.1.1

2013-10-16 Thread Stephen Connolly
Any work that gets patches applied is valid work. You don't get commit access if you are in the school, only a bunch of mentors who have commit access to shout at if your patches are being ignored ;-) IOW self starters wanted ;-) On Wednesday, 16 October 2013, Manfred Moser wrote: > Hi! > > I ha

plugin-testing release for 3.1.1

2013-10-16 Thread Manfred Moser
Hi! I have a fork of plugin-testing that works for 3.1.1 at https://github.com/mosabua/plugin-testing/tree/maven311 It works fine and we currently use it for the android maven plugin master branch that is migrating to 3.1.1. Could someone please apply the patches back to the repo and release this

Re: Plugin testing release for 3.1.1

2013-09-19 Thread Manfred Moser
Seemingly it does.. a release together with the 3.1.1 release of Maven would be great. manfred > I will if it takes 60 days to create a Git repo. > > On Sep 19, 2013, at 4:47 PM, Olivier Lamy wrote: > >> Maybe can be release from svn. >> >> On 13 September 2013 14:05, Manfred Moser >> wrote: >>

Re: Plugin testing release for 3.1.1

2013-09-19 Thread Jason van Zyl
I will if it takes 60 days to create a Git repo. On Sep 19, 2013, at 4:47 PM, Olivier Lamy wrote: > Maybe can be release from svn. > > On 13 September 2013 14:05, Manfred Moser wrote: >> Hi! >> >> With the 3.1.1 release of Maven coming up hopefully soon I would like to >> move forward with th

Re: Plugin testing release for 3.1.1

2013-09-19 Thread Olivier Lamy
Maybe can be release from svn. On 13 September 2013 14:05, Manfred Moser wrote: > Hi! > > With the 3.1.1 release of Maven coming up hopefully soon I would like to > move forward with the plugin testing harness using it as well. Jason fixed > it to work with 3.0 and requested the repo to be moved

RE: Plugin testing release for 3.1.1

2013-09-13 Thread Martin Gainty
Manfred if there is a problem is on the Apache side you should be able to make the change wheres the hangup ? Martin __ > Date: Fri, 13 Sep 2013 00:05:23 -0400 > Subject: Plugin testing release for 3.1.1 > F

RE: Plugin testing release for 3.1.1

2013-09-13 Thread Manfred Moser
> Manfred > > if there is a problem is on the Apache side you should be able to make the > change wheres the hangup I am not a committer so I have no way to do anything. Maybe I should become one.. manfred - To unsubscribe, e-ma

RE: Plugin testing release for 3.1.1

2013-09-13 Thread Tanveer Ahmad
: Plugin testing release for 3.1.1 Hi! With the 3.1.1 release of Maven coming up hopefully soon I would like to move forward with the plugin testing harness using it as well. Jason fixed it to work with 3.0 and requested the repo to be moved from svn to git so he can release 2.2 over a month ago. It

Plugin testing release for 3.1.1

2013-09-13 Thread Manfred Moser
Hi! With the 3.1.1 release of Maven coming up hopefully soon I would like to move forward with the plugin testing harness using it as well. Jason fixed it to work with 3.0 and requested the repo to be moved from svn to git so he can release 2.2 over a month ago. It seems like nothing happen on th