I will see how the Eclipse Oxygen work goes and if necessary do this step back. It is good to know this is an option.
If we are trying to maintain 2.11 and 2.12 coverage, then it may be worthwhile to create eclipse-projects-2.11 and eclipse-projects-2.12, then one could have two different eclipse workspaces. ________________________________ From: Steve Lawrence <[email protected]> Sent: Monday, August 6, 2018 8:07:45 AM To: [email protected]; Mike Beckerle Subject: Re: Daffodil development on Scala 2.12 using Eclipse Perhaps we should revert the changes to .classpath/.project to use the 2.11 library versions? The only change to your workflow would be that when running updateClassifiers, you would need to do the following to download the 2.11 versions for eclipse. sbt ++2.11.12 updateClassifiers On 07/27/2018 12:13 PM, Mike Beckerle wrote: > In rebasing onto the latest, I had to upgrade to Scala 2.12, which means > getting an Eclipse and Scala IDE that support 2.12. > > > I tried the current stable Scala IDE with these releases: > > > * Eclipse Mars - can't set a breakpoint to debug in Scala code, running > unit tests from src/test/scala works. > * Eclipse Oxygen - breakpoints work, but can't run all unit tests under > src/test/scala. Individual packages work, not the root dir of them. > * Eclipse Photon - can't set a breakpoint to debug in scala code. > > > I reported the bug in scala IDE about not being able to run tests easily. I > am not certain it is scala IDE related. I have to try the same thing from a > plain java project. > > > In any case, if developing Daffodil using Eclipse, the best configuration > right now is Eclipse Oxygen, and running tests outside the IDE using sbt. > This is really sub-optimal, but hopefully a fix will be forthcoming. > >
