Andrea Selva

I suspect that https://github.com/logstash-plugins/logstash-input-file/blob/42e2ef2b094741ff5744a4eafeb82f2d70305177/lib/logstash/inputs/delete_completed_file_handler.rb#L4-L7 unlink using a File.delete in JRuby create a twin handler to the same file, the other is kept by https://github.com/logstash-plugins/logstash-input-file/blob/42e2ef2b094741ff5744a4eafeb82f2d70305177/lib/filewatch/watched_file.rb#L18-L19 so Windows doesn't delete and Unix...

Hi @MikeKemmerer thanks to raise this, fell free to come up with a PR, it's welcome will be reviewed

Hi @SUMIT0733 I think this originates from the fact the you are connecting filebeat with the HTTP input, you should use instead the `logstash-input-beats` plugin if you want to pull...

Hi @GokcerBelgusen actually no news on this, but I'll keep track in my radar

I think this a problem of versioning. If a plugin is for version >= "7.6" it can't run previous logstashes. We can postpone this change for LS 8.0.0 or if...

This new dependency `logstash-core-deprecations-adapter` should be hosted in separate repository and provide a gem with this inside, I suppose. For the Java part, with more work, I think we could...

Hi @yaauie I've investigated little bit to use ByteBuddy to redefine the interface `co.elastic.logstash.api.Context`adding a method `getDeprecationLogger` to be used by plugins updated after version 7.6 running ion LS with...

So do we provide the gem `logstash-core-deprecation-adapter` that carries the Ruby adapter idea by @yaauie plus an adapter class for old LS? Then stays to plugin developer to use the...

Discussion wrap up: - for the Ruby plugin we create and provide a gem (https://github.com/logstash-plugins/logstash-core-deprecation-adapter) with the ideas provided by @yaauie - for the Java part we clearly describe in...

Hi folks, the ``` describe in the documentation that a plugin writer that intend to use the new deprecation logger feature must bump a new a version and update the...