GitHub user ahgittin opened a pull request:
https://github.com/apache/incubator-brooklyn/pull/879
minor tweaks to docs during 080 release
javadoc errors now seem to be fatal, so simply warn on them, and record
lessons from gpg pinentry woes
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ahgittin/incubator-brooklyn 080-fixes-090
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-brooklyn/pull/879.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 #879
----
commit 0d5dc59749b9a9eba076abdc647732fcf8619834
Author: Alex Heneveld <[email protected]>
Date: 2015-09-03T01:06:33Z
tips on debugging pinentry when doing the release
commit b8869d2958bdd1e55511c4d52ae5282562089782
Author: Alex Heneveld <[email protected]>
Date: 2015-09-03T01:06:47Z
make release script takes -y and checks for existing gpg-agent
commit 98cf3a83d7ba46557a6e764ef22f9d24d3f5e358
Author: Alex Heneveld <[email protected]>
Date: 2015-09-03T01:07:06Z
allow malformed javadoc
commit bd1dd8bff8f98687bf3a51e652253cca97db0ac0
Author: Alex Heneveld <[email protected]>
Date: 2015-09-03T02:14:54Z
ignore javadoc errors in docs build
javadoc seems a lot stricter here (updated os x environment), both in CLI
and maven.
i wonder if the exit code has changed...
commit 1760fd604719fafa5f2b533e67aca6904ba81e16
Author: Alex Heneveld <[email protected]>
Date: 2015-09-03T02:16:09Z
minor tweaks to doc build process advice
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
