| Summary: | Unable to create editor ID org.eclipse.mtj.ui.editor.BuildProperties: null argument | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Tools] MTJ | Reporter: | Fabio <wolfetti.bsk> | ||||
| Component: | UI | Assignee: | Project Inbox <dsdp.mtj-inbox> | ||||
| Status: | NEW --- | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | diegosandin, remy.suen | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Fabio
Cannot proceed without more information. Please attach your workspace's log file (workspace/.metadata/.log). Created attachment 181714 [details]
Eclipse log file stack trace.
Wow how fast you are! :D however, it was just what I was doing! Thank you very much, Fabio It looks like this can happen only if you do not have an active configuration for your midlet project. This is very unlikely for the midlet projects but if you have a case I can reproduce that would be helpful. On a second thought, you can have a similar effect if this editor used on a project that is not a midlet project. Can you say if you are opening a build.properties file from a midlet project I can reproduce this only when MTJ build property editor is used on a non-midlet project. |