[
https://issues.apache.org/jira/browse/CLK-347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12887412#action_12887412
]
Md. Jahid Shohel commented on CLK-347:
--------------------------------------
>I also think we need to differentiate between modules and the way to manage a
>big project. One can certainly >break a big app into smaller modules (Eclipse
>subprojects), but they are still part of the same application and >are tested
>as a whole. However creating stand-alone application modules which are dropped
>into a main >application is not a simple task.
So, should we finalize the definition of modularity that we are talking here?
Like jar level modularity (where the dependency is only on jar, but there will
be no source code copy), or just a separate package, which can be copied over
and over on different projects? For the 2nd case, we should not use the word
"modularity" though.
> Module support
> --------------
>
> Key: CLK-347
> URL: https://issues.apache.org/jira/browse/CLK-347
> Project: Click
> Issue Type: Improvement
> Components: core
> Reporter: Bob Schellink
>
> Add module support to Click core. Some code has been committed here:
> http://click.svn.sourceforge.net/viewvc/click/trunk/sandbox/sabob/plugin/
> Note that with the recent work done on CLK-343 the module code wont compile
> anymore.
> A related issue is: CLK-328
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
