[
https://issues.apache.org/jira/browse/HTRACE-180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14582535#comment-14582535
]
Colin Patrick McCabe commented on HTRACE-180:
---------------------------------------------
bq. My patch has go build into htrace-htraced/target rather than
htrace-htraced/src/go/build. htrace-htraced/src/go seems fine as location for
src.
That sounds like a good layout. However, I had a lot of problems changing this
in the past. Can we do this in a separate JIRA?
bq. Will do up a patch that depends on dev setting HTRACED_WEB_DIR when they
want to do webapp dev.
How about defaulting {{HTRACED_WEB_DIR}} to {{`dirname $0`/../web}}, and then
creating a (relative) symlink in that position named web, which went to the
{{htrace-gui}} directory? Then the default could be appropriate for both the
installed version (where the RPM would put the web directory there) and the
source tree version. I'd rather not put up roadblocks in front of people
trying to run the code out of the source tree (even if there are ways around
the roadblocks). it should "just work" so that new developers can hit the
ground running.
> Move the GUI to a top-level subproject
> --------------------------------------
>
> Key: HTRACE-180
> URL: https://issues.apache.org/jira/browse/HTRACE-180
> Project: HTrace
> Issue Type: Improvement
> Reporter: Colin Patrick McCabe
> Assignee: stack
> Attachments: 180.txt, HTRACE-180.002.proof-of-concept.patch
>
>
> Move the GUI to a top-level subproject, so that we can use it for
> htrace-hbase as well as htrace-htraced (and possibly other subprojects in the
> future)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
