Hi,
Please use the Maven Users list instead. This list is meant for actual
development of Maven itself.
Vincent
2013/9/22 Suranga Kasthurirathne suranga...@gmail.com
Hi,
I apologize in advance if this email contains sketchy / incomplete details.
I'm not really a maven expert, and would
In order to accept patches into any Apache Foundation project there must be
EITHER a signed ICLA on file from the person submitting the change OR a
clear indication of intent to contribute the code to the Apache Foundation.
For small or quick changes signing a ICLA is overkill and too large a
On Sep 23, 2013, at 3:54 AM, Stephen Connolly stephen.alan.conno...@gmail.com
wrote:
In order to accept patches into any Apache Foundation project there must be
EITHER a signed ICLA on file from the person submitting the change OR a
clear indication of intent to contribute the code to the
On 23 September 2013 14:32, Daniel Kulp dk...@apache.org wrote:
On Sep 23, 2013, at 3:54 AM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
In order to accept patches into any Apache Foundation project there must
be
EITHER a signed ICLA on file from the person submitting the
@Stephen, @Daniel, sorry I didn't subscribe the ML so just read your
replies via markmail.org
Regarding license, my github repo is simply a clone of
https://github.com/apache/maven-plugins, hence should inherit the same
license, and I kinda agree with Daniel that pull requests on github
are now
FYI, Kristian opened a Jira issue at LEGAL on that question some time ago:
https://issues.apache.org/jira/browse/LEGAL-156
Am Montag, 23. September 2013 schrieb ryenus :
@Stephen, @Daniel, sorry I didn't subscribe the ML so just read your
replies via markmail.org
Regarding license, my
Thank you Andreas.
I've commented on that issue, with almost the same words I used here
about the copyright/license stuff.
Could someone please look at the patches instead of merely worrying
about the license issue (there's no issue at all). They're very
simple, and I have to wait to release my
