I would still would like some doc.

The doc in the code source is still broken and it make it difficult to know how 
it is rendered.
In the mean time time, you could write a page. I will then ensure myself that 
is proper included in the doc and rendered when the build will be fixed. You 
can take this file as an exemple:
https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=doc/resolver/ibiblio.html;h=80057c4816a3cabc79bee70c961c57adcee29d11;hb=HEAD
 
<https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=doc/resolver/ibiblio.html;h=80057c4816a3cabc79bee70c961c57adcee29d11;hb=HEAD>

Nicolas

> Le 2 déc. 2014 à 22:56, JBaruch <[email protected]> a écrit :
> 
> Can we use this opportunity to sneak IVY-1474 in?
> 
> Baruch.
> 
> --
> JFrog Developer Advocate
> www.jfrog.com
> +972544954353
> @jbaruch <https://twitter.com/jbaruch/>
> http://linkd.in/jbaruch
> 
> On Tue, Dec 2, 2014 at 6:19 PM, Nicolas Lalevée <[email protected]>
> wrote:
> 
>> It was so obvious that this release candidate should be canceled that I
>> forgot to officially set it. Here it is.
>> 
>> I see that the infra ticket is resolved. Jean-Louis spotted some issues
>> with it though. But I guess we will retry very soon.
>> 
>> Nicolas
>> 
>>> Le 9 nov. 2014 à 17:56, Nicolas Lalevée <[email protected]> a
>> écrit :
>>> 
>>> I have built a release candidate for Ivy 2.4.0
>>> 
>>> The git tag of this release is:
>> https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=commit;h=b7f132a46601cdecfc631052818cab7f498078d2
>>> 
>>> The artifacts has been published to:
>> https://dist.apache.org/repos/dist/dev/ant/ivy/2.4.0@7093
>>> 
>>> Do you vote for the release of these binaries?
>>> 
>>> [ ] Yes
>>> [ ] No
>>> 
>>> Regards,
>>> Nicolas
>>> 
>>> 
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [email protected]
>>> For additional commands, e-mail: [email protected]
>>> 
>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>> 
>> 

Reply via email to