vaadin / vaadin/browserless-test

Is it possible to move all Kotlin code to a separate module? The current project is unusable in Eclipse.

Open
#145 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
1
Forks
3
Avg merge
1d 20h
Merged PRs (30d)
51

Description

Kotlin is not supported in the Eclipse IDE. I've tried using the available Eclipse plugins and it wrecked my environment: All the Kotlin code showing compile errors. Maven updating itself in an infinite loop that can not be turned off.

I believe the only way I can work on code for this project is if the Kotlin code is in a separate module, which I could then link to in jar form.

Unless I am completely wrong and someone has figured out how to to work with it in Eclipse?

Rich MacDonald

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are identified. Start by examining the current Maven module layout and how Kotlin sources are included, then verify the Eclipse and Maven failure modes described in the issue. Done would require an agreed module design that lets Kotlin be consumed as a JAR and leaves the project usable in Eclipse.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, kotlin
Domain
build-system, developer-experience
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.