Re: Ivy - we have now moved to asciidoc for docs

[Jaikiran Pai]

> 
> 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 Nicolas to migrate the xooki backed HTML 
>> docs to asciidoc. This tool auto-generated the asciidoc text and for most 
>> part no other changes were needed. However, there are some fixes the 
>> generated asciidoc will need which I’m doing and will continue to do in the 
>> coming days to fix any issues with the generated doc. Once the fixes are 
>> done, soon, we’ll remove the xooki backed documentation completely from our 
>> git repo. For now though, any new documentation or changes should go into 
>> the asciidoc files.
> 
> I did a general grep about finding non translated html markup, and I have 
> cleaned the ones I have found.
> I have pushed the result here: http://people.apache.org/~hibou/doc/ 
> 
> 
> Probably we can start pushing it to the site, since there is section 
> dedicated to the trunk version of the doc (which should be probably renamed 
> master).
> http://ant.apache.org/ivy/history/trunk/index.html 
> 
> It would be an opportunity to get an idea of what would it mean when a 
> release will happen.

I actually forgot to send a mail yesterday, but I setup our nightly Ivy job on 
Jenkins to publish the latest generated docs as build artifact so that it gives 
everyone a chance to view/review it. It’s here 
https://builds.apache.org/view/A/view/Ant/job/Ivy-NightlyDistribution/lastSuccessfulBuild/artifact/build/.
 We could just push it to the site under master but I wasn’t too sure if it’s 
the right time to do that or if we should just cleanup the rest of the issues 
in the doc before starting to push it there.

> 
> And just an idea: since there are a lot of pages, maybe we could organize a 
> review at many, without useless double checks. I see 4 big parts in the doc: 
> the ant tasks, the pages related to the ivy file, the pages related to the 
> ivysettings, and the other pages. If 4 volunteers can do a quick review of 
> each page, I think we can be pretty confident that we didn’t leave any 
> ugliness somewhere. The goal wouldn’t to do a fine grain review, but ensure 
> that everything is readable. wdyt ?
> 

Sounds a good idea. I’ll start off with the “Settings” which relates to the Ivy 
settings file.

-Jaikiran



-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: Ivy - we have now moved to asciidoc for docs

[Jaikiran Pai]

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  wrote:


> 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 Nachricht-
>> Von: Jaikiran Pai [mailto:jai.forums2...@gmail.com]
>> Gesendet: Montag, 19. Juni 2017 04:52
>> An: Ant Developers List
>> Betreff: Ivy - we have now moved to asciidoc for docs
>> 
>> 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 text and for most part no other changes were needed. However,
>> there are some fixes the generated asciidoc will need which I’m doing
>> and will continue to do in the coming days to fix any issues with the
>> generated doc. Once the fixes are done, soon, we’ll remove the xooki
>> backed documentation completely from our git repo. For now though, any
>> new documentation or changes should go into the asciidoc files.
>> 
>> -Jaikiran
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional
>> commands, e-mail: dev-h...@ant.apache.org
> 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
> For additional commands, e-mail: dev-h...@ant.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: Ivy - we have now moved to asciidoc for docs

[Gintautas Grigelionis]

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.
> > 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 Nachricht-
> >> Von: Jaikiran Pai [mailto:jai.forums2...@gmail.com]
> >> Gesendet: Montag, 19. Juni 2017 04:52
> >> An: Ant Developers List
> >> Betreff: Ivy - we have now moved to asciidoc for docs
> >>
> >> 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 text and for most part no other changes were needed. However,
> >> there are some fixes the generated asciidoc will need which I’m doing
> >> and will continue to do in the coming days to fix any issues with the
> >> generated doc. Once the fixes are done, soon, we’ll remove the xooki
> >> backed documentation completely from our git repo. For now though, any
> >> new documentation or changes should go into the asciidoc files.
> >>
> >> -Jaikiran
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional
> >> commands, e-mail: dev-h...@ant.apache.org
> >
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
> > For additional commands, e-mail: dev-h...@ant.apache.org
> >
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
> For additional commands, e-mail: dev-h...@ant.apache.org
>
>

Re: Ivy - we have now moved to asciidoc for docs

[Nicolas Lalevée]

