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
Eclipse build fails in master because CliBase.java, LFStandaloneModule.java, Lfc.java, and other classes reference ReportingUtil.kt. Does that class have to be Kotlin?
There is also this error:
Description Resource Path Location Type
Bundle 'org.lflang.epoch.external.dependencies' cannot be resolved MANIFEST.MF /org.lflang/META-INF line 19 Plug-in Problem
The text was updated successfully, but these errors were encountered:
This class does not have to be Kotlin (non of our classes have to). But I would consider converting it back to Java a step backwards.
This issue was caused by merging #1422. This PR integrates the contents of org.lflang.cli into org.lflang as a first step for simplifying our source tree layout (see #1276). I think the problem occurs now, because Eclipse simply did not compile org.lflang.cli before since it is not needed for Epoch.
Since the cli subpackage is not used by Epoch, my proposal is to exclude it from the source list in the Eclipse configuration. Should this not work for some reason, I would propose to convert all classes in cli to Kotlin, as then they are effectively ignored by Eclipse.
Eclipse build fails in master because CliBase.java, LFStandaloneModule.java, Lfc.java, and other classes reference ReportingUtil.kt. Does that class have to be Kotlin?
There is also this error:
Description Resource Path Location Type
Bundle 'org.lflang.epoch.external.dependencies' cannot be resolved MANIFEST.MF /org.lflang/META-INF line 19 Plug-in Problem
The text was updated successfully, but these errors were encountered: