Re: [jelly] moved werkz tags
From: Jason van Zyl [EMAIL PROTECTED] Hi, I moved the Werkz jelly tags of out of jelly proper and into the Werkz repository. I also changed a couple of others things like test resource copying and the project.xml file to update the version of Werkz being used. I just did a massive refactoring of Maven so the test build works for me and I've asked Dion to try the jelly build to try and find any problems before anyone else does. This sounds like a good idea. One problem this causes is that the Jeez tag library (terrible name, probably calling it the Maven tag library or Maven core tag library would be better) which is a combination of Werkz + Ant + a couple more tags). Its probably worth moving this Jeez tag library into either Werkz or Maven; the latter probably makes most sense then any other Maven specific tags could be put into this single tag library that is then bound to the default XML namespace. So how about we move this Jeez library into Maven? James --- http://radio.weblogs.com/0112098/ __ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [jelly] moved werkz tags
+1 -- dIon Gillard, Multitask Consulting Blog: http://www.freeroller.net/page/dion/Weblog Work: http://www.multitask.com.au James Strachan [EMAIL PROTECTED] wrote on 31/12/2002 10:36:26 PM: From: Jason van Zyl [EMAIL PROTECTED] Hi, I moved the Werkz jelly tags of out of jelly proper and into the Werkz repository. I also changed a couple of others things like test resource copying and the project.xml file to update the version of Werkz being used. I just did a massive refactoring of Maven so the test build works for me and I've asked Dion to try the jelly build to try and find any problems before anyone else does. This sounds like a good idea. One problem this causes is that the Jeez tag library (terrible name, probably calling it the Maven tag library or Maven core tag library would be better) which is a combination of Werkz + Ant + a couple more tags). Its probably worth moving this Jeez tag library into either Werkz or Maven; the latter probably makes most sense then any other Maven specific tags could be put into this single tag library that is then bound to the default XML namespace. So how about we move this Jeez library into Maven? James --- http://radio.weblogs.com/0112098/ __ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] ForwardSourceID:NT0009D7BA -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [jelly] moved werkz tags
On Tue, 2002-12-31 at 06:36, James Strachan wrote: From: Jason van Zyl [EMAIL PROTECTED] Hi, I moved the Werkz jelly tags of out of jelly proper and into the Werkz repository. I also changed a couple of others things like test resource copying and the project.xml file to update the version of Werkz being used. I just did a massive refactoring of Maven so the test build works for me and I've asked Dion to try the jelly build to try and find any problems before anyone else does. This sounds like a good idea. One problem this causes is that the Jeez tag library (terrible name, probably calling it the Maven tag library or Maven core tag library would be better) which is a combination of Werkz + Ant + a couple more tags). Its probably worth moving this Jeez tag library into either Werkz or Maven; the latter probably makes most sense then any other Maven specific tags could be put into this single tag library that is then bound to the default XML namespace. So how about we move this Jeez library into Maven? I have copies of them there which I'm now using. I just wasn't sure what you had planned vis-a-vis general ant usage. If it's cool with you I think moving them into Maven would make the most sense. I just didn't want to break your ant tests which seemed to use Jeez. I would also not be averse to moving the ant tag lib to maven either. I think I'm close to being able run build.xml files directly now and having all the tags in maven would probably help with this. James --- http://radio.weblogs.com/0112098/ __ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [jelly] moved werkz tags
From: Jason van Zyl [EMAIL PROTECTED] On Tue, 2002-12-31 at 06:36, James Strachan wrote: From: Jason van Zyl [EMAIL PROTECTED] Hi, I moved the Werkz jelly tags of out of jelly proper and into the Werkz repository. I also changed a couple of others things like test resource copying and the project.xml file to update the version of Werkz being used. I just did a massive refactoring of Maven so the test build works for me and I've asked Dion to try the jelly build to try and find any problems before anyone else does. This sounds like a good idea. One problem this causes is that the Jeez tag library (terrible name, probably calling it the Maven tag library or Maven core tag library would be better) which is a combination of Werkz + Ant + a couple more tags). Its probably worth moving this Jeez tag library into either Werkz or Maven; the latter probably makes most sense then any other Maven specific tags could be put into this single tag library that is then bound to the default XML namespace. So how about we move this Jeez library into Maven? I have copies of them there which I'm now using. I just wasn't sure what you had planned vis-a-vis general ant usage. If it's cool with you I think moving them into Maven would make the most sense. I just didn't want to break your ant tests which seemed to use Jeez. I've just fixed the test cases which were using Jeez instead of the Ant taglib. So now its only the Jeez test cases that use Jeez (I think). So its all ready to move to Maven. I would also not be averse to moving the ant tag lib to maven either. I think I'm close to being able run build.xml files directly now Way cool! and having all the tags in maven would probably help with this. I think I'd like to keep the Ant tag library inside the Jelly distro as its very useful to be able to use Ant tasks inside of Jelly. It also means Jelly based testing frameworks like Latka or Ant based frameworks that use Jelly like Anteater can make use of Ant tasks without being dependent on Maven. Who knows, maybe one day Ant itself could use Jelly to script its tasks too. James --- http://radio.weblogs.com/0112098/ __ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [jelly] moved werkz tags
On Tue, 2002-12-31 at 11:16, James Strachan wrote: I think I'd like to keep the Ant tag library inside the Jelly distro as its very useful to be able to use Ant tasks inside of Jelly. It also means Jelly based testing frameworks like Latka or Ant based frameworks that use Jelly like Anteater can make use of Ant tasks without being dependent on Maven. Who knows, maybe one day Ant itself could use Jelly to script its tasks too. Yes, it would be nice if all that great utility code was taken out of Ant and put in the commons and use a dynabean adapter to turn the utility bean into a task for use in Ant. I think that is the most fundametnal design error and drawback to Ant is that everything that is basically really just a bean is bound Task and the very problematic AntClassLoader. If the utility code was taken out of Ant I imagine you could get an compatible mechanism up and running in a couple months. That would be a huge unification and allow access to all the utility code in Ant which is very annoying to use outside of Ant currently. James --- http://radio.weblogs.com/0112098/ __ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
[jelly] moved werkz tags
Hi, I moved the Werkz jelly tags of out of jelly proper and into the Werkz repository. I also changed a couple of others things like test resource copying and the project.xml file to update the version of Werkz being used. I just did a massive refactoring of Maven so the test build works for me and I've asked Dion to try the jelly build to try and find any problems before anyone else does. -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
