[
https://issues.apache.org/jira/browse/BEAM-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15838347#comment-15838347
]
ASF GitHub Bot commented on BEAM-246:
-------------------------------------
GitHub user dhalperi opened a pull request:
https://github.com/apache/beam/pull/1846
[BEAM-246] re-enable Checkstyle by default
This adds 50%+ overhead to a clean build (with testing disabled), but
per dev@ discussion is a huge usability win for contributors and
committers alike.
https://lists.apache.org/thread.html/CAA8k_FKafuon8GEA3CXwR2MZh2kAXEFZQK=bgx5tk2fzjeb...@mail.gmail.com
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dhalperi/beam checkstyle-default
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/beam/pull/1846.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 #1846
----
commit 0d0eb9bf3fa5b3facf403d486787c579c2e82228
Author: Dan Halperin <[email protected]>
Date: 2017-01-24T21:52:06Z
[BEAM-246] re-enable Checkstyle by default
This adds 50%+ overhead to a clean build (with testing disabled), but
per dev@ discussion is a huge usability win for contributors and
committers alike.
https://lists.apache.org/thread.html/CAA8k_FKafuon8GEA3CXwR2MZh2kAXEFZQK=bgx5tk2fzjeb...@mail.gmail.com
----
> Streamline default Maven profile for user efficiency
> ----------------------------------------------------
>
> Key: BEAM-246
> URL: https://issues.apache.org/jira/browse/BEAM-246
> Project: Beam
> Issue Type: Improvement
> Components: sdk-java-core
> Reporter: Kenneth Knowles
> Assignee: Daniel Halperin
> Priority: Minor
> Fix For: 0.4.0
>
>
> We should optimize the default maven profile for interactive human use. Right
> now it does a lot of things that waste time & CPU and do not speed
> development, like building the source jar and javadoc.
> We certainly still want to build all of these things in release tests,
> probably in post-commit tests, and case-by-case in pre-commit tests. But for
> these we can set up a profile to activate them.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
