8/28/2017 7:21:24 PM
code style template. Update README
- Modify the style template to preserve line feeds in the Javadoc. This
makes it easier to preserve the Javadoc format in the source file. This
is especially helpful given this intellij issue
"Formatting doesn't apply to javadoc in modified files"
https://youtrack.jetbrains.com/issue/IDEA-178073
- Change the name of the style config file and the style name
to reflect that it is now a customized style for the project.
And it contains styles for other languages such as JavaScript as well.
- Update the README to reference the new style file. Make it clear that
the new style need to be activated after it is imported.
- Update the README to require saveAction plugin. We have finished
auto formatting all the source files.
* Change style rules in the README file
The modification we made to the style configuration i.e. preserving line
feeds is still consistent with the Google style guide.
It's simpler to state we follow strictly the Google style.
Also added the link to the specific version of the config file our
configuration file is based on. It makes it easier to merge in new
changes to the Google style config in the future.
|
8/27/2017 10:25:35 PM
class (#1404)
Use proper javadoc tags to preserve the formatting of the xml example in the javadoc. {@code} is used to prevent javadoc compiler from misinterpreting the xml tags as javadoc tags. The `<pre>` tag prevents intellij from attempting to reformat the example code.
See
http://www.rgagnon.com/javadetails/java-0623.html
|
8/27/2017 10:17:28 PM
class (#1403)
Adjust `<p>` tags placements to conform to the Google style guide.
Include more details in the class summary line.
See
https://google.github.io/styleguide/javaguide.html#s7.1.2-javadoc-paragraphs
Also see
http://www.oracle.com/technetwork/java/javase/documentation/index-137868.html
http://blog.joda.org/2012/11/javadoc-coding-standards.html
Note that the Google style places <p> after the empty line. It's
different from the Oracle style.
|
8/27/2017 10:10:49 PM
output (#1405)
It's useful to see additional information. It's currently difficult to
debug a flaky test that only fails in Travis since there is no easy way
to see the test's console output.
|
8/27/2017 10:03:27 PM
Issue
Travis CI build sometimes fail with the following error
'''
Process 'Gradle Test Executor 6' finished with non-zero exit value 137 travis
'''
## Fix
See
https://discuss.gradle.org/t/gradle-travis-ci/11928/9
https://discuss.gradle.org/t/travis-ci-org-gradle-launcher-daemon-client-daemondisappearedexception-gradle-build-daemon-disappeared-unexpectedly-it-may-have-been-killed-or-may-have-crashed/13106/3
|
|
|
|
|
|
|
|
|
|
|