> 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 Nachricht-
>> Von: Jaikiran Pai [mailto:jai.forums2...@gmail.com]
>> Gesendet: Montag, 19. Juni 2017 04:52
>> An: Ant Developers List
>> Betreff: Ivy - we have now moved to asciidoc for docs
>> 
>> 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 text and for most part no other changes were needed. However,
>> there are some fixes the generated asciidoc will need which I’m doing
>> and will continue to do in the coming days to fix any issues with the
>> generated doc. Once the fixes are done, soon, we’ll remove the xooki
>> backed documentation completely from our git repo. For now though, any
>> new documentation or changes should go into the asciidoc files.
>> 
>> -Jaikiran
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional
>> commands, e-mail: dev-h...@ant.apache.org
> 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
> For additional commands, e-mail: dev-h...@ant.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: Ivy - we have now moved to asciidoc for docs

[Nicolas Lalevée]

> 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 text and for most 
> part no other changes were needed. However, there are some fixes the 
> generated asciidoc will need which I’m doing and will continue to do in the 
> coming days to fix any issues with the generated doc. Once the fixes are 
> done, soon, we’ll remove the xooki backed documentation completely from our 
> git repo. For now though, any new documentation or changes should go into the 
> asciidoc files.

I did a general grep about finding non translated html markup, and I have 
cleaned the ones I have found.
I have pushed the result here: http://people.apache.org/~hibou/doc/ 


Probably we can start pushing it to the site, since there is section dedicated 
to the trunk version of the doc (which should be probably renamed master).
http://ant.apache.org/ivy/history/trunk/index.html 

It would be an opportunity to get an idea of what would it mean when a release 
will happen.

I have noticed one bug in the generation of the toc. There is notion of 
abstract node, which has a title but no link, it shouldn’t be clickable. But 
for instance the node at Reference/Introduction is clickable, and sends to the 
home. This should be fixed. I mentioning it if somebody wants to look at it, 
before me. 

And just an idea: since there are a lot of pages, maybe we could organize a 
review at many, without useless double checks. I see 4 big parts in the doc: 
the ant tasks, the pages related to the ivy file, the pages related to the 
ivysettings, and the other pages. If 4 volunteers can do a quick review of each 
page, I think we can be pretty confident that we didn’t leave any ugliness 
somewhere. The goal wouldn’t to do a fine grain review, but ensure that 
everything is readable. wdyt ?

Nicolas

Re: Process for handling GitHub PRs and closing them

[Matt Sicker]

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, GitHub (and git in general) doesn't notice that it's merged, so it
doesn't auto-close. If you really want to rebase, there's no way around
adding an additional commit to add the magic "closes #N" message.

On 19 June 2017 at 09:48, Jaikiran Pai  wrote:

>
> 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 mirror of ASF git
> repo). Users submit pull requests to our github repos and the process I
> follow for merging such PRs is the “rebase” approach which looks something
> like this:
> >>
> >>
> >> - Fetch the PR locally (git fetch github pull/45/head:pr-45)
> >> - Checkout to that branch locally (git checkout pr-45)
> >> - Rebase that PR on top of latest ASF (upstream) repo (git rebase
> asf/master)
> >> - Run a short build, verify and push to ASF repo (git push asf
> pr-45:master)
> >>
> >> (assume 45 is the pull request id).
> >>
> >> So essentially, I rebase the commits from the PR on top of the latest
> master and then push to the ASF repos. All this works fine and the ASF
> repos get those changes. However, this doesn’t “close” the pull request on
> github.
> >>
> >> Apparently, the way to have the pull request closed is doing a actual
> “merge” of the pull request commits into the ASF repo instead of rebasing
> the commits.
> >>
> >> Then the other approach, which isn’t that clean IMO, is to push a
> commit to the ASF repo with a commit message which includes “This closes
> #X” where X is the pull request id. The ASF github bot then notices this
> commit messages and goes and closes the open PR.
> >>
> >> I usually prefer the rebase approach (the one I outlined above) for
> dealing with pull requests, since it gives a clean git commit tree. But
> clearly that doesn’t have a way to close the PR.
> >>
> >> Is there any preferred approach that we should follow with PRs?
> >
> > I agree with the approach you have. I have been lazy though, I just use
> the command line suggested in the email notifications, which makes things
> quite straight forward.
> >
> > I would just insist on trying to get the PR closed. Even if it may
> pollute the commit log, we should put the "This closes #X" message. And it
> can be viewed as a marker, just like we do with Jira. Also, we could make
> thing more explicit by specifying the full path of the github project: «
> closes apache/ant-ivy#123 ».
> > See the github documentation about it: https://help.github.com/
> articles/closing-issues-via-commit-messages/  articles/closing-issues-via-commit-messages/>
> >
>
>
> I wasn’t aware that this kind of commit message comes from and is
> supported by github itself. I was under the impression that this is
> something that the ASF github integration had introduced. Thanks for that
> link.
>
> What you suggest about making sure that the PR gets closed even if we end
> up with those mark commit messages, sounds fine to me and I’ll start doing
> that.
>
> -Jaikiran
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
> For additional commands, e-mail: dev-h...@ant.apache.org
>
>


