Re: [PR] Fix copy&paste error in signjar documentation [ant]

bodewig commented on PR #214: URL: https://github.com/apache/ant/pull/214#issuecomment-2465236081 thanks -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-m

Re: [PR] Fix copy&paste error in signjar documentation [ant]

bodewig merged PR #214: URL: https://github.com/apache/ant/pull/214 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For

[PR] Fix copy&paste error in signjar documentation [ant]

Vampire opened a new pull request, #214: URL: https://github.com/apache/ant/pull/214 (no comment) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: de

Re: [PR] IVY-1651 Augment 'Child elements’ section of 'File System Resolver' documentation [ant-ivy]

maartenc commented on PR #101: URL: https://github.com/apache/ant-ivy/pull/101#issuecomment-243835 I think we should link to https://ant.apache.org/ivy/history/2.5.2/concept.html where the possible tokens inside a pattern are discussed. In addition, the https://ant.apache.org/ivy/histo

Re: [PR] IVY-1651 Augment 'Child elements’ section of 'File System Resolver' documentation [ant-ivy]

Seros commented on PR #101: URL: https://github.com/apache/ant-ivy/pull/101#issuecomment-2133442798 Hey ^^ Just wanted to ask when we can expect this change to be merged as it seems it's the only one left for the [next version 2.5.3](https://issues.apache.org/jira/issues?jql=project%20%3D%2

[PR] IVY-1651 Augment 'Child elements’ section of 'File System Resolver' documentation [ant-ivy]

lewismc opened a new pull request, #101: URL: https://github.com/apache/ant-ivy/pull/101 PR to address https://issues.apache.org/jira/browse/IVY-1651 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go

Re: [PR] fix example documentation in manual [ant]

jaikiran merged PR #208: URL: https://github.com/apache/ant/pull/208 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For

Re: [PR] fix example documentation in manual [ant]

jaikiran commented on PR #208: URL: https://github.com/apache/ant/pull/208#issuecomment-1956990993 Thank you Dave for this fix. The change looks correct to me and matches the `compilerarg` documentation of the `javac` task. -- This is an automated message from the Apache Git

[PR] fix example documentation in manual [ant]

mebigfatguy opened a new pull request, #208: URL: https://github.com/apache/ant/pull/208 documentation says the attribute name for is arg, but it's value. Updated doc. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub an

[GitHub] [ant] jmkf commented on issue #95: Refer to Java 8 documentation for consistency

jmkf commented on issue #95: Refer to Java 8 documentation for consistency URL: https://github.com/apache/ant/pull/95#issuecomment-498033078 Thanks for the improvement on the javadoc This is an automated message from the

[GitHub] [ant] jmkf merged pull request #95: Refer to Java 8 documentation for consistency

jmkf merged pull request #95: Refer to Java 8 documentation for consistency URL: https://github.com/apache/ant/pull/95 This is an automated message from the Apache Git Service. To respond to the message, please log on to

[GitHub] [ant] asfgit commented on issue #95: Refer to Java 8 documentation for consistency

asfgit commented on issue #95: Refer to Java 8 documentation for consistency URL: https://github.com/apache/ant/pull/95#issuecomment-498032089 Refer to this link for build results (access rights to CI server needed): https://builds.apache.org/job/Ant%20Github-PR-Windows/130

[GitHub] [ant] asfgit commented on issue #95: Refer to Java 8 documentation for consistency

asfgit commented on issue #95: Refer to Java 8 documentation for consistency URL: https://github.com/apache/ant/pull/95#issuecomment-498032057 Refer to this link for build results (access rights to CI server needed): https://builds.apache.org/job/Ant%20Github-PR-Linux/124

[GitHub] [ant] asfgit commented on issue #95: Refer to Java 8 documentation for consistency

asfgit commented on issue #95: Refer to Java 8 documentation for consistency URL: https://github.com/apache/ant/pull/95#issuecomment-498031225 Refer to this link for build results (access rights to CI server needed): https://builds.apache.org/job/Ant%20Github-PR-Linux/123

[GitHub] [ant] asfgit commented on issue #95: Refer to Java 8 documentation for consistency

asfgit commented on issue #95: Refer to Java 8 documentation for consistency URL: https://github.com/apache/ant/pull/95#issuecomment-498031230 Refer to this link for build results (access rights to CI server needed): https://builds.apache.org/job/Ant%20Github-PR-Windows/129

