Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@apache.org Received: (qmail 50691 invoked from network); 17 May 2002 04:54:25 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 17 May 2002 04:54:25 -0000 Received: (qmail 15772 invoked by uid 97); 17 May 2002 04:54:31 -0000 Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org Received: (qmail 15728 invoked by uid 97); 17 May 2002 04:54:30 -0000 Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 15717 invoked by uid 50); 17 May 2002 04:54:30 -0000 Date: 17 May 2002 04:54:30 -0000 Message-ID: <20020517045430.15716.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: ant-dev@jakarta.apache.org Cc: Subject: DO NOT REPLY [Bug 9190] - Task.setTaskType should be protected or public X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N 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://nagoya.apache.org/bugzilla/show_bug.cgi?id=9190 Task.setTaskType should be protected or public ------- Additional Comments From memmel2@yahoo.com 2002-05-17 04:54 ------- Setting it to a default in Task should be the "right" thing. If you don't expose it it should be set to a real value. Basically Task should intialialize as UnknownElement in its constrcutor. I'm not sure you really need UnknownElement I think it can be eliminated. Theres no reason I think for Task to be abstract instead it can be combined with UnkownElment to create a concrete class. Okay you asked I guess I need to admit what I'm using Ant for. First its not what it was designed for but I've written a completley new AWT implementation thats full screen and has all kinds of cool features it will be released I hope early next week. Features RDF (Resource Description Framework) built in meta repository. AWT implemented on top of Swing Basic changes which open up the possibility to unify Swing/AWT apis. Fairly robust Multi Application Support almost the best you can do with out fundamental changes to the JVM implementation. The ability to lauch a full desktop interface of the Network. etc etc. I recently moved the Java build process over to Ant and as I did it I realized the core design for Ant was almost exactly what I want my xml based application launcher to do. I wrote a task for gcc its a hack but I did add the abilitly to generate the javah headers on the fly by greping the C source file for jni like headers which I find very useful for jni code. Thats something I would not want to do using make but it was very easy using ant. If you guys want it tell me where to send it. A real "generic" C compiler task is a lot of work but maybe this could be useful as input if someones writing one. As I worked with ant I realized the ant task model really fits a lot of other problems and I feel the core of ant can be abstracted to provide a generic task management system. I was able to replace my launcher with ant very easily. The ant core really only needs a bit of work to provide a very cool api whenever someone wants to use the task/xml concept which ant implements. In my case I want to use ant task to intilize the JavaOS launch Apps and even provide a Cron/At task all this can be done using ants core with very few changes. And you can see why I will be making strange bug reports : ) -- To unsubscribe, e-mail: For additional commands, e-mail: