Hi,
The vote has passed with the following result:
+1 (binding): Karl Heinz Marbaise, Hervé Boutemy, Jason van Zyl
+1 (non binding): Dan Tran
I will promote the artifacts to the central repo.
Kind regards
Karl Heinz Marbaise
+1
> On Jun 27, 2015, at 11:02 AM, Karl Heinz Marbaise wrote:
>
> Hi,
>
> this is only a bug fix release and based on the fix we required to use Java
> 1.6 Only (that is the reason for the version upgrade to 2.0.0).
>
> We solved 2 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.j
+1
Regards,
Hervé
Le samedi 27 juin 2015 17:02:06 Karl Heinz Marbaise a écrit :
> Hi,
>
> this is only a bug fix release and based on the fix we required to use
> Java 1.6 Only (that is the reason for the version upgrade to 2.0.0).
>
> We solved 2 issues:
> https://issues.apache.org/jira/secur
Hi,
here is my +1
Kind regards
Karl Heinz Marbaise
On 6/27/15 5:02 PM, Karl Heinz Marbaise wrote:
Hi,
this is only a bug fix release and based on the fix we required to use
Java 1.6 Only (that is the reason for the version upgrade to 2.0.0).
We solved 2 issues:
https://issues.apache.org/jira/
Of course with Perforce SCM where the crucial fix is for.
Thanks
-Dan
On Sat, Jun 27, 2015 at 9:40 AM, Dan Tran wrote:
> +1 none binding. Tested with both maven 3.2.x and 3.3.x
>
> Thanks Karl Heinz for doing this
>
> -Dan
>
> On Sat, Jun 27, 2015 at 8:02 AM, Karl Heinz Marbaise
> wrote:
>
>
+1 none binding. Tested with both maven 3.2.x and 3.3.x
Thanks Karl Heinz for doing this
-Dan
On Sat, Jun 27, 2015 at 8:02 AM, Karl Heinz Marbaise
wrote:
> Hi,
>
> this is only a bug fix release and based on the fix we required to use
> Java 1.6 Only (that is the reason for the version upgrad
Hi,
this is only a bug fix release and based on the fix we required to use
Java 1.6 Only (that is the reason for the version upgrade to 2.0.0).
We solved 2 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317525&version=12332831
There are still a couple of issues lef
