[
https://issues.apache.org/jira/browse/CLK-531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12840631#action_12840631
]
Joseph Schmidt commented on CLK-531:
------------------------------------
> it would allow to be used by several IDEs directly(from a plug-in or from
> external tools)
But is it worth spending the effort to make it a library? Would the IDEs (
ClickIDE and NBX) use it instead of their actual code?
There are a few standalone tools that do something similar (but for Tapestry
and Struts):
http://jag.sourceforge.net/
> Quick Start Project Builder improvements
> ----------------------------------------
>
> Key: CLK-531
> URL: https://issues.apache.org/jira/browse/CLK-531
> Project: Click
> Issue Type: New Feature
> Reporter: Adrian A.
> Assignee: Adrian A.
>
> To make Click even more useful for new users, Quick Start needs to be better.
> Some improvements that could help make it much better:
> 1. move form an ANT based implementation to a standalone library (and maybe +
> CLI).
> 2. allow more options for project setup:
> - inclusion of libraries: cayenne, spring, hibernate, external click
> controls, etc.
> - security type: container, Click, Acegi, and maybe GAE/J etc .
> 3. generation of unit tests and selenium tests (+configuration)
> #1 would bring several advantages:
> - it would allow to be used by several IDEs directly(from a plug-in or
> from external tools)
> - the effort would not be duplicated and a best practice structure used
> everywhere.
> - if included in the path it could create a click project everywhere
> from the command line - not just in the click directory (this looks very nice
> in live presentations).
>
> #2 would reduce the time to setup a project considerably, since a simple
> Click application without persistence is quite seldom.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
