Error using sbteclipse with SBT 1.4.0 about sbt-eclipse HOT 12 CLOSED

@bpossolo You are right. There are more changes than necessary. My initial goal was to unblock a collegue. I have not tested this on eclipse myself and as I mentioned there is one test failing. Nevertheless I created the PR, but I am fairly certain that no one will care to merge it unless this test is fixed.
Generally this may run into issues when the internal api change, but I would worry about that once the time comes. Doing such a change exceeds my allotted time.

As for the underlying issue: sbt changed to use VirtualFileRef instead of File. The plugin tries match source files to their generated artifacts (as part of the sbt execution). My fix is to map the source files to VirtualFileRef, than match those against the Analysis.relations, followed by copying the generated artifact to the proper folder.

from sbt-eclipse.

I created a fix in my fork at https://github.com/domizei385/sbteclipse (Branch sbt_1.4).
There is one test still failing, but it is not relevant for my use case.

from sbt-eclipse.

seeing this with sbt 1.4.7 + sbteclipse 5.2.4

from sbt-eclipse.

@domizei385 How about creating a pull request with your fixes?

from sbt-eclipse.

@domizei385 your branch has a lot of changes that seem like they might be unnecessary to get the plugin to work.
if you don't have time to submit a PR, could you describe what the main issue is?
It looks like the issue is caused by a reference to an sbt internal method which no longer exists.
I noticed in your branch you're still using sbt.internal.inc.Analysis
is it safe to reference sbt.internal.* components or does that open it up for failure again in the future the next time the internal api changes?

from sbt-eclipse.

Any plans of a fix for this issue? We would like to use sbt 1.5.0 with PlayFramework v2.8.8

from sbt-eclipse.

A couple of weeks ago I had a look what the problem is and I think back then I found out what's going on. Maybe I find them the next days to provide a pull request with a fix (but I am busy currently)

from sbt-eclipse.

Thanks, looking forward to a fix.

from sbt-eclipse.

Hi,
Any progress on this issue ? We need to upgrade to newer sbt version due to log4j vulnerability but this issue stops us from upgrading

Thanks

from sbt-eclipse.

No time to work on it yet, but it's on my radar.

from sbt-eclipse.

We are very close to a sbt-eclipse 6.0.0 release, finally with support for sbt 1.4.0+ (I merged #402 already). Now I am waiting for access to push the artifacts to maven central: https://issues.sonatype.org/browse/OSSRH-77819?focusedCommentId=1202733&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-1202733

I hope that happens within the next 24 hours.

from sbt-eclipse.

It took ages, but finally, after 5 years, I just released a new sbt-eclipse version: https://github.com/sbt/sbt-eclipse/releases/tag/6.0.0 with support for newer (1.4+) sbt versions.
Be aware that the groupId and artifact name changed, see the release notes.
Also, from now on, releases are hosted on Maven Central, so you don't need to configure any resolvers: https://repo1.maven.org/maven2/com/github/sbt/sbt-eclipse_2.12_1.0/6.0.0/

from sbt-eclipse.