To clarify, the whole lifecycle-mapping business is both unnecessary and
actively harmful?
On 03/03/2020 14:18, Flavio Pompermaier wrote:
Sorry for the late reply. I'm using the latest Eclipse (2019-12 R) and if I
create a project using the Flink 1.10 archetype Eclipse doesn't reconstruct
correctly the sources folders.
If I remove the lifecycle-mapping plugin from the build section everything
works as expected.
About Flink development it's almost the same. I only need to install the
scale plugin if I need to debug or edit the scala code.
On Sat, Feb 29, 2020 at 12:45 AM Stephan Ewen <se...@apache.org> wrote:
Flavio, do you load Flink source code into Eclipse, or develop Flink
applications in Eclipse (based on the quickstart archetypes)?
On Fri, Feb 28, 2020 at 4:10 PM Chesnay Schepler <ches...@apache.org>
wrote:
What do you have to change it to?
What happens if you just remove it completely?
On 28/02/2020 16:08, Flavio Pompermaier wrote:
I use Eclipse but the stuff added in the pom.xml to improve the
out-of-the-box experience is pretty useless, I always have to change it
On Fri, Feb 28, 2020 at 4:01 PM Chesnay Schepler <ches...@apache.org>
wrote:
Hello,
in various maven pom.xml we have some plugin definitions exclusively to
increase support for the Eclipse IDE.
From what I have heard developing Flink is not really possible with
Exclipse (we explicitly recommend IntelliJ in our documentation); I'm
not aware of any committer using it at least.
Hence I wanted to ask here to find out whether anyone is using Eclipse.
If not, then I would like remove this stuff from the poms in an effort
to reduce noise, and to reduce issues when using other IDE's (like what
happened for vscode-java in FLINK-16150).
