[
https://issues.apache.org/jira/browse/SLIDER-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15052232#comment-15052232
]
Josh Elser commented on SLIDER-1005:
------------------------------------
bq. I have attached a patch for this, move the plugin from profile to build.
Don't we still want this to be in a profile, per Steve's earlier remark?
One other question from your patch:
{code}
<output>${project.build.directory}/generated-sources/java</output>
{code}
Is Maven smart enough to find the sources here and include them in the normal
jar? Some sort of convention?
> The java code generated by protobuf should not be placed in src directory
> -------------------------------------------------------------------------
>
> Key: SLIDER-1005
> URL: https://issues.apache.org/jira/browse/SLIDER-1005
> Project: Slider
> Issue Type: Improvement
> Components: build, core
> Affects Versions: Slider 0.90
> Environment: Centos 6.5, Maven 3.2.5
> Reporter: Pan Yuxuan
> Assignee: Pan Yuxuan
> Priority: Minor
> Attachments: SLIDER-1005-001.patch
>
>
> Now slider using protobuf for RPC, but the output directory is
> <output>${basedir}/src/main/java</output> in slider-core/pom.xml. That means
> the generated java code was been placed in the src directory.
> I have seen the generated java code for protobuf in Hadoop, they put the code
> in build directory
> <output>${project.build.directory}/generated-sources/java</output>. And they
> put the compile-protoc in <plugin> not <profile> in the pom.xml.
> I think the way Hadoop used is more reasonable. The code is generated by
> protobuf, not by ourselves.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
