[jira] Commented: (MASSEMBLY-56) Refactor DirectoryMojo so it can be run either stand-alone or attached
[ http://jira.codehaus.org/browse/MASSEMBLY-56?page=comments#action_60175 ] Allan Ramirez commented on MASSEMBLY-56: Does somebody already came up with a good name for this? ;) 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]
[jira] Commented: (MASSEMBLY-56) Refactor DirectoryMojo so it can be run either stand-alone or attached
[ 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]
[jira] Commented: (MASSEMBLY-56) Refactor DirectoryMojo so it can be run either stand-alone or attached
[ http://jira.codehaus.org/browse/MASSEMBLY-56?page=comments#action_56943 ] Dan Tran commented on MASSEMBLY-56: --- here is some discussion in IRC dantran brett, i would like to help committing an assembly patch, but having trouble coming up with a name ;-) comments? http://jira.codehaus.org/browse/MASSEMBLY-56 * henry has joined #maven brett dantran: no idea brett not attached brett directory-only ? dantran hheeh, you have the same problem eh?.. i hate naming noisygreg not sure what the context is, but detached might help if you talk about sthg not attached ^^ dantran standlone? dantran they are all confusing brett the current :directory is the standalone one brett detached is not right either * hen has joined #maven * adc|mbl has quit IRC (Leaving) dantran now i am not sure why we need this feature, surely we dont want to bind it to a phase, we want to run it as a standlone as well brett dantran: what was the original use case? dantran I think it tries to solve infinite looping in assembly:directory where packing=pom brett but that bug was fixed anyway brett I think? dantran dont think so, it still there, ppl use assembly:attached instead dantran that is why we dont hear any more screaming ;-) dantran http://jira.codehaus.org/browse/MASSEMBLY-37 brett k I now understand how this JIRA is for If you bind assembly:attached to a package phase and run mvn assembly:directory, it will loop The work around is to run maven package to then unzip the output manually Untill we can come up with a good name, introduce this patch may create more confusion ;-) 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]
[jira] Commented: (MASSEMBLY-56) Refactor DirectoryMojo so it can be run either stand-alone or attached
[ http://jira.codehaus.org/browse/MASSEMBLY-56?page=comments#action_56635 ] Gilles Scokart commented on MASSEMBLY-56: - Do not hesitate to change the name. I don't like this name neither. But I didn't find a good one. 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]
[jira] Commented: (MASSEMBLY-56) Refactor DirectoryMojo so it can be run either stand-alone or attached
[ http://jira.codehaus.org/browse/MASSEMBLY-56?page=comments#action_56629 ] Dan Tran commented on MASSEMBLY-56: --- The patch looks good, but I am not certain about the name thou. attached-directory indicates what user can deploy/ install directory type archiver. However the mojo never attach it to the project, which is correct. isn't it confusing? Need to queury the core developers for suggestion 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]