[GitHub] [ant] asfgit commented on issue #95: Refer to Java 8 documentation for consistency

asfgit commented on issue #95: Refer to Java 8 documentation for consistency URL: https://github.com/apache/ant/pull/95#issuecomment-497997900 Refer to this link for build results (access rights to CI server needed): https://builds.apache.org/job/Ant%20Github-PR-Linux/121

[GitHub] [ant] asfgit commented on issue #95: Refer to Java 8 documentation for consistency

asfgit commented on issue #95: Refer to Java 8 documentation for consistency URL: https://github.com/apache/ant/pull/95#issuecomment-497997906 Refer to this link for build results (access rights to CI server needed): https://builds.apache.org/job/Ant%20Github-PR-Windows/127

[GitHub] [ant] twogee opened a new pull request #95: Refer to Java 8 documentation for consistency

twogee opened a new pull request #95: Refer to Java 8 documentation for consistency URL: https://github.com/apache/ant/pull/95 http to https changes in references also introduced Java 5 to 8 changes, so let's be consi

Re: Ivy old docs removed - documentation now resides under asciidoc

-13 16:06 GMT+01:00 Jan Matèrne (jhm) : > >> May /docs-to-convert ;) >> >> A directory /doc makes the expectation to find (actual) documentation. >> >> >> Jan >> >> > -Ursprüngliche Nachricht- >> > Von: Gintautas Grigelionis [mai

Re: Ivy old docs removed - documentation now resides under asciidoc

I converted them, and they're dev-related. You can read them directly on GitHub :-) Gintas 2018-03-13 16:06 GMT+01:00 Jan Matèrne (jhm) : > May /docs-to-convert ;) > > A directory /doc makes the expectation to find (actual) documentation. > > > Jan > > &

AW: Ivy old docs removed - documentation now resides under asciidoc

May /docs-to-convert ;) A directory /doc makes the expectation to find (actual) documentation. Jan > -Ursprüngliche Nachricht- > Von: Gintautas Grigelionis [mailto:g.grigelio...@gmail.com] > Gesendet: Dienstag, 13. März 2018 10:14 > An: Ant Developers List > Betreff: R

Re: Ivy old docs removed - documentation now resides under asciidoc

There is some documentation that has not been converted to asciidoc (eg ideas.txt or conflict-solving-algo.html). I will put them into dev, or does anyone have a better idea? Gintas 2018-03-07 11:49 GMT+01:00 Jaikiran Pai : > A while back we moved Ivy's documentation to Asciidoc. That a

Re: Ant documentation

2018-03-02 13:13 GMT+01:00 Stefan Bodewig : > > All I wanted to say, keeping things visually consistent helps > > understanding. So, my simple set of rules is: > > >- is for attributes > >- is for values > >- is for shell variable names/property name/CLI options and > input > >

Ivy old docs removed - documentation now resides under asciidoc

A while back we moved Ivy's documentation to Asciidoc. That automated migration, thanks mainly to Nicolas, went off fine and we fixed whatever issues we discovered in the migrated docs over a period of time. At this point, the previous HTML and xooki based documentation is no longer neede

Re: Ant documentation

2018-03-02 13:13 GMT+01:00 Stefan Bodewig : > On 2018-03-02, Gintautas Grigelionis wrote: > > > 2018-03-02 9:54 GMT+01:00 Stefan Bodewig : > > >> On 2018-03-01, Stefan Bodewig wrote: > > On Thu, Mar 1, 2018 at 7:28 AM, Gintautas Grigelionis < > g.grigelio...@gmail.com> wrote: > > > I

Re: Ant documentation

On 2018-03-02, Gintautas Grigelionis wrote: > 2018-03-02 9:54 GMT+01:00 Stefan Bodewig : >> On 2018-03-01, Stefan Bodewig wrote: On Thu, Mar 1, 2018 at 7:28 AM, Gintautas Grigelionis < g.grigelio...@gmail.com> wrote: > I tried then to use the replacement tags as consistently as >>

Re: Ant documentation

nd of rules keep people from > > writing docs :-) > > This comment isn't fair and I should have known better, sorry. > > Whenever people who are new to Open Source ask where to contribute I > first point out that it is supposed to be fun and they should pick the > th

Re: Ant documentation

