You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/01/05 17:14:58 UTC
[jira] [Commented] (BEAM-246) Streamline default Maven profile for
user efficiency
[ https://issues.apache.org/jira/browse/BEAM-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15801906#comment-15801906 ]
ASF GitHub Bot commented on BEAM-246:
-------------------------------------
GitHub user dhalperi opened a pull request:
https://github.com/apache/beam/pull/1740
[BEAM-246] Improve developer experience after streamlined Maven profile
* Rename the `release` profile that contains enhanced validation to `all-checks`
* Add the proper test command `mvn clean install -Pall-checks` in the GitHub Pull Request template.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dhalperi/beam all-checks
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/beam/pull/1740.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 #1740
----
commit 17aa11de70f5fb08fb4f7d113388bda25fee73b8
Author: Dan Halperin <dh...@google.com>
Date: 2017-01-05T17:09:59Z
Rename `release` profile to `all-checks`
commit d913b03bbea5297554d002b639b85b8d0583d9bc
Author: Dan Halperin <dh...@google.com>
Date: 2017-01-05T17:11:37Z
Update pull request template to include the all-checks profile
----
> 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)