Yes, that appears to be the only place where we explain documentation
contribution.
However, the IvyDE project page too points to this page. That’s a reminder for
us that the IvyDE project too probably needs to move to asciidoc.
-Jaikiran
On 20-Jun-2017, at 3:39 AM, Nicolas Lalevée
>
> On 20-Jun-2017, at 3:38 AM, Nicolas Lalevée
> wrote:
>
>
>> Le 19 juin 2017 à 04:52, Jaikiran Pai a écrit :
>>
>> The documentation for ant-ivy project has now been migrated to asciidoc. The
>> migration used a tool developed by
On 19-Jun-2017, at 2:43 PM, Nicolas Lalevée wrote:
>
>> Le 19 juin 2017 à 05:14, Jaikiran Pai a écrit :
>>
>> We have (read only) github repos which back our main ASF git repos (consider
>> the github ant-ivy repo which is a read-only
What I've done on other Apache projects is essentially "git pull
github/pull/N/head", merging directly into master (this is after it's ready
to merge of course). After pushing that, GitHub will see that the branch is
merged and auto-closes the PR. If you rewrite history as with the rebase
example,
> Le 19 juin 2017 à 08:30, Jan Matèrne (jhm) a écrit :
>
> Doc's mentioning 'how to document' must be updated.
> I found http://ant.apache.org/ivy/write-doc.html Some more?
This is the only page which explain xooki I know.
Nicolas
>
> Jan
>
>> -Ursprüngliche
> Le 19 juin 2017 à 04:52, Jaikiran Pai a écrit :
>
> The documentation for ant-ivy project has now been migrated to asciidoc. The
> migration used a tool developed by Nicolas to migrate the xooki backed HTML
> docs to asciidoc. This tool auto-generated the asciidoc
SVG is inlined as code, see http://people.apache.org/~hibou/doc/osgi.html
Gintas
2017-06-20 0:09 GMT+02:00 Nicolas Lalevée :
>
> > Le 19 juin 2017 à 08:30, Jan Matèrne (jhm) a écrit :
> >
> > Doc's mentioning 'how to document' must be updated.
> >
On 2017-06-19, Jaikiran Pai wrote:
> We have (read only) github repos which back our main ASF git repos
> (consider the github ant-ivy repo which is a read-only mirror of ASF
> git repo). Users submit pull requests to our github repos and the
> process I follow for merging such PRs is the
Doc's mentioning 'how to document' must be updated.
I found http://ant.apache.org/ivy/write-doc.html Some more?
Jan
> -Ursprüngliche Nachricht-
> Von: Jaikiran Pai [mailto:jai.forums2...@gmail.com]
> Gesendet: Montag, 19. Juni 2017 04:52
> An: Ant Developers List
> Betreff: Ivy - we have
> Le 19 juin 2017 à 05:14, Jaikiran Pai a écrit :
>
> We have (read only) github repos which back our main ASF git repos (consider
> the github ant-ivy repo which is a read-only mirror of ASF git repo). Users
> submit pull requests to our github repos and the process
I was reading up some docs and happened to find this page
http://ant.apache.org/nightlies.html which lists the Ant/Ivy jobs. Turns out we
also have Teamcity builds for Ivy and they have been failing since we moved to
Java 1.7[1]. Does any of us have access to those setups to configure it
Looks like infra needs to change security policy to unlimited crypto
strength. That is documented in build.xml
Gintas
2017-06-19 12:28 GMT+02:00 Jaikiran Pai :
> I was reading up some docs and happened to find this page
> http://ant.apache.org/nightlies.html which
On 2017-06-19, Jaikiran Pai wrote:
> I was reading up some docs and happened to find this page
> http://ant.apache.org/nightlies.html which lists the Ant/Ivy
> jobs. Turns out we also have Teamcity builds for Ivy and they have
> been failing since we moved to Java 1.7[1].
Are we maintaining the
Policy files in JRE must be replaced; here's the link for Java 8
http://www.oracle.com/technetwork/java/javase/downloads/jce8-download-2133166.html
Gintas
2017-06-19 13:02 GMT+02:00 Stefan Bodewig :
> On 2017-06-19, Jaikiran Pai wrote:
>
> > I was reading up some docs and
14 matches
Mail list logo