etter, sorry. Whenever people who are new to Open Source ask where to contribute I first point out that it is supposed to be fun and they should pick the thing they enjoy most. For most developers I know (including myself) writing documentation is not something they enjoy. It's a chore that n

Re: Ant documentation

2018-03-02 7:44 GMT+01:00 Jan Matèrne (jhm) : > > > > > I made an attempt to convert the manual to HTML 5, the rationale > > > > being > > > > > that HTML 5 deprecates tt tag and recommends to replace it with > > > > > tags like code, kbd, samp and var, which could be used in a more > > > > consis

AW: Ant documentation

> > > > I made an attempt to convert the manual to HTML 5, the rationale > > > being > > > > that HTML 5 deprecates tt tag and recommends to replace it with > > > > tags like code, kbd, samp and var, which could be used in a more > > > consistent > > > > way to achieve something closer to a semanti

Re: Ant documentation

2018-03-01 10:43 GMT+01:00 Jan Matèrne (jhm) : > > > I made an attempt to convert the manual to HTML 5, the rationale > > being > > > that HTML 5 deprecates tt tag and recommends to replace it with tags > > > like code, kbd, samp and var, which could be used in a more > > consistent > > > way to a

AW: Ant documentation

> > I made an attempt to convert the manual to HTML 5, the rationale > being > > that HTML 5 deprecates tt tag and recommends to replace it with tags > > like code, kbd, samp and var, which could be used in a more > consistent > > way to achieve something closer to a semantic markup. > > > > I trie

Re: Ant documentation

On 2018-03-01, Dominique Devienne wrote: > On Thu, Mar 1, 2018 at 7:28 AM, Gintautas Grigelionis < > g.grigelio...@gmail.com> wrote: >> I tried then to use the replacement tags as consistently as possible in >> such a large body of text, but I realised that we perhaps need a kind of a >> style gu

Re: Ant documentation

On Thu, Mar 1, 2018 at 7:28 AM, Gintautas Grigelionis < g.grigelio...@gmail.com> wrote: > I made an attempt to convert the manual to HTML 5, the rationale being that > HTML 5 deprecates tt tag and recommends to replace it with tags like code, > kbd, samp and var, which could be used in a more cons

Ant documentation

I made an attempt to convert the manual to HTML 5, the rationale being that HTML 5 deprecates tt tag and recommends to replace it with tags like code, kbd, samp and var, which could be used in a more consistent way to achieve something closer to a semantic markup. I tried then to use the replaceme

Re: [1/6] ant-ivy git commit: Documentation review (partly inspired by IVY-1089) [Forced Update!]

gs during a build. Then every Ivy task >> should specify the settings it uses using the `settingsRef` attribute. >>[source,xml] >> >> >> http://git-wip-us.apache.org/repos/asf/ant-ivy/blob/b693aa0a/asciidoc/use/var.adoc >> -

Re: [1/6] ant-ivy git commit: Documentation review (partly inspired by IVY-1089) [Forced Update!]

out (in fact it's why we use yEd), so y == Preparation -First you have to generate a graphml file. Simply call the report task (see ivy use documentation) for that. +First you have to generate a GraphML file. Simply call the report task (see ivy use documentation) for that. -== Ste

Re: Documentation-related issues in Jira

gt; > > On 23/08/17 12:12 AM, Gintautas Grigelionis wrote: > >> Earlier, I wrote about the amount of documentation-related issues in Jira. >> There are 27 of them still open [1], and some of them could be closed >> right >> away. >> I would be glad to help,

Re: Documentation-related issues in Jira

Thanks, somehow I missed the pencil in my profile :-) I'll start commenting the issues. Gintas 2017-08-23 7:44 GMT+02:00 Stefan Bodewig : > On 2017-08-22, Gintautas Grigelionis wrote: > > > I would be glad to help, but I have no privileges. Is there somebody who > > could help me? > > I seem to

Re: Documentation-related issues in Jira

On 2017-08-22, Gintautas Grigelionis wrote: > I would be glad to help, but I have no privileges. Is there somebody who > could help me? I seem to be administrator for the Ivy JIRA Project, I've added both your accounts (gintas and twogee) to the committers group. I didn't know which one of these

Re: Documentation-related issues in Jira

s weekend. -Jaikiran On 23/08/17 12:12 AM, Gintautas Grigelionis wrote: Earlier, I wrote about the amount of documentation-related issues in Jira. There are 27 of them still open [1], and some of them could be closed right away. I would be glad to help, but I have no privileges. Is there somebody

