tag:blogger.com,1999:blog-4110180.post109121124878555599..comments2023-06-20T05:31:24.545-07:00Comments on Tapestry Central: Ant best practice: One Compile, One Directory, One JARAnonymoushttp://www.blogger.com/profile/04486596490758986709noreply@blogger.comBlogger6125tag:blogger.com,1999:blog-4110180.post-1146507233696671062006-05-01T11:13:00.000-07:002006-05-01T11:13:00.000-07:00you really believe your article is clear, to the p...you really believe your article is clear, to the point and obvious. the fact that I missed the point (in your opinion, in mine the article is just cheap guru-posing) and the other 2 commentators (luke and russell) disagree on what you actually tried to say doesn't convince you it's something wrong with your writing... <BR/>but hey, I seem to be the only one ... <BR/>:-)))))))<BR/><BR/>just a suggestion: when you try to say "multiple compiles from multiple source trees to multiple jars", don't name your article "one compile, one directory, one jar". gives the wrong impression...<BR/><BR/>I just saw this blog is from 2004, if somebody didn't really try to convince me to put all the classes in one jar (giving your article as reference) I wouldn't write anything here (waste of time)Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-4110180.post-1146496110558966622006-05-01T08:08:00.000-07:002006-05-01T08:08:00.000-07:00Yes, Ranjix. Every single other person appears to ...Yes, Ranjix. Every single other person appears to have realized that the point: generate multple JARs, have one source tree per JAR. You are the only one who seems to have leaped to the conclusion that I would suggest building a single JAR for your entire application.Anonymoushttps://www.blogger.com/profile/04486596490758986709noreply@blogger.comtag:blogger.com,1999:blog-4110180.post-1146494938619781562006-05-01T07:48:00.000-07:002006-05-01T07:48:00.000-07:00heh. I missed the point? let's quote from the arti...heh. I missed the point? let's quote from the article. <BR/><BR/>"Do yourself a favor. When you are laying out your source tree, follow this rule: One Compile, One Directory, One JAR."<BR/><BR/>since everybody is working on an j2ee app, basically your "point" seems to be to have all the classes (for the app, mind you) in a single jar. that IS the point of your writing, as you so generously bolded it so one is sure he'll never forget. if this is NOT actually the point you're trying to make then you might want to re-write your point, this time paying attention to what you say. <BR/><BR/>howard, the article is weird and confusing and might give to some weaklings the wrong message (read the previous comments to see confused people, luke cracks me up "I agree wholeheartedly -- I think"). For myself I know I'm not going to put one app in one jar, even if gosling declares it the "pattern of the year". but I'm afraid some dudes will. <BR/><BR/>btw. in normal j2ee containers, usually there is ONE CLASSLOADER per EAR. so as long you have only one EAR (application), then you shouldn't run into problems with the classloader.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-4110180.post-1146284608500999202006-04-28T21:23:00.000-07:002006-04-28T21:23:00.000-07:00Ranjix --- you totally missed the point. I like to...Ranjix --- you totally missed the point. I like to build proper layers of code in properly modular jars. I just organize things in such a way that the build process doesn't become a gnarly monster. But that's ok ... we won't miss you in happy Tapestry / HiveMind land!Anonymoushttps://www.blogger.com/profile/04486596490758986709noreply@blogger.comtag:blogger.com,1999:blog-4110180.post-1146261479546179512006-04-28T14:57:00.000-07:002006-04-28T14:57:00.000-07:00and, coming soon, from the same author, "building ...and, coming soon, from the same author, "building one big EXE file instead of EXE and DLLs", respectively, "molding a car from a single piece of metal, including wheels - case in discussion Kia Sonata". <BR/><BR/>dude, you convinced me never to try tapestry or hivemind. <BR/><BR/>btw, ddj runs the opposite story: http://www.ddj.com/dept/java/185300006?cid=RSSfeed_DDJ_JavaAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-4110180.post-1091460173316236822004-08-02T08:22:00.000-07:002004-08-02T08:22:00.000-07:00I agree wholeheartedly -- I think. I had to rerea...I agree wholeheartedly -- I think. I had to reread a few times to be sure you were saying what I thought you were saying. When you say "Why is this dangerous?" you should clarify that what is dangerous is the notion of adding other directories' classes or source directories to this directory's build classpath. This is not clear in the original post because the dangerous part is a parenthetical comment.Luke Blanshardhttps://www.blogger.com/profile/17192829091365588327noreply@blogger.com