2015-06-27 14:40 GMT+02:00 robert.patr...@oracle.com <
robert.patr...@oracle.com>:
>
> The second time, I tried to interact around someone else's problem with
> mvnDebug.cmd. No one ever responded.
>
That's not really true - people did respond, it's just that no one stood up
and put your suggest
Hi Robert,
On 6/27/15 2:40 PM, robert.patr...@oracle.com wrote:
I have only tried to interact a few times myself (others in my team have tried
as well).
> The first time, my team and I get a patch we submitted
>to enhance the wagon-http for SSO-protected repositories adopted
thanks to Olivie
I have only tried to interact a few times myself (others in my team have tried
as well). The first time, my team and I get a patch we submitted to enhance
the wagon-http for SSO-protected repositories adopted thanks to Olivier Lamy.
The second time, I tried to interact around someone else's pro
>> Which would exactly results in coded builds which is in the end much
>> more complicated and worse maintainable than any Maven build every be
I agreed that the build is worse maintainable after long time, but the
problem is that Java Hamcrest project, as an example, decided to use Graddle
Hi Robert,
On 6/27/15 12:51 PM, robert.patr...@oracle.com wrote:
Sorry for butting in but as someone who is a staunch supporter of
> Maven within my company and its user community,
> I have to agree that the difficulty in engaging
> the Maven developers to even discuss issues
> is too high.
F