Documentation-related issues in Jira

Earlier, I wrote about the amount of documentation-related issues in Jira. There are 27 of them still open [1], and some of them could be closed right away. I would be glad to help, but I have no privileges. Is there somebody who could help me? Thanks, Gintas P.S. I noticed that I misspelled my

[GitHub] ant-ivyde issue #6: IvyDE credentials documentation added and cleanup done

Github user nlalevee commented on the issue: https://github.com/apache/ant-ivyde/pull/6 Merged. The feature is now in master and will be available with the next release. Thank you very much Alexander! --- If your project is set up for it, you can reply to this email and have your

[GitHub] ant-ivyde pull request #6: IvyDE credentials documentation added and cleanup...

Github user asfgit closed the pull request at: https://github.com/apache/ant-ivyde/pull/6 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is ena

[GitHub] ant-ivyde pull request #6: IvyDE credentials documentation added and cleanup...

GitHub user alex-bl opened a pull request: https://github.com/apache/ant-ivyde/pull/6 IvyDE credentials documentation added and cleanup done This pull request includes: - Project cleanup (a deprecated and unused class was removed) - IvyDE credential extension documentation

Re: ant-ivy git commit: avoid generating the reports in the folder where the html of the documentation is generated

older where the html of the > documentation is generated > > > Project: http://git-wip-us.apache.org/repos/asf/ant-ivy/repo > Commit: http://git-wip-us.apache.org/repos/asf/ant-ivy/commit/eeb79e10 > Tree: http://git-wip-us.apache.org/repos/asf/ant-ivy/tree/eeb79e10 > Diff: http://git-w

[GitHub] ant-ivy pull request #47: Move to asciidoc for documentation

Github user asfgit closed the pull request at: https://github.com/apache/ant-ivy/pull/47 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enab

[GitHub] ant-ivy pull request #47: Move to asciidoc for documentation

GitHub user jaikiran opened a pull request: https://github.com/apache/ant-ivy/pull/47 Move to asciidoc for documentation This PR contains multiple commits, which together are a first step towards moving the current `xooki` backed documentation to `asciidoc`. The commits are

Re: Ivy website - fixing a Quickstart documentation live

ilt these tutorials on 2.4.0 tag of Ivy project, generated those logs and then regenerated the site with these logs in the relevant folder. The generated documentation now has these output inlined correctly in the quickstart and various other docs. The attached patch was generated with https://svn.a

Re: Ivy documentation with asciidoc

. The original Ivy logo is unfortunately too low resolution > >> for > >>> simple tracing :-( Is this all there is? > > >> The only version of the logo we have is in the svn. > > > > That's a pity. > > > A couple of related questions: Apache

Re: Ivy documentation with asciidoc

? >> The only version of the logo we have is in the svn. > That's a pity. > A couple of related questions: Apache Incubator has changed the logo, > should the new logo from their press release kit be used in documentation > instead? Does the Ivy doc include the Incubator

Re: Ivy documentation with asciidoc

t's a pity. A couple of related questions: Apache Incubator has changed the logo, should the new logo from their press release kit be used in documentation instead? Next, there is an "Apache Ant Group" logo that looks like the regular ASF feather <https://commons.wikimedia.org/wik

Re: Ivy documentation with asciidoc

> Le 31 mai 2017 à 19:47, Gintautas Grigelionis a > écrit : > > I looked at the documentation: both > http://ant.apache.org/ivy/history/trunk/tutorial/start.html > <http://ant.apache.org/ivy/history/trunk/tutorial/start.html> and > https://ant.apache.org/ivy/histor

Re: Ivy documentation with asciidoc

I looked at the documentation: both http://ant.apache.org/ivy/history/trunk/tutorial/start.html and https://ant.apache.org/ivy/history/latest-milestone/tutorial/start.html have black rectangles. Also, external links must be pruned and/or directed to Internet Archive :-( The tutorial of yEd must

Re: Ivy documentation with asciidoc

> Le 31 mai 2017 à 17:53, J Pai a écrit : > > > On 31-May-2017, at 9:02 PM, Nicolas Lalevée > wrote: > > >> Le 31 mai 2017 à 15:34, J Pai a écrit : >> >> One thing I just noticed in the generated adoc files is that “external” >> links that are part of th

Re: Ivy documentation with asciidoc

On 31-May-2017, at 9:02 PM, Nicolas Lalevée wrote: > Le 31 mai 2017 à 15:34, J Pai a écrit : > > One thing I just noticed in the generated adoc files is that “external” links > that are part of the original xooki backed .html files are not being > generated as links in the converted adoc. T

Re: Ivy documentation with asciidoc

ts to svnpubsub on release? > > If you look at the menu on the left, it is present on each page, so it means > that for any new file or deleted file, every page has to be regenerated. The > consequence it that generating a page of the site has to be aware of the list > of all

Re: Ivy documentation with asciidoc

t worst case scenario, can't you just >> commit the parts to svnpubsub on release? > > If you look at the menu on the left, it is present on each page, so it means > that for any new file or deleted file, every page has to be regenerated. The > consequence it th

Re: Ivy documentation with asciidoc

rst case scenario, can't you > just > > commit the parts to svnpubsub on release? > > If you look at the menu on the left, it is present on each page, so it > means that for any new file or deleted file, every page has to be > regenerated. The consequence it that generating a

Re: Ivy documentation with asciidoc

nu on the left, it is present on each page, so it means that for any new file or deleted file, every page has to be regenerated. The consequence it that generating a page of the site has to be aware of the list of all the pages of the documentation. But we can imagine that we uncouple the

Re: Ivy documentation with asciidoc

s that for any new file or deleted file, every page has to be regenerated. The consequence it that generating a page of the site has to be aware of the list of all the pages of the documentation. But we can imagine that we uncouple the documentation, like it is being done for the old versions o

Re: Ivy website - fixing a Quickstart documentation live

underlying html looks like it has tags with no content. > >>> > >>> > >>> The way these tutorial docs are generated, during the build, it > triggers > >>> the build of quickstart examples and dumps the logs into files. The log > >>> files a

Re: Ivy website - fixing a Quickstart documentation live

d dumps the logs into files. The log >>> files are then referred to via xooki references and the contents of those >>> log files are inlined within the div tags. So I went ahead and built >> these >>> tutorials on 2.4.0 tag of Ivy project, generated those logs and then >

Re: Ivy website - fixing a Quickstart documentation live

ing the build, it triggers > > the build of quickstart examples and dumps the logs into files. The log > > files are then referred to via xooki references and the contents of those > > log files are inlined within the div tags. So I went ahead and built > these > > tutorials o

Re: Ivy website - fixing a Quickstart documentation live

> regenerated the site with these logs in the relevant folder. The generated > documentation now has these output inlined correctly in the quickstart and > various other docs. > > The attached patch was generated with https://svn.apache.org/repos/ > asf/ant/site/ as the root of

Re: Ivy website - fixing a Quickstart documentation live

So I went ahead and built these tutorials on 2.4.0 tag of Ivy project, generated those logs and then regenerated the site with these logs in the relevant folder. The generated documentation now has these output inlined correctly in the quickstart and various other docs. The attached patch was

Re: Ivy website - fixing a Quickstart documentation live

> since the migration to git. For Ivy and IvyDE, part of the site is built > from the source for the projects. It used to be managed via svn:externals. > Now there are ant tasks to run to the fetch of the sources. I have found an > old discussion [1] we had about it which should help you.

Re: Ivy website - fixing a Quickstart documentation live

svn:externals. Now there are ant tasks to run to the fetch of the sources. I have found an old discussion [1] we had about it which should help you. By the way, the Ivy documentation is managed by an hand crafted html editor, xooki, just is good but quite slow. I did some work some time ago (2 years

AW: Ivy website - fixing a Quickstart documentation live

+1 for asciidoc. Using xooki means using a tool only few people know ... Jan > -Ursprüngliche Nachricht- > Von: J Pai [mailto:jai.forums2...@gmail.com] > Gesendet: Donnerstag, 25. Mai 2017 14:03 > An: Ant Developers List > Betreff: Re: Ivy website - fixing a Quickstart doc

Re: Ivy documentation with asciidoc

7;t you just > commit the parts to svnpubsub on release? If you look at the menu on the left, it is present on each page, so it means that for any new file or deleted file, every page has to be regenerated. The consequence it that generating a page of the site has to be aware of the list

Re: Ivy documentation with asciidoc

t.org/tmp/ivy- > asciidoc/index.html> > > It seems pretty good, but I didn’t looked to most of the pages. > > Before going further, we need to figure out how it would be integrated to > the website since it is also managed by xooki. The site and the > documentation are tidily coup

Ivy documentation with asciidoc

nd the documentation are tidily coupled by the toc which is managed by xooki. Nicolas

Re: Ivy website - fixing a Quickstart documentation live

On 25-May-2017, at 5:26 PM, Nicolas Lalevée wrote: > By the way, the Ivy documentation is managed by an hand crafted html editor, > xooki, just is good but quite slow. I did some work some time ago (2 years > ago, time flies!) to try to migrate to asciidoc [2]. I can even

Re: Ivy website - fixing a Quickstart documentation live

. Now there are ant tasks to run to the fetch of the sources. I have found an old discussion [1] we had about it which should help you. By the way, the Ivy documentation is managed by an hand crafted html editor, xooki, just is good but quite slow. I did some work some time ago (2 years ago, time

Re: Ivy website - fixing a Quickstart documentation live

By the way... we'll need ant-ivy-site-styles , too :-) Gintas

Re: Ivy website - fixing a Quickstart documentation live

r from ant-site-source or from documentation generated by builds for respective project. Gintas 2017-05-25 8:30 GMT+02:00 Jan Matèrne (jhm) : > The whole site is in svn and a server process (svnpubsub i think) is > getting > the 'publish' files and pushing them to the webserv

AW: Ivy website - fixing a Quickstart documentation live

hem. Jan > -Ursprüngliche Nachricht- > Von: Gintautas Grigelionis [mailto:g.grigelio...@gmail.com] > Gesendet: Donnerstag, 25. Mai 2017 06:29 > An: Ant Developers List > Betreff: Re: Ivy website - fixing a Quickstart documentation live > > Is the documentation still

Re: Ivy website - fixing a Quickstart documentation live

Is the documentation still in SVN? IVY-1542 is about site/sources/style which is shared by Ivy and IvyDE. Are there any plans about migrating this to Git and separating the source repo from publication repo? Gintas 2017-05-25 6:12 GMT+02:00 J Pai : > What would be the process of having the l

Ivy website - fixing a Quickstart documentation live

What would be the process of having the live docs of Ivy project updated to fix/update an issue in the documentation[1]? The quickstart documentation refers to certain log files that get auto-generated during the doc build process. It looks like those log files weren’t uploaded and are

Re: Ant Documentation Page Error (javac task "debug" tag)

On 2016-07-01, John Argentieri wrote: > This page has a note which I think may be causing some confusion. Is > the javac "debug" tag for ant really supposed to be "off"/"true"? or > is it really supposed to be "on"/"off"? If so, the last sentence is > incorrect...: Ant understand true/yes/on and

Ant Documentation Page Error (javac task "debug" tag)

Dear Ant Devs, This page has a note which I think may be causing some confusion. Is the javac "debug" tag for ant really supposed to be "off"/"true"? or is it really supposed to be "on"/"off"? If so, the last sentence is incorrect...: https://ant.apache.org/manual/Tasks/javac.html Javac Tas

ant pull request: fix incorrect attribute in the Zip Task documentation

Github user jwadamson closed the pull request at: https://github.com/apache/ant/pull/2 - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org

ant pull request: fix incorrect attribute in the Zip Task documentation

GitHub user jwadamson opened a pull request: https://github.com/apache/ant/pull/2 fix incorrect attribute in the Zip Task documentation I copied this example to add to a build file, and it exploded. The correct attribute is visible in the example immediately preceding this one

Re: How to build the Ant job to create automated documentation of the ETL source code in pentaho Data Integration

n Jan 11, 2013, at 12:01 AM, sandhya.kac...@gmail.com wrote: > Hello, > > o build the Ant job to create automated documentation of the ETL source code > in pentaho Data Integration. > > Can anyone provide me some ideas in this regard. > >

Re: Pedantic Documentation Issue

On 2011-10-24, John Jenkins wrote: > The documentation for the "excludes" parameter is either incorrect or > there is an additional "exclude" parameter that means something > slightly different on: > http://ant.apache.org/manual/Tasks/war The XML element supp

Pedantic Documentation Issue

The documentation for the "excludes" parameter is either incorrect or there is an additional "exclude" parameter that means something slightly different on: http://ant.apache.org/manual/Tasks/war It complains when I gave it one file with the "excludes" parame

AW: Ant Task Documentation

nr...@web.de > Betreff: Re: Ant Task Documentation > > 2011/6/16 Grüner Heinrich : > > > >     Hi, > > > >     I've written a couple of own tasks for which I want to generate > >     help files via javadoc. > >     This documentation should look like

Re: Ant Task Documentation

2011/6/16 Grüner Heinrich : > >     Hi, > >     I've written a couple of own tasks for which I want to generate >     help files via javadoc. >     This documentation should look like the original ant documentation. >     Can anyone provide a javadoc set up or doclet? >

Ant Task Documentation

Hi, I've written a couple of own tasks for which I want to generate help files via javadoc. This documentation should look like the original ant documentation. Can anyone provide a javadoc set up or doclet? Are there any efforts to generate the documentati

Re: DO NOT REPLY [Bug 49569] New: Documentation for previous versions should be available online

On 7/13/2010 12:30 AM, Stefan Bodewig wrote: On 2010-07-12, Antoine Levy-Lambert wrote: On 7/9/2010 7:14 AM, Stefan Bodewig wrote: I volunteer to change the distribution target, release instructions and to create archives for Ant 1.6.5 to 1.8.1 unless anybody objects.

Re: DO NOT REPLY [Bug 49569] New: Documentation for previous versions should be available online

On 2010-07-12, Antoine Levy-Lambert wrote: > On 7/9/2010 7:14 AM, Stefan Bodewig wrote: >> I volunteer to change the distribution target, release instructions and >> to create archives for Ant 1.6.5 to 1.8.1 unless anybody objects. > How is this going to work ? Not completely sure, but most lik

Re: DO NOT REPLY [Bug 49569] New: Documentation for previous versions should be available online

On 7/9/2010 7:14 AM, Stefan Bodewig wrote: It would be pretty simple to create ZIPs/tarballs of the docs subfolder as separate release artifacts and publish them side by side with the source and binary releases. They wouldn't need to be signed or hashed. Also, it would be pretty simple to do so

Re: DO NOT REPLY [Bug 49569] New: Documentation for previous versions should be available online

> At the top of the online Ant manual, it says: > "This is the manual for version 1.8.1 of Apache Ant. If your version > of Ant (as verified with ant -version) is older or newer than this > version then this is not the correct manual set. Please use the > documentation appropr

Re: sync task documentation

On 2009-03-11, Samir SAADA wrote: > I have noticed a version confusion in documentation, for a sync task > nested element. The task sync exists since the 1.6.0; but > preserveInTarget element appeared in the 1.7.0 version of ant. Thanks. Fixed in svn with revision 763656

sync task documentation

Hi all, I have noticed a version confusion in documentation, for a sync task nested element. The task sync exists since the 1.6.0; but preserveInTarget element appeared in the 1.7.0 version of ant. http://ant.apache.org/manual/CoreTasks/sync.html Regards

Re: Documentation Clarification

2009/2/10 Steve Appling : > I am working on a patch with some minor edits (mostly typos and > grammatical errors) to the documentation, but have a question about the > meaning of one line that just doesn't make sense for me. > > The "How does it work" page > (

Re: Documentation Clarification

To clarify - it is only Ivy tutorial documentation I am patching. Steve Appling wrote: I am working on a patch with some minor edits (mostly typos and grammatical errors) to the documentation, but have a question about the meaning of one line that just doesn't make sense for me. The &quo

Documentation Clarification

I am working on a patch with some minor edits (mostly typos and grammatical errors) to the documentation, but have a question about the meaning of one line that just doesn't make sense for me. The "How does it work" page (http://ant.apache.org/ivy/history/latest-release/principl

Re: documentation for [#IVY-848] Add publish support to URL resolver

On Mon, Aug 11, 2008 at 8:47 AM, Scheper, Erik-Berndt < [EMAIL PROTECTED]> wrote: > Hi, > > I just noticed that publish support has been added for the URL resolver > (IVY-848 in jira). > Wouldn't it be nice to modify the documentation to reflect this change? I agree.

documentation for [#IVY-848] Add publish support to URL resolver

Hi, I just noticed that publish support has been added for the URL resolver (IVY-848 in jira). Wouldn't it be nice to modify the documentation to reflect this change? Regards, Erik-Berndt Disclaimer: This message contains information that may be privileged or confidential and is

  1   2   3   4   >