[GitHub] ant pull request: scp task: update docs and add new ResourceCollec...

Github user asfgit closed the pull request at: https://github.com/apache/ant/pull/11 --- 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 enabled

[GitHub] ant pull request: scp task: update docs and add new ResourceCollec...

GitHub user rednoah opened a pull request: https://github.com/apache/ant/pull/11 scp task: update docs and add new ResourceCollection usage You can merge this pull request into a Git repository by running: $ git pull https://github.com/rednoah/ant scp-update-docs

DO NOT REPLY [Bug 29988] - Zip task Update mode adds all zip entries even though only one file is updated

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 29988] - Zip task Update mode adds all zip entries even though only one file is updated

gzilla/show_bug.cgi?id=29988 Zip task Update mode adds all zip entries even though only one file is updated --- Additional Comments From [EMAIL PROTECTED] 2004-11-05 16:05 --- This is because the tasks in Ant 1.4 simply were wrong. They only compared the files on your disk with the archive

DO NOT REPLY [Bug 29988] New: - Zip task Update mode adds all zip entries even though only one file is updated

gzilla/show_bug.cgi?id=29988 Zip task Update mode adds all zip entries even though only one file is updated Summary: Zip task Update mode adds all zip entries even though only one file is updated Product: Ant Version: 1.6.0 Platform:

DO NOT REPLY [Bug 24702] - Jar task update creates duplicate Class-Path

gzilla/show_bug.cgi?id=24702 Jar task update creates duplicate Class-Path [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PRO

Re: task update

Peter reilly wrote: On Fri, 2003-11-28 at 11:54, Christopher Lenz wrote: Peter reilly wrote: The rule is as is in the ant namespace documentation, opps the to be written documentation, is that if the element name is in ant's xmlns, then the componentname of the element is the local name, otherwise

Re: task update

On Fri, 2003-11-28 at 11:54, Christopher Lenz wrote: > Peter reilly wrote: > > The rule is as is in the ant namespace documentation, opps > > the to be written documentation, is that > > if the element name is in ant's xmlns, then > > the componentname of the element is the local name, > > otherwis

Re: task update

Peter reilly wrote: The rule is as is in the ant namespace documentation, opps the to be written documentation, is that if the element name is in ant's xmlns, then the componentname of the element is the local name, otherwise it is uri:localname. This is to be backward compatible with previous vers

Re: task update

On Friday, November 28, 2003, at 04:13 AM, Steve Loughran wrote: Stefan Bodewig wrote: On Thu, 27 Nov 2003, Peter reilly <[EMAIL PROTECTED]> wrote: This is to be backward compatible with previous versions of ant. Actually, my mail is a success mail 8-) we could do a really cool task with this XML

Re: task update

Stefan Bodewig wrote: On Thu, 27 Nov 2003, Peter reilly <[EMAIL PROTECTED]> wrote: This is to be backward compatible with previous versions of ant. Actually, my mail is a success mail 8-) we could do a really cool task with this XMLFragment thingy, or add an task that is more RESTy -

Re: task update

On Thu, 27 Nov 2003, Peter reilly <[EMAIL PROTECTED]> wrote: > This is to be backward compatible with previous > versions of ant. Actually, my mail is a success mail 8-) Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For ad

Re: task update

The rule is as is in the ant namespace documentation, opps the to be written documentation, is that if the element name is in ant's xmlns, then the componentname of the element is the local name, otherwise it is uri:localname. This is to be backward compatible with previous versions of ant. On Th

Re: task update

On 25 Nov 2003, Stefan Bodewig <[EMAIL PROTECTED]> wrote: > this is from running nant.xml with Mono 0.28 and NAnt (CVS version) > in my PATH on Linux: and now: leads to [EMAIL PROTECTED] dotnet]$ ant -f /tmp/nant.xml Buildfile: /tmp/nant.xml [nant] NAnt version 0

task update

Hi, just to give you an idea, this is from running nant.xml with Mono 0.28 and NAnt (CVS version) in my PATH on Linux: [EMAIL PROTECTED] dotnet]$ ant -f src/etc/testcases/nant.xml Buildfile: src/etc/testcases/nant.xml echo: [nant] NAnt version 0.8.4 Copyright (C) 2001-2003 Gerry Shaw

DO NOT REPLY [Bug 24702] - Jar task update creates duplicate Class-Path

gzilla/show_bug.cgi?id=24702 Jar task update creates duplicate Class-Path [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PRO

DO NOT REPLY [Bug 24702] - Jar task update creates duplicate Class-Path

gzilla/show_bug.cgi?id=24702 Jar task update creates duplicate Class-Path [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Reso

DO NOT REPLY [Bug 24702] New: - Jar task update creates duplicate Class-Path

gzilla/show_bug.cgi?id=24702 Jar task update creates duplicate Class-Path Summary: Jar task update creates duplicate Class-Path Product: Ant Version: 1.5.4 Platform: All OS/Version: Linux Status: NEW Severity: Major Pr