[
https://issues.apache.org/jira/browse/HIVE-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654818#action_12654818
]
Johan Oskarsson commented on HIVE-144:
--------------------------------------
A few alternatives:
# If we'd want to make the handling of generated code a bit more consistent we
could put the code from Hive.g into svn under ql/src/gen-java much like the
thrift generated code in other modules.
# Copy ql/src/java into build/ql/java or a similar directory that is not
build/gen-java
Personally I'd vote for the first option.
> Ql java source copied to build/gen-java
> ---------------------------------------
>
> Key: HIVE-144
> URL: https://issues.apache.org/jira/browse/HIVE-144
> Project: Hadoop Hive
> Issue Type: Bug
> Components: Build Infrastructure
> Affects Versions: 0.19.0
> Reporter: Johan Oskarsson
> Priority: Trivial
> Fix For: 0.19.0
>
>
> Since HIVE-98, the build process copies the contents of the ql/src/java
> directory to build/gen-java where the code generated from Hive.g is located.
> This makes it a bit more difficult to work on the project in Eclipse, since
> one has to add the build/gen-java folder to the project and not ql/src/java.
> This means we'll edit the ql java files in the wrong location. Adding both of
> these directories will of course result in duplicate entries.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.