[
https://issues.apache.org/jira/browse/BEAM-1717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15938385#comment-15938385
]
ASF GitHub Bot commented on BEAM-1717:
--------------------------------------
GitHub user amitsela opened a pull request:
https://github.com/apache/beam/pull/2303
[BEAM-1717] maven-javadoc-plugin execution id should match the id in …
…apache parent.
Be sure to do all of the following to help us incorporate your contribution
quickly and easily:
- [ ] Make sure the PR title is formatted like:
`[BEAM-<Jira issue #>] Description of pull request`
- [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable
Travis-CI on your fork and ensure the whole test matrix passes).
- [ ] Replace `<Jira issue #>` in the title with the actual Jira issue
number, if there is one.
- [ ] If this contribution is large, please file an Apache
[Individual Contributor License
Agreement](https://www.apache.org/licenses/icla.txt).
---
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/amitsela/beam change-javadoc-execution-id
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/beam/pull/2303.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2303
----
commit c910d09cf85a40edca4cae24a0b30f7190923859
Author: Amit Sela <amitsel...@gmail.com>
Date: 2017-03-23T14:13:00Z
[BEAM-1717] maven-javadoc-plugin execution id should match the id in apache
parent.
----
> 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)
