|
From: Juergen H. <ju...@in...> - 2005-04-13 12:42:05
|
Both approaches have advantages. If the overall size is rather small, I would lean towards a single springmodules.jar. If it starts getting bigger, offer both a full springmodules.jar and some finer-grained jar files (but not necessarily one for each piece of code, rather one for each high-level package). This is essentially what we're doing in core Spring too. The other question is how to organize the springmodules source tree. As I've already argued, jar file separation does not have to match source tree separation. A single source tree can be used to generate multiple jar files, just like we currently do for core Spring. Juergen -----Original Message----- From: spr...@li... [mailto:spr...@li...]On Behalf Of Dmitriy Kopylenko Sent: Wednesday, April 13, 2005 2:29 PM To: spr...@li... Subject: Re: [Springframework-developer] Where does webflow live? Thomas Risberg wrote: > Rob, > > So what is the plan for the springmodules - is this going to be one > monolithic collection of modules or do you plan to split it up into > specific subprojects? I have a couple of small modules that could > live there but I'm not sure of how to coordinate adding them and > creating a distributable jar file. Do you see each module as an > independent piece that will have its own jar file or do you envision a > single springmodules.jar? > I guess that springmodules.jar would be too coarse grained. I would lean towards a separate jar per module. What do others think? Dmitriy. ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |