[
https://issues.apache.org/jira/browse/MNG-5901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16516295#comment-16516295
]
Robert Scholte commented on MNG-5901:
-------------------------------------
Yes and no. maven-artifact-transfer contains a workaround that works. I
thinking about a new feature of the plugin API, which might superceed this
issue.
{code}
@Deliverable
private File targetFile; // can either be Path, File or String
@Deliverable ( classifier = "sources" )
private File attachedFile;
{code}
If Maven supports something like this, there's no need to expose the
(Sub)Artifact. Only in that case there's no need to fix this.
> Export org.eclipse.aether.util.artifact.SubArtifact
> ---------------------------------------------------
>
> Key: MNG-5901
> URL: https://issues.apache.org/jira/browse/MNG-5901
> Project: Maven
> Issue Type: Bug
> Components: Deployment
> Affects Versions: 3.1.1, 3.2.1, 3.2.2, 3.2.3, 3.2.5, 3.3.1, 3.3.3
> Reporter: Robert Scholte
> Assignee: Robert Scholte
> Priority: Major
> Fix For: 3.x / Backlog
>
>
> Without exporting {{org.eclipse.aether.util.artifact.SubArtifact}} you will
> get a {{ClassNotFoundException}} when trying to deploy/upload attachments
> using the pure Aether solution by Eclipse.
> This is also the reason why maven-artifact-transfer shades this class, so
> this component will still work with all Maven versions between 3.1.1 and 3.3.3
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
