[ http://jira.codehaus.org/browse/MASSEMBLY-56?page=comments#action_61009 ]
John Casey commented on MASSEMBLY-56: ------------------------------------- Ok, I just verified that binding assembly:directory to the 'package' phase will indeed cause a forked lifecycle. This means we *do* need another mojo that performs the same tasks as :directory, but which will execute within the confines of the current lifecycle, rather than forking a new one. I'd probably be in favor of naming it something like "directory-inline" or something, to denote that it's meant to operate inline within a lifecycle. > 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
