[jira] Commented: (MNG-483) sort out artifact attachment

[ http://jira.codehaus.org/browse/MNG-483?page=comments#action_44522 ] Jason Grant commented on MNG-483: - Would you like me to check my enhancements in to svn? I notice that Daniel Krisher has patched the assembly plugin off the trunk, over in #MNG-735.

[jira] Updated: (MNG-483) sort out artifact attachment

[ http://jira.codehaus.org/browse/MNG-483?page=all ] Jason Grant updated MNG-483: Attachment: assembly-050814-1.zip I've made the change described in my comment above. Hope it finds its way into svn soon. Note that this attachment builds on the

[jira] Commented: (MNG-723) [patch] assembly:unpack

[ http://jira.codehaus.org/browse/MNG-723?page=comments#action_44425 ] Jason Grant commented on MNG-723: - The code attached to this issue has now been enhanced with extra functionality as described in #MNG-483. I've attached a new zip to that issue; it now

[jira] Commented: (MNG-483) sort out artifact attachment

[ http://jira.codehaus.org/browse/MNG-483?page=comments#action_44464 ] Jason Grant commented on MNG-483: - Re (4): My patch does *not* cater for the cliOnly idea; it simply attaches all assemblies as project artifacts as described in #action_44289 above.

[jira] Updated: (MNG-723) [patch] assembly:unpack

[ http://jira.codehaus.org/browse/MNG-723?page=all ] Jason Grant updated MNG-723: Attachment: UnpackMojo.java The first attachment still had System.out debug statements. This one doesnt. [patch] assembly:unpack --- Key:

[jira] Commented: (MNG-723) [patch] assembly:unpack

[ http://jira.codehaus.org/browse/MNG-723?page=comments#action_44305 ] Jason Grant commented on MNG-723: - I want to do a further update - AssemblyMojo has been wired so far to assume that dependencies are jars - if unpack is required, then it tries to unjar

[jira] Updated: (MNG-723) [patch] assembly:unpack

[ http://jira.codehaus.org/browse/MNG-723?page=all ] Jason Grant updated MNG-723: Attachment: assembly-050811-1.zip Oh what the heck - did the changes described above and am attaching the code, since doing otherwise will just hold things up. This time,

[jira] Commented: (MNG-709) lifecycle can end up in an infinite loop

[ http://jira.codehaus.org/browse/MNG-709?page=comments#action_44343 ] Jason Grant commented on MNG-709: - Yes, you're right; depending on a separate dedicated project is the way to go. For some reason, I had it in my head that maven would sweep each phase

[jira] Created: (MNG-723) [patch] assembly:unpack

[patch] assembly:unpack --- Key: MNG-723 URL: http://jira.codehaus.org/browse/MNG-723 Project: Maven 2 Type: New Feature Components: maven-plugins Versions: 2.0-beta-1 Reporter: Jason Grant Priority: Minor Fix For:

[jira] Commented: (MNG-483) sort out artifact attachment

[ http://jira.codehaus.org/browse/MNG-483?page=comments#action_44289 ] Jason Grant commented on MNG-483: - A bit of background with regard to Brett's mention of me looking at the attachment of artifacts, above. I've been using assembly to produce zip files,

[jira] Commented: (MNG-709) lifecycle can end up in an infinite loop

[ http://jira.codehaus.org/browse/MNG-709?page=comments#action_44293 ] Jason Grant commented on MNG-709: - Would that approach allow me to specify, say, phasegenerate-sources/phase if I wanted to create some zips for inclusion into tests, etc.? WRT your

[jira] Created: (MNG-709) AssemblyMojo.execute() no longer gets invoked from pom

AssemblyMojo.execute() no longer gets invoked from pom -- Key: MNG-709 URL: http://jira.codehaus.org/browse/MNG-709 Project: Maven 2 Type: Bug Components: maven-plugins Versions: 2.0-beta-1