[ http://issues.apache.org/struts/browse/SHALE-324?page=comments#action_38561 ] Craig McClanahan commented on SHALE-324: ----------------------------------------
> I'm not sure how we should best pull this into Shale. It has dependencies > with the > maven plugin api. What do you think Wendy, Craig, James? For the utility itself, it's just a standalone JAR file with a main class, right? It seems to me we should establish a "tools" top level directory (parallel to framework and maven), and put the utility project there. There's quite a few things we can do with command line tools like this (Rahul's converter for dialog configuration files comes to mind, as do ideas about a tool that audits all the config files in a project). The mojo and its associated test would seem to belong in the "maven" top level directory, where we can release them separately. I also like the design practice of supplying command line tools as a standalone executable, plus a Maven mojo. > Maven Mojo to convert JSF type library descriptors to clay configuration files > ------------------------------------------------------------------------------ > > Key: SHALE-324 > URL: http://issues.apache.org/struts/browse/SHALE-324 > Project: Shale > Issue Type: New Feature > Components: Clay > Affects Versions: 1.0.3 > Environment: Any > Reporter: Hermod Opstvedt > Attachments: Clay-tools.zip > > > I have created a Utility that will convert a JSF type library descriptor into > a corresponding Clay component configuration file. It can be ran standalone, > or as a Maven mojo thereby enabling the conversion to take place as part of > the Clay Maven build process. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
