[
https://issues.apache.org/jira/browse/BEAM-1717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15924812#comment-15924812
]
Amit Sela commented on BEAM-1717:
---------------------------------
Seems that there is more than one issue here.
First one is with {{beam-sdks-common-fn-api}} which produces the {{javadoc}}
jar twice.
This seemed to be resolved by changing the execution id of
{{maven-javadoc-plugin}} in {{beam-parent.xml}} from {{javadoc}} to
{{attach-javadocs}} like this:
{code}
...
<profile>
<id>release</id>
<build>
<pluginManagement>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-javadoc-plugin</artifactId>
<executions>
<execution>
<id>attach-javadocs</id>
<phase>package</phase>
<goals>
<goal>jar</goal>
</goals>
</execution>
</executions>
</plugin>
...
{code}
> Maven release/deploy tries to uploads some artifacts more than once
> --------------------------------------------------------------------
>
> Key: BEAM-1717
> URL: https://issues.apache.org/jira/browse/BEAM-1717
> Project: Beam
> Issue Type: Bug
> Components: build-system
> Reporter: Amit Sela
> Assignee: Amit Sela
> Priority: Minor
>
> Running maven {{release}} or {{deploy}} causes some artifacts to deploy more
> than once which fails deployments to release Nexus.
> While this is not an issue for the Apache release process (because it uses a
> staging Nexus), this affects users who wish to deploy their own fork.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
