Ravindar Reddy schrieb: > It would be good to split a monolithic jar into smaller jars with clear > dependencies. This makes it easy for developers to choose the functionality > based on the needs . > > I could think of the breakdown like: > > - a jar for dojo > - a jar with shared utility code > - a jar with all validators > - a jar with all converters > - a jar with components and renderers only > - a jar with taglib codefor JSF components. (e.g: somebody instantiating JSF > components dynamically do not need this) > > just my 2 cents, thanks > -Ravi R >
please dont, that is overkill, a commons jar ought to be enough upon which component libs can build... there should not be references from the commons back into the core.