-- 
Matt Sicker 

Re: Process for handling GitHub PRs and closing them

[Jaikiran Pai]

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 mirror of ASF git repo). Users 
>> submit pull requests to our github repos and the process I follow for 
>> merging such PRs is the “rebase” approach which looks something like this:
>> 
>> 
>> - Fetch the PR locally (git fetch github pull/45/head:pr-45)
>> - Checkout to that branch locally (git checkout pr-45)
>> - Rebase that PR on top of latest ASF (upstream) repo (git rebase asf/master)
>> - Run a short build, verify and push to ASF repo (git push asf pr-45:master)
>> 
>> (assume 45 is the pull request id).
>> 
>> So essentially, I rebase the commits from the PR on top of the latest master 
>> and then push to the ASF repos. All this works fine and the ASF repos get 
>> those changes. However, this doesn’t “close” the pull request on github.
>> 
>> Apparently, the way to have the pull request closed is doing a actual 
>> “merge” of the pull request commits into the ASF repo instead of rebasing 
>> the commits. 
>> 
>> Then the other approach, which isn’t that clean IMO, is to push a commit to 
>> the ASF repo with a commit message which includes “This closes #X” where X 
>> is the pull request id. The ASF github bot then notices this commit messages 
>> and goes and closes the open PR. 
>> 
>> I usually prefer the rebase approach (the one I outlined above) for dealing 
>> with pull requests, since it gives a clean git commit tree. But clearly that 
>> doesn’t have a way to close the PR. 
>> 
>> Is there any preferred approach that we should follow with PRs?
> 
> I agree with the approach you have. I have been lazy though, I just use the 
> command line suggested in the email notifications, which makes things quite 
> straight forward.
> 
> I would just insist on trying to get the PR closed. Even if it may pollute 
> the commit log, we should put the "This closes #X" message. And it can be 
> viewed as a marker, just like we do with Jira. Also, we could make thing more 
> explicit by specifying the full path of the github project: « closes 
> apache/ant-ivy#123 ».
> See the github documentation about it: 
> https://help.github.com/articles/closing-issues-via-commit-messages/ 
> 
> 


I wasn’t aware that this kind of commit message comes from and is supported by 
github itself. I was under the impression that this is something that the ASF 
github integration had introduced. Thanks for that link.

What you suggest about making sure that the PR gets closed even if we end up 
with those mark commit messages, sounds fine to me and I’ll start doing that.

-Jaikiran



-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: Ivy jobs on Teamcity need reconfiguring

[Gintautas Grigelionis]

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 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 job ourselves? Jan, have you got access to the
> credentials?
>
> Is this job doing anything that we couldn't do with builds.apache.org by
> now?
>
> Stefan
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
> For additional commands, e-mail: dev-h...@ant.apache.org
>
>

Re: Ivy jobs on Teamcity need reconfiguring

[Stefan Bodewig]

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 job ourselves? Jan, have you got access to the
credentials?

Is this job doing anything that we couldn't do with builds.apache.org by
now?

Stefan

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: Ivy jobs on Teamcity need reconfiguring

[Gintautas Grigelionis]

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 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 correctly to use Java 7? It’s a good thing that those jobs are
> running on Windows OS and will give us coverage on Windows. There are a few
> more Ivy related Teamcity jobs listed on that Ant project page which we
> probably will have to cleanup a bit.
>
>
> [1] https://teamcity.jetbrains.com/viewType.html?buildTypeId=bt125=1
>
> -Jaikiran
> -
> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
> For additional commands, e-mail: dev-h...@ant.apache.org
>
>

Ivy jobs on Teamcity need reconfiguring

