After subscribing to the mailing list (dev-subscribe@ant.apache.org) several messages had the following at the bottom of the emails.
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
I went back to http://ant.apache.org , clicked on mailing lists to see more information about the dev-help option. I saw this:
"To subscribe to a mailinglist use the links below. In your first email you will get some information about working with the list manager EZMLM."
EZMLM had a link, but it did not seem to be much help. It talked about how the email bot worked in general, but not specifically for the Ant project.
Seemed like an interesting idea to use their email bot to get information about the mailing list.
The response was pretty quick (a few minutes) and in summary, this is what I got:
"This is a generic help message. The message I received wasn't sent to any of my command addresses."
There was the unsubscribe email address from above, and a subscribe email address.
There was also one for information and one for FAQ:
dev-info@ant.apache.org
dev-faq@ant.apache.org
There were also instructions for subscribing to and unsubscribing from a digest version.
Also interesting were "commands" to get groups of messages from the archive by "message number".
To get messages 123 through 145 (a maximum of 100 per request), mail:
dev-get.123_145@ant.apache.org
To get an index with subject and author for messages 123-456 , mail:
dev-index.123_456@ant.apache.org
They are always returned as sets of 100, max 2000 per request, so you'll actually get 100-499.
To receive all messages with the same subject as message 12345, send a short message to:
dev-thread.12345@ant.apache.org
The messages should contain one line or word of text to avoid being treated as sp@m, but I will ignore their content. Only the ADDRESS you send to is important.
An email to dev-info returned the same general message but with the following :
No information has been provided for this list.
An email to dev-faq returned the same general message but with the following:
FAQ - Frequently asked questions of the dev@ant.apache.org.
None available yet.
Saturday, May 15, 2010
Tuesday, May 11, 2010
Using Eclipse debugger in Ant project
I was really hoping I could run the Ant code locally in Eclipse through the debugger. I think I am close, I think the main driving class is Launcher, but I am not sure how to set it up properly to run it.
ACM 24x7 Ant Book
On ACM, I found one Ant book in their 24x7 books:
http://acm.books24x7.com/viewer.asp?bookid=3166&chunkid=0506148908
The title of the book is
http://acm.books24x7.com/viewer.asp?bookid=3166&chunkid=0506148908
The title of the book is
| Java Tools for Extreme Programming—Mastering Open Source Tools Including Ant, JUnit, and Cactus |
Replace Task
I was hoping to understand the replace task so I can tackle "15149 dealing with the replace task"
I think I'm going to have to mock up some sample data. The override concept is an interesting one. There are a list of files with tokens in them representing other values. This is kinda like mail merge. The replace task can take a properties file (a list of entries like name=value) and replace the tokens which match name with the corresponding value. For 15149, the submitter suggested that there could be a large master file of properties, the user could reference, but also use a smaller file to override a small subset of entries with custom entries. I could see this two ways. The first method would be to have a master file and an override file. The other method would be to allow the user to set up a hierarchy of property files. I have a similar issue at work and a hierarchical structure would work nicely.
I think I'm going to have to mock up some sample data. The override concept is an interesting one. There are a list of files with tokens in them representing other values. This is kinda like mail merge. The replace task can take a properties file (a list of entries like name=value) and replace the tokens which match name with the corresponding value. For 15149, the submitter suggested that there could be a large master file of properties, the user could reference, but also use a smaller file to override a small subset of entries with custom entries. I could see this two ways. The first method would be to have a master file and an override file. The other method would be to allow the user to set up a hierarchy of property files. I have a similar issue at work and a hierarchical structure would work nicely.
Wednesday, May 5, 2010
Ant 1.8.1
It looks like Ant 1.8.1 was released today. I took an update from subversion and found changes indicating the 1.8.1 version update.
I built it from the code again and set up Eclipse to use this version rather than the version built into Eclipse for builds.
I played around with it a while working on a build script for some sample CS550 code. Created an execute task for bison, another for flex, and one for cc. It seemed to work as well as a makefile. I tried it with my default version of ant (1.6.5) and the compiled 1.8.1 version.
I built it from the code again and set up Eclipse to use this version rather than the version built into Eclipse for builds.
I played around with it a while working on a build script for some sample CS550 code. Created an execute task for bison, another for flex, and one for cc. It seemed to work as well as a makefile. I tried it with my default version of ant (1.6.5) and the compiled 1.8.1 version.
Bug submission process
I found some information regarding how to submit a bug fix:
http://ant.apache.org/manual/tutorial-tasks-filesets-properties.html#contribute
Navigation to this was not easy
Main site http://ant.apache.org/
Click on "Manual" under "Documentation"
Click on "Developing with Ant"
Click on Tasks using Properties, Filesets & Paths
Click on Contribute the new task
This seems to coincide with the comments I saw on some of the bugs in bugzilla. The submitter puts a "delta" file directly into the bug rather than checking the change into subversion. Seems pretty awkward. If someone else makes a change to an overlapping portion of the code before the submitter's fix is applied, then whoever accepts the bug would have a difficult merge on their hands.
http://ant.apache.org/manual/tutorial-tasks-filesets-properties.html#contribute
Navigation to this was not easy
Main site http://ant.apache.org/
Click on "Manual" under "Documentation"
Click on "Developing with Ant"
Click on Tasks using Properties, Filesets & Paths
Click on Contribute the new task
This seems to coincide with the comments I saw on some of the bugs in bugzilla. The submitter puts a "delta" file directly into the bug rather than checking the change into subversion. Seems pretty awkward. If someone else makes a change to an overlapping portion of the code before the submitter's fix is applied, then whoever accepts the bug would have a difficult merge on their hands.
Saturday, May 1, 2010
Ant Candidate voting
It never occurred to me that an open source project would post a vote for a release candidate. One Ant member created a place to vote on version 1.8.1.
Subscribe to:
Posts (Atom)
