You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Herve Boutemy (Jira)" <ji...@apache.org> on 2022/04/24 00:47:00 UTC
[jira] [Commented] (MNG-483) sort out artifact attachment
[ https://issues.apache.org/jira/browse/MNG-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17526945#comment-17526945 ]
Herve Boutemy commented on MNG-483:
-----------------------------------
https://github.com/apache/maven/blob/maven-2.2.x/maven-project/src/main/resources/org/apache/maven/project/pom-4.0.0.xml#L156
> sort out artifact attachment
> ----------------------------
>
> Key: MNG-483
> URL: https://issues.apache.org/jira/browse/MNG-483
> Project: Maven
> Issue Type: Bug
> Reporter: Brett Porter
> Assignee: John Dennis 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 was sent by Atlassian Jira
(v8.20.7#820007)