[Jaikiran Pai]

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 
correctly to use Java 7? It’s a good thing that those jobs are running on 
Windows OS and will give us coverage on Windows. There are a few more Ivy 
related Teamcity jobs listed on that Ant project page which we probably will 
have to cleanup a bit.


[1] https://teamcity.jetbrains.com/viewType.html?buildTypeId=bt125=1

-Jaikiran
-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: Process for handling GitHub PRs and closing them

[Nicolas Lalevée]

> 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 follow for merging 
> such PRs is the “rebase” approach which looks something like this:
> 
> 
> - Fetch the PR locally (git fetch github pull/45/head:pr-45)
> - Checkout to that branch locally (git checkout pr-45)
> - Rebase that PR on top of latest ASF (upstream) repo (git rebase asf/master)
> - Run a short build, verify and push to ASF repo (git push asf pr-45:master)
> 
> (assume 45 is the pull request id).
> 
> So essentially, I rebase the commits from the PR on top of the latest master 
> and then push to the ASF repos. All this works fine and the ASF repos get 
> those changes. However, this doesn’t “close” the pull request on github.
> 
> Apparently, the way to have the pull request closed is doing a actual “merge” 
> of the pull request commits into the ASF repo instead of rebasing the 
> commits. 
> 
> Then the other approach, which isn’t that clean IMO, is to push a commit to 
> the ASF repo with a commit message which includes “This closes #X” where X is 
> the pull request id. The ASF github bot then notices this commit messages and 
> goes and closes the open PR. 
> 
> I usually prefer the rebase approach (the one I outlined above) for dealing 
> with pull requests, since it gives a clean git commit tree. But clearly that 
> doesn’t have a way to close the PR. 
> 
> Is there any preferred approach that we should follow with PRs?

I agree with the approach you have. I have been lazy though, I just use the 
command line suggested in the email notifications, which makes things quite 
straight forward.

I would just insist on trying to get the PR closed. Even if it may pollute the 
commit log, we should put the "This closes #X" message. And it can be viewed as 
a marker, just like we do with Jira. Also, we could make thing more explicit by 
specifying the full path of the github project: « closes apache/ant-ivy#123 ».
See the github documentation about it: 
https://help.github.com/articles/closing-issues-via-commit-messages/ 

> The other thing I had in mind, if we agree upon, is to have an enhancement 
> raised with the ASF infra team to allow adding some specific comment on the 
> open PR by a *committer* which then auto-closes the PR. Some comment like 
> “This PR is merged”.

I don’t think the ASF infra team can do something about it. The « This closes 
#x » is something that is supported by every github repository, this is not 
specific to the mirrored ASF repos.
Probably a simpler and better integration with github would be to make the PR 
tracker editable to ASF committers. And probably both github and asf teams have 
heard about that.

Nicolas

Re: Process for handling GitHub PRs and closing them

[Stefan Bodewig]

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 “rebase” approach which
> looks something like this:

> - Fetch the PR locally (git fetch github pull/45/head:pr-45)
> - Checkout to that branch locally (git checkout pr-45)
> - Rebase that PR on top of latest ASF (upstream) repo (git rebase asf/master)
> - Run a short build, verify and push to ASF repo (git push asf pr-45:master)

I tend to download 45.patch and "git am" it, but that's almost the same
as your first two steps. Most of the time I don't need to rebase. OTOH I
haven't got any problem with merge commits for PRs :-)

> Apparently, the way to have the pull request closed is doing a actual
> “merge” of the pull request commits into the ASF repo instead of
> rebasing the commits.

I'm not sure whether merging actually closes the PR, I've almost always
been forced to use a "closes #45" commit.

Most of the time there is some additional commit you have to perform,
like keeping track of the change inside the changelog. I use this extra
commit to close the PR. Not sure whether this is a best practice or even
a good practice.

Stefan

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

AW: Ivy - we have now moved to asciidoc for docs

[jhm]

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 now moved to asciidoc for docs
> 
> 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 text and for most part no other changes were needed. However,
> there are some fixes the generated asciidoc will need which I’m doing
> and will continue to do in the coming days to fix any issues with the
> generated doc. Once the fixes are done, soon, we’ll remove the xooki
> backed documentation completely from our git repo. For now though, any
> new documentation or changes should go into the asciidoc files.
> 
> -Jaikiran
> -
> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional
> commands, e-mail: dev-h...@ant.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org