[ http://jira.codehaus.org/browse/MNG-483?page=comments#action_44457 ]
Brett Porter commented on MNG-483: ---------------------------------- reponses to http://jira.codehaus.org/browse/MNG-483#action_44258 1) cool 2) how about just having an "attach" parameter on each mojo that can do it? Now that I think about it, that seems much easier. 3) this should tie into (1). So (2) would always default to false, then the super POM would have a profile with the release ID that enables sources and javadocs. I'm almost inclined to leave this out and make people specify it, but put it in the archetypes... 4) I think Jason's patch takes care of this? > 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 > Attachments: assembly-050814-1.zip > > > 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]
