Caoyuan Deng

Did you: sbt clean compile publish-local on nbsbt? The last commit: https://github.com/dcaoyuan/nbsbt/commit/6935089e17600d2c687d6ae13d76f20d52415988 indicates that I've successfully pushed it to github. On Sat, Mar 9, 2013 at 1:36 AM, rcano [email protected]...

Here is an example that I create via nbsbt automatically on akka sbt project (notice the 'managed' tag) On Sat, Mar 9, 2013 at 2:16 AM, rcano [email protected] wrote: >...

From sbt document, there is only classDirectory as the output setting key, there is no managedClassDirectory or any other settings that could tell me where will be the output classes...

BTW, since IDE is using to edit/probe only, as I've added managed sources to the internal compiler setting, that is, the output directory may not be so important for IDE...

Thanks for the information, I'll try to find a way to get the output path setting of managed sources. On Sat, Mar 9, 2013 at 5:20 AM, rcano [email protected] wrote:...

Did you find any clue in your project definition file (*.sbt or Build.scala etc) that explicitly specifies the output(classes) path of the managed source? Actually, for my understanding, the Scala's...

Since the managed sources will be re-created each time, you can try to right-click on an opening editing windows and choose "Reset Scala Compiler" when these sources created again (this...

It may be caused by wrong settings of src folders in my Scala compiler (the global), I pushed fixes: 2f00a9c59dee8bf34bd835e7c973e537cfc547cb

As the error is seen in a Java source file, when referring a generated Scala source in the managed sources folder, this issue is from uncompleted work that is going...

BTW, the netbeans cache place could be got from netbeans_installation/etc/netbeans.conf file