使用 Eclipse 3.5 时黑莓 COD 文件随机丢失
我发现 BB/Eclipse 环境非常不稳定，想知道我是否在这里做了一些根本性的错误？
我构建了我的项目，它通常会生成大约 40 个左右的 COD 文件。有时，如果我清理并运行一些 COD 文件，则会丢失并且无法运行（或更糟糕的是，它会以某种方式运行旧版本）。我没有骗你，每次我想运行/测试我的设置时，我都会花费大约一个小时，这比我使用的其他平台慢一个数量级。它最终通过点击清理/调试/清理/调试/等...并且除了这些清理/调试/重复步骤之外不执行任何其他操作来工作。
如果我对我的 src 进行增量更改，那么拾取它们是相当可靠的，但是当我通过 Windows 资源管理器添加新资源并在 Eclipse 中的该目录上说“刷新”时，所有问题就开始了。
来自经验丰富的 Eclipse/BB 用户的任何指示将不胜感激（特别是如何缩小为什么有时它有效而有时无效的原因）。 谢谢， 斯图尔特
I'm finding the BB/Eclipse environment incredibly unstable and wanted to know if I'm doing something fundamentally wrong here?
I build my project and it produces about 40 or so COD files... usually. Sometimes if I clean and run some COD files are missing and it fails to run (or worse it runs the old version somehow). I kid you not, I'm spending about an hour each time I want to run/test my setup which is an order of magnitude slower than the other platforms I work with. It eventually works by hitting the clean/debug/clean/debug/etc... and doing nothing else except these clean/debug/repeat steps.
If I make incremental changes to my src it's fairly reliable at picking them up but when I add a new resource via windows explorer and say 'refresh' on that directory in eclipse it's when all the problems start.
Any pointers from experienced Eclipse/BB users would be much appreciated (especially how to narrow down why sometimes it works and sometimes it doesn't).
Thanks,
Stuart
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我相信我已经缩小了问题范围。首先，我在 src 上使用 DropBox，但这具有备份构建文件的无意功能，并且找不到禁用此功能的方法。
如果文件被 Dropbox 锁定，它毫无疑问会失败，但问题是它没有说“无法写入文件，因为它已锁定”或任何类似的有用信息......只是失败。显然，当我去检查它时，Dropbox 已经完成了它的工作，所以这是完美的犯罪！
我的经验：
在 COD 生成版本上禁用 Dropbox。
当更改 SDK 版本时，我发现我必须
通过构建配置设置更改 SDK，
干净的，
退出日食，
使用 Windows 资源管理器删除构建目录，
重新启动 Eclipse 并点击刷新/清理。
现在看来构建得相当可靠。在不重新启动 Eclipse 的情况下，我会遇到各种奇怪的错误：文件到达错误的位置以及脏数据被拾取。主要的一个是任何 //#ifdef 都没有被预处理器正确识别，因此会出现 1001 错误。
I believe I've narrowed down the issues. Firstly I use DropBox on the src but this has the inadvertent feature of backing up build files and can't find a way of disabling this.
If the files are locked by Dropbox it unsurprisingly fails, the catch is it doesn't say 'couldn't write to file as it's locked' or anything helpful like that... just fails. Obviously when I go to inspect it Dropbox has done it's stuff so the perfect crime!
My learnings:
disable Dropbox on COD producing builds.
When changing SDK version I found I have to
change the SDK via the build config settings,
clean,
exit eclipse,
delete the build directory with windows explorer,
Restart eclipse and hit refresh/clean.
That seems to build fairly reliably now. Without restarting Eclipse I get all sorts of wierd errors of files going to wrong locations and dirty data being picked up. The main one is any //#ifdef's are not picked up by the preprocessor correctly so get 1001 errors.