You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now it seems that sbteclipse doesn't "see" the extra managedSources that .enablePlugins(ProtobufPlugin) puts into a project configuration, unless that's explicitly invoked before running eclipse.
In other words, in a clean workspace, sbt eclipse will generate a correct .classpath. But running it again will not have the src_managed generated protobuf sources in it. Touching a .proto file, opening the SBT console, and typing compileand theneclipse will once more yield the correct result.
I stumbled onto this when doing an SBT 1.0 upgrade... I'm unsure whether this worked before, or whether I'm just missing something extra in my project. I'd expect that managedSources is interrogated by sbt eclipse before generating the .classpath though, so I don't know what's up.
The text was updated successfully, but these errors were encountered:
I'm using the SBT protobuf plugin together with sbteclipse, on SBT 1.0.1.
Now it seems that
sbteclipse
doesn't "see" the extramanagedSources
that.enablePlugins(ProtobufPlugin)
puts into a project configuration, unless that's explicitly invoked before runningeclipse
.In other words, in a clean workspace,
sbt eclipse
will generate a correct.classpath
. But running it again will not have thesrc_managed
generated protobuf sources in it. Touching a.proto
file, opening the SBT console, and typingcompile
and theneclipse
will once more yield the correct result.I stumbled onto this when doing an SBT 1.0 upgrade... I'm unsure whether this worked before, or whether I'm just missing something extra in my project. I'd expect that
managedSources
is interrogated bysbt eclipse
before generating the.classpath
though, so I don't know what's up.The text was updated successfully, but these errors were encountered: