[ http://jira.codehaus.org/browse/MASSEMBLY-56?page=comments#action_57190 ]
John Didion commented on MASSEMBLY-56: -------------------------------------- I'll give you our use case: we have several "tool" components, basically command-line tools for admin tasks. I've written a plugin to generate batch files to execute these admin tools. We've decided the best way to use this is to create a directory assembly in the target directory and place the generated batch files there. Devs can then either use the exec plugin to run these batch files, or just run them directly. So, as you see, an attached version of the directory assembly plugin is the only thing that works for us. Maybe it would make more sense to make "directory" one of the output formats for the assembly/attached plugins rather than have seperate directory and attached-directory plugins. > Refactor DirectoryMojo so it can be run either stand-alone or attached > ---------------------------------------------------------------------- > > Key: MASSEMBLY-56 > URL: http://jira.codehaus.org/browse/MASSEMBLY-56 > Project: Maven 2.x Assembly Plugin > Type: Improvement > Versions: 2.1 > Reporter: John Didion > Fix For: 2.1 > Attachments: MASSEMBLY-56.patch > > > Pretty straight-forward. Just make the directory goal into two goals (like > assembly and attached), one that can be run stand-alone and one that can be > run attached to a lifecycle phase. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
