[
https://issues.apache.org/jira/browse/HTRACE-180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14582411#comment-14582411
]
Colin Patrick McCabe commented on HTRACE-180:
---------------------------------------------
The source and the build products of the Go build are actually very cleanly
separated at this point. Nothing under {{htrace-htraced/src/go/src}} is
generated or downloaded. The downloaded or generated files are under
{{htrace-htraced/src/go/\{build,pkg,Godeps\}}}. I guess perhaps it's confusing
that those build directories have "src" in the path, even though they contain
build products. Perhaps we should move {{htrace-htraced/src/go}} to
{{htrace-htraced/go}} to avoid this confusion? I don't think the Go build
directories will ever look exactly like Java build directories, but I think
that's OK.
We need to be able to make changes to the htraced web GUI and try them without
running Maven. Maven just adds a lot of delay to the Javascript development
process. I think we should just change the default value of
{{HTRACED_WEB_DIR}} to be the relative path to the htrace-gui project. Let me
post a patch as a proof-of-concept for that
> 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
>
>
> 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)
