[ http://jira.codehaus.org/browse/MNG-483?page=comments#action_44078 ]
Brett Porter commented on MNG-483: ---------------------------------- 1) Jason Grant is looking at implementing the attaching of artifacts during assembly:assembly which is a part of this 2) on my "tricky bit" comment above, this can probably be resolved by having that be @execute phase="package" cliOnly="true" (where cliOnly is a new construct indicating the goal had to be called explicitly to trigger it, instead of during the lifecycle for package). This hearkens back to "reverse lookup of the lifecycle for a goal", so should review that issue first to see whether there are other reasons to beware of here. > sort out artifact attachment > ---------------------------- > > Key: MNG-483 > URL: http://jira.codehaus.org/browse/MNG-483 > Project: Maven 2 > Type: Bug > Reporter: Brett Porter > Assignee: John Casey > Priority: Blocker > Fix For: 2.0-beta-1 > > > currently, there is an attachArtifact call inside the plugin building the > attachment. It imposes a m-a and m-p dependency, as well as an > artifactFactory requirement to be able to construct the artifact to attach. > sort out > - if there is an easier way to achieve this > - how to retain the default source binding, but also how to turn it off > - how to make the source binding happen only on "release" (bear in mind > people may not be using the release plugin... a profile was the original idea) > - how to bind assembly similarly -- 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]
