You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2005/08/05 08:02:58 UTC
[jira] Commented: (MNG-483) sort out artifact attachment
[ http://jira.codehaus.org/browse/MNG-483?page=comments#action_43983 ]
Brett Porter commented on MNG-483:
----------------------------------
I think the current code attachment will suffice for now.
I think removing the SNAPSHOT check and letting users add a release profile that the release plugin always uses (but that they can use too) is a good way to do this.
I'm not yet sure how to enable the source binding by default, and how to disable it once enabled. Thoughts?
> 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org