Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 315209 - [fiximprove]: Issue with WTK 3.0 import
Summary: [fiximprove]: Issue with WTK 3.0 import
Status: NEW
Alias: None
Product: MTJ
Classification: Tools
Component: SDK Management (show other bugs)
Version: 1.0.1   Edit
Hardware: PC Windows XP
: P3 normal with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 299872 (view as bug list)
Depends on: 318500
Blocks:
  Show dependency tree
 
Reported: 2010-06-01 09:08 EDT by Gustavo de Paula CLA
Modified: 2010-08-17 05:45 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Gustavo de Paula CLA 2010-06-01 09:08:35 EDT 
it seesm that the devices are being imported with both the CLDC 1.0 and CLDC 1.1 jars. but since the 1.0 is imported first it end up being used as the project stubs. this problem of that is that some cldc 1.1 methods are not found for instance all dataoutstream float and double related methods.

there is a discussion about that on MTJ forum
http://www.eclipse.org/forums/index.php?t=msg&th=168599&start=0&
Comment 1 Gorkem Ercan CLA 2010-06-10 11:52:54 EDT 
*** Bug 299872 has been marked as a duplicate of this bug. ***
Comment 2 Gorkem Ercan CLA 2010-06-11 05:14:47 EDT 
WTK reports both CLDC 1.1 and CLDC 1.0 as part of its boothclasspath and supported API list. This is not consistent with the other UEI compliant SDKs and also with the earlier WTK2.5.2. WTK 2.5.2 reported both on supported API list only. I think the safest way to fix this is to create a WTK3 device importer.
Comment 3 Gorkem Ercan CLA 2010-07-03 16:43:36 EDT 
Investigating further, the root cause of the WTK problem is because MTJ build path does not filter out the profile & configuration that is not active for the project. This causes both CLDC 1.0 and CLDC 1.1 classes to be present for the project. However the project aims only one. This does not happen with most other SDKs because they usually support a single configuration jar file. There is bug 318500 for addressing this problem.
Comment 4 Amitkumar Raodeo CLA 2010-08-17 05:45:47 EDT 
This is a blocking issue.

I am unable to use WTK 3.0 with MTJ 1.0.1 plugin in eclipse 3.5.2, currently i am using nokia emulators.
I am facing the issue even when the configuration is selected by the emulator configured for the project and not by using jad file, which is also not working as mentioned in bug 318500.

This is definitely higher priority issue than P3 normal.