On Sat, Oct 6, 2012 at 11:04 PM, Stephen Connolly
wrote:
> Our original intent in voting to accept the EPL licensed aether from
> sonatype was that the eclipse one was taking too long, so I viewed the vote
> as being both to take the eclipse one AND pragmatically take the sonatype
> one until ecli
The commit for review if anyone wants to take a look is here:
https://github.com/tesla/maven-3/commit/4595e0860243854a7d80db8ebea97205aa4aca65
Ceki added support for logging to a file without massive contortions so I have
defaulted the implementation to slf4j-simple which is small and provides t
On Oct 6, 2012, at 4:23 AM, Hervé BOUTEMY wrote:
> Aether 0.9.0.M1 is now in central [1]
> and Benjamin did the upgrade on his own Maven 3 branch [2]
>
> Question: do we need a formal vote for the upgrade of this dependency?
No.
> Any objection to do the upgrade without vote, given it's just a
no objections from me.
2012/10/6 Stephen Connolly :
> The dependency we currently have is EPL and the "replacement" is EPL so I
> don't see the need to vote. Only if the license was changing or if we were
> moving from eclipse to a non-foundation hosted artifact would I see the
> need for a vote.
The dependency we currently have is EPL and the "replacement" is EPL so I
don't see the need to vote. Only if the license was changing or if we were
moving from eclipse to a non-foundation hosted artifact would I see the
need for a vote.
In any case I think we can hold back the decision until the
Github user peterlynch closed the pull request at:
https://github.com/apache/maven-indexer/pull/2
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Aether 0.9.0.M1 is now in central [1]
and Benjamin did the upgrade on his own Maven 3 branch [2]
Question: do we need a formal vote for the upgrade of this dependency?
Any objection to do the upgrade without vote, given it's just a new home for a
compoennt we already use?
Regards,
Hervé
[1] ht