[
https://issues.apache.org/jira/browse/BEAM-5763?focusedWorklogId=156398&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-156398
]
ASF GitHub Bot logged work on BEAM-5763:
----------------------------------------
Author: ASF GitHub Bot
Created on: 19/Oct/18 16:47
Start Date: 19/Oct/18 16:47
Worklog Time Spent: 10m
Work Description: swegner commented on issue #6732: [BEAM-5763] Fix wiki
link to IntelliJ
URL: https://github.com/apache/beam/pull/6732#issuecomment-431426341
Ping @kennknowles
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 156398)
Time Spent: 50m (was: 40m)
> Re-organize IntelliJ docs into workflow tasks
> ---------------------------------------------
>
> Key: BEAM-5763
> URL: https://issues.apache.org/jira/browse/BEAM-5763
> Project: Beam
> Issue Type: Sub-task
> Components: build-system, website
> Reporter: Scott Wegner
> Assignee: Scott Wegner
> Priority: Major
> Fix For: Not applicable
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> The current documentation is not well organized. It mostly focuses on how to
> get an initial setup working, but doesn't talk about common developer tasks
> (building from scratch, testing a single module / unit test / integration
> test, recovering from project corruption).
> I'd like to re-organize the documentation so to make it very prescriptive to
> follow and easy to validate that it works.
> Current set of proposed "workflows" listed in this doc:
> https://docs.google.com/document/d/18eXrO9IYll4oOnFb53EBhOtIfx-JLOinTWZSIBFkLk4/edit?usp=sharing
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
