[
https://issues.apache.org/jira/browse/FLINK-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14294137#comment-14294137
]
ASF GitHub Bot commented on FLINK-1330:
---------------------------------------
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/333#issuecomment-71722351
We can bind the `unlink`to the `pre-clean` phase, see if that helps.
All in all, if it does not work, it does not work. This is a nice utility,
by no way crucial enough to spent huge amounts of time on it...
> Restructure directory layout
> ----------------------------
>
> Key: FLINK-1330
> URL: https://issues.apache.org/jira/browse/FLINK-1330
> Project: Flink
> Issue Type: Improvement
> Components: Build System, Documentation
> Reporter: Max Michels
> Priority: Minor
> Labels: usability
>
> When building Flink, the build results can currently be found under
> "flink-root/flink-dist/target/flink-$FLINKVERSION-incubating-SNAPSHOT-bin/flink-$YARNVERSION-$FLINKVERSION-incubating-SNAPSHOT/".
> I think we could improve the directory layout with the following:
> - provide the bin folder in the root by default
> - let the start up and submissions scripts in bin assemble the class path
> - in case the project hasn't been build yet, inform the user
> The changes would make it easier to work with Flink from source.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
