operator-framework/java-operator-plugins

Remove .placeholder file generated after operator-sdk init command

laxmikantbpandhare opened this issue · 5 comments

Bug Report

.placeholder file gets generated after init command.

What did you do?

I created memcached operator using init command.

What did you expect to see?

.placeholder file is not expected.

What did you see instead? Under which circumstances?

Screen Shot 2021-10-20 at 3 31 01 PM

Environment

Operator type:

Kubernetes cluster type:

Minikube

$ operator-sdk version

v1.13

$ java -version (if language is Java)

16.0.2

$ kubectl version

1.22.2

Possible Solution

Delete this file in next steps. Maybe in Create API command.

thank you @jmrodri for your comment - #33 (comment)

Does the .placeholder get picked up by the generated jar?

I suggest we just remove the generation of this file entirely. The only reason it exists is to allow you to commit the src/main/java directory structure before you add any files to it.

@jmrodri - I tried to remove the .placeholder from the code but /src/main/java is not creating directory. Instead, it is created java as a file. This is the issue of our scaffolding architect only. For now, I added it in init command and removed when we are running create api command.

Screen Shot 2021-10-26 at 9 45 11 PM

Updated the code and it will make directory structure like /src/main/java during init command.