UPDATE
I edited the question after doing additional troubleshooting and realizing that the issue is specific to Kotlin and not a general problem with Eclipse.
ORIGINAL QUESTION
In an earlier question, I found that I need to set the Disable Workspace Resolution setting in order to successfully deploy applications to Tomcat within Eclipse, when the application has references to co-developed dependencies (i.e. dependencies which I am also primarily developing along with the main application). The Disable Workspace Resolution setting has many inconveniences, not the least of which is a need to run mvn install any time the code in a dependency project is modified.
My question now is:
What do I need to configure, either in Eclipse, Maven, or Tomcat, in order to start using Enable Workspace Resolution successfully with Kotlin?
I have reviewed essentially all of the SO questions on the topic, unfortunately none of them specifically address Eclipse with Kotlin:
- Eclipse maven-enabled web app references workspace projects, but those are not deployed when running Tomcat server
- How to get Maven plugin to use Eclipse workspace resolution?
- Maven workspace resolution horked
- maven-assembly-plugin and eclipse Workspace resolution
- How make Eclipse uses maven projects even if Workspace resolution is not working?
- maven eclipse workspace resolution
- Maven workspace resolution missing jars for local Tomcat testing
- Maven project and Eclipse workspace
- M2E Eclipse Maven Workspace resolution and CDI
- Eclipse Maven Workspace Resolution not seeing Generated Classes
- Using Tomcat within Eclipse for a Maven project
- Deploy Maven Project using Eclipse and Tomcat
- maven + eclipse + tomcat : class not found exception
- How to run a Maven Project In Tomcat From Eclipse
- Deployment to tomcat from eclipse via M2eclipse and Maven
Go through following steps,
Enable Workspace Resolution for your project.
Right-click the project, then Maven > Enable Workspace Resolution.
Finally, if your project no longer resolved,
This should resolve your problem. If after this, your dependencies are still referenced from the file system, test the groupId, artifactId and particularly model of each dependency again.
And check if you don't have any errors in your project