[ http://jira.codehaus.org/browse/MNG-483?page=comments#action_44199 ]
John Casey commented on MNG-483: -------------------------------- I'm not sure I have enough background on this issue to keep up. 1. How would you activate a profile that introduces the attachment in the case of the release plugin? 2. What do you mean by disabling the source binding once enabled, and in the case of enabling it by default are you talking about some sort of POM addition or something? What's the issue here, exactly? 3. What SNAPSHOT check are you referring to? Determining whether to attach the source artifact based on snapshot vs. not? 4. I like the cliOnly annotation idea, and I think it may have more general applicability. > 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]
