Re: cvs commit: ant/src/testcases/org/apache/tools/ant/taskdefs/optional/junit JUnitReportTest.java
On Sat, 14 May 2005, Steve Loughran [EMAIL PROTECTED] wrote: we could use .toURL, which probably works better across platforms. Our own FileUtils version works even better than that. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] include FTP task revisions in 1.6.4 release
Steve Cohen wrote: Shall the newly added FTP task revisions be incorporated into release 1.6.4? I'm withdrawing this vote request. Although commons-net functions as expected, the relationship with the FTP task is a little more complicated than I'd thought, and those who have expressed fears are correct in doing so, in spite of any carping I might still want to do about remarks indicating that the remarkers considered this is an unwanted maintenance chore being thrust upon them rather than something motivated in the first place by bug reports and feature requests in Ant's own bug system. I had assumed that tying commons-net timezone functionality into the task's newer logic would be simpler than it has turned out to be. There are still a few wrinkles I need to work out. Since Steve Loughran is talking about a July release rather than the six months I'd heard bandied about earlier, I am less insistent on getting it in for 1.6.4. Steve Cohen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
FTP.isUpToDate()
In trying to bring over new commons-net timezone functionaility, I
discover the following:
protected boolean isUpToDate(FTPClient ftp, File localFile,
String remoteFile)
throws IOException, BuildException {
...
if (this.action == SEND_FILES) {
return remoteTimestamp + timeDiffMillis localTimestamp;
} else {
return localTimestamp remoteTimestamp + timeDiffMillis;
}
}
Off the top of my head, and given the general logic associated with the
name of the method, can anyone think of a reason why the two
greater-than signs in the above code should not be greater-than-or-equal?
In the test case I am developing from the new code, my first iteration
didn't produce the expected results. I expected one or two files to be
gotten, not the entire directory of 300 files. When I changed the 's
above to ='s, the code worked as expected. Can anyone see something
I'm missing?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 34924] New: - SummaryJUnitResultFormatter does not print the test case name
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=34924. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=34924 Summary: SummaryJUnitResultFormatter does not print the test case name Product: Ant Version: 1.6.3 Platform: Other OS/Version: other Status: NEW Severity: normal Priority: P2 Component: Optional Tasks AssignedTo: dev@ant.apache.org ReportedBy: [EMAIL PROTECTED] hi, in most of the projects that i have worked on using ant, the devs have felt that they need ant to only show the summary of test results. To achieve this, we use the 'formatter=plain' specification with summary turned on. But this just prints the summary without printing the actual test case name. It would be really helpful if this could be done by default - or at least turned on with some switch. thanks, Vijay -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] include FTP task revisions in 1.6.4 release
Steve Cohen wrote: Steve Loughran wrote: Steve Cohen wrote: Shall the newly added FTP task revisions be incorporated into release 1.6.4? Motivation: I understand this comes in under the wire and may cause justifiable trepidation among some. I still favor adding it to the release because: 1) The tasks add some important new capabilities (in order of importance): a) the ability for the newer attribute to recognize timezone differences between client and server b) the ability to handle the all-numeric timestamp format that some unixes (Debian for example) are now shipping with. c) the ability to handle legacy systems that still use locale-specific timestamp formatting (becoming rare but still encountered). Documentation of the new features has also been checked in. 2) Care has been taken to avoid adding new dependency requirements to Ant. The new features require commons-net-1.4.0 and the task cannot be compiled without it, but users with an earlier version of commons-net can still use the task exactly as before. Existing scripts will function exactly as before. 3) Just to reiterate - in spite of earlier postings the the contrary, including this in release 1.6.4 WOULD NOT REQUIRE USERS TO UPGRADE COMMONS-NET. This has been tested against commons-net-1.2.2 (the previous recommended system) and all tests passed. My vote: -1 I dont think I've -1'd anything before, at least not in recent memory. Here is my thinking (a) 1.6.4 is an emergency release to fix some defects that didnt show up during beta testing Fair enough. (b) any feature added now would go into the release without beta testing. It runs the risk of breaking. Fair enough, although it's worth repeating that existing tests that test existing functionality do not break, either with the old commons-net lib or the new. (c) We'd be effectively obliged to maintain the API forever. Its good to use something in a few of your own build files first to see what works, and what doesnt. What is there about this API compared to any others that Ant is obliged to maintain that you don't like? This objection is meaningless and insulting. These features have been extensively tested in commons-net. Sorry. I dont mean commons-net API changes. What I meant was any new attributes/methods added to ant tasks need to be preserved for eternity, so its good to get them right. Commons-net is under the jakarta umbrella with an active team of developers. Meanwhile Ant maintains APIs adapting it to various commercial products for which it has no serious maintainers. I myself maintained the starteam tasks for Ant for as long as I had a job that gave me access to a StarTeam server. (late 2003). Looking back through CVS at the entire starteam package I find one substantive change made in a year and a half (a NPE fix). There have been no enhancements, and nothing but boilerplate changes. Okay, there's probably not too much demand for those tasks and, at any rate, no one has stepped forward. But please don't put jakarta-commons-net into that bag. It wasnt intended to. ftp, telnet, rexec, are core, even though I think SSH is safer. FTP and telnet are far more common. If I sound a little resentful, it's because these changes were designed by me specifically with Ant in mind. I resisted suggestions from others that would have implemented these changes in fashions that were less compatible with Ant. Now this effort seems to be being treated as an unwanted intrusion. No, no no, I am grateful for the changes. We get a lot of grief about Ftp not handling different countries/tz/platforms, and the stuff in there is welcome. Its just I think that an immediate relase of them to end users, just because we are doing a no-beta-test-planned release next week is too premature. -steve - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] include FTP task revisions in 1.6.4 release
Steve Cohen wrote: Steve Cohen wrote: Shall the newly added FTP task revisions be incorporated into release 1.6.4? I'm withdrawing this vote request. Although commons-net functions as expected, the relationship with the FTP task is a little more complicated than I'd thought, and those who have expressed fears are correct in doing so, in spite of any carping I might still want to do about remarks indicating that the remarkers considered this is an unwanted maintenance chore being thrust upon them rather than something motivated in the first place by bug reports and feature requests in Ant's own bug system. I had assumed that tying commons-net timezone functionality into the task's newer logic would be simpler than it has turned out to be. There are still a few wrinkles I need to work out. I apologise if you felt I was carping; its not unwanted maintenance, its welcome change, and you have done some excellent work. I particularly like your trick of doing an in-package import to get the stuff, and am running against commmons-net 1.4.0 today (and using it and the new tasks as the basis for the updated section in the second edition of Erik and my ant book.). I dont have any issue with change. I just dont believe in premature releases of untested stuff. Since Steve Loughran is talking about a July release rather than the six months I'd heard bandied about earlier, I am less insistent on getting it in for 1.6.4. I'd estimate a summer release of 1.7beta, with a fairly unhurried program fielding requests and stabilising things. The Plan Of Record is in the Wiki, though without any dates. I am currently doing the slideware for the europe apachecon on the subject, and it would really help me if there was a release then, though with the deadline for slides being friday, I am going to have to avoid the subject of changes to import, and other major pending changes. I can talk about the new release of the maven2 repository tasks though :) -steve - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: ant/docs/manual/OptionalTasks scp.html
stevel 2005/05/15 14:13:06
Modified:docs/manual/OptionalTasks scp.html
Log:
scp doc tweakage.
Revision ChangesPath
1.19 +11 -4 ant/docs/manual/OptionalTasks/scp.html
Index: scp.html
===
RCS file: /home/cvs/ant/docs/manual/OptionalTasks/scp.html,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- scp.html 29 Apr 2005 18:58:09 - 1.18
+++ scp.html 15 May 2005 21:13:06 - 1.19
@@ -13,7 +13,7 @@
pemsince Ant 1.6/em/p
-pCopies a file or FileSet to or from a remote machine running SSH daemon.
+pCopies a file or FileSet to or from a (remote) machine running an SSH
daemon.
FileSet ionly/i works for copying files from the local machine to a
remote machine./p
@@ -210,15 +210,22 @@
pstrongSecurity Note:/strong Hard coding passwords and/or usernames
in scp task can be a serious security hole. Consider using variable
-substitution and include the password on the command line. For example:br
+substitution and include the password on the command line. For example:
+p
pre
lt;scp todir=quot;${username}:[EMAIL PROTECTED]:/dirquot; ...gt;
/pre
-Invoke ant with the following command line:
+Invoking ant with the following command line:
pre
ant -Dusername=me -Dpassword=mypassword target1 target2
/pre
-/p
+
+Is slightly better, but the username/password is exposed to all users on an
Unix
+system (via the ps command). The best approach is to use the
+codelt;inputgt;/code task and/or retrieve the password from a (secured)
+.properties file.
+
+p
pstrongUnix Note:/strong File permissions are not retained when files
are copied; they end up with the default codeUMASK/code permissions
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Online Bookstore
I think it's safe to say that users of ASF software buy their share of computer books. The online retailers, like Amazon.com, offer commission programs for people who link to their site. The Apache Software Foundation is a not-for-profit corporation funded solely through donations from the community. To help offset the costs of ASF infrastructure, we could make it possible for ASF supporters to buy books about ASF project software through commission-program links. The commissions for such links is usually 5% or more. Given the vast number of books ASF supporters purchase, the commissions from these sales could become a respectable source of revenue. Setting up an online bookstore to benefit the ASF has been a longstanding itch of mine, which I've finally gotten a chance to scratch. A prototype bookstore is now available as a Confluence wiki. You can check it out at: * http://opensource.atlassian.com/confluence/oss/display/BOOKS/Home If anyone is interested in helping out with maintaining the site, please let me know. I'd especially welcome ASF project committers who'd like to help oversee the section about their project. If there was interest, we could also add pages for books recommended by ASF committers. Here, we could list other related books and off-topic items, like DVDs and CDs that we enjoy. There's an unfinished prototype of a committer page here: * http://opensource.atlassian.com/confluence/oss/display/BOOKS/husted If anyone would like to make any existing links commission-program links, there are instructions for how to do that on the bookstore Feedback page. * http://opensource.atlassian.com/confluence/oss/display/BOOKS/Feedback There is also a general FAQ on the Feedback page. Of course, this is a 100% volunteer effort and 100% of all commissions are donated directly to the Apache Software Foundation. Comments and suggestions are welcome. I'm sending this message to dev@ for each Project with a category in the online bookstore. After getting feedback from the dev lists, a broader announcement would be made. -Ted. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Online Bookstore
On 5/15/05, Ted Husted [EMAIL PROTECTED] wrote: I'm sending this message to dev@ for each Project with a category in the online bookstore. This should have read: I'm sending this message to fundraising@ and the dev@ for each Project with a category in the online bookstore. Sorry for the churn. -Ted. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
