On 06 Sep 2007 18:24:44 +0200 (CEST), Robo <[EMAIL PROTECTED]> wrote: > Sorry Eelco but me and also quite a lot of other developers(I know, contrary > to others developers) consider same b.s. libraries which are \"alive\" just > because they are in classpath. It is like talking when nobody asks you ... > Look at Java SDK do you need all packages to build console \"Hello World!\" > No. And who cares. They are just there and do their stuff when needed. So why > wicket-velocity is doing job developer do not want and did not asked to. > Where is writen that I cannot put mindesly tens of useles libs when they just > sit there, assuming of course the packages are not duplicating. Do you > understand why there are packages Eelco. Unles the class is uniqeu develioper > should not be afreaid of using other class he wanted. To push your false > premise to edge, why you deliberatly put all packages and classes into jar > when you need just few of them also with dependencies. Isn`t it b.s.? Yes it > is .. and also it is not conceptual ... Do not make zombie libraries and > there wi ll > be no problem with dependecies. Got the point? If not I`m not alble not > help you sorry ...
Yeah, it's not that I don't get your point, it's just that I don't agree. What I'm saying is that you don't live in that perfect world and not all software acts like you seem to expect. There is no rule that you can't what we do, and Java makes it possible. AND many other frameworks do this kind of initialization as well, so you can have the same problem in many other occasions. Not to mention problems with versioning and shared server libs you might have (especially with older app server versions) if you just include every jar you come across. Anyway, to my knowledge, wicket-velocity is the only project that initializes pulling in more dependencies. And as you're not using that, we can end this discussion now. Eelco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
