As far as I can see after 4/27 nightly build there is only a single change to the MTJ repository. That change is related to https://bugs.eclipse.org/bugs/show_bug.cgi?id=311318 and on a single file. The bug in question is not a high priority/critical bug. I think we can use the 4/27 nightly for producing the Pulsar M7 and pick up the fix for this bug in the next release.
--
Gorkem
On Fri, May 7, 2010 at 4:45 PM, Daniel Barboza Franco <nkvg64@xxxxxxxxxxxx> wrote:
Hi everyone,
Based on what Ian said, there is a risk of not having MTJ in Helios (therefore in pulsar too). Besides Diego is there anyone else who can generate a new build?
Gustavo, can we use the nightly build that you generated last week? I think this one would be better than 1.0.1 right?
Just to be clear, M7 is scheduled to be released today. It is not
going to be an option to use another build.
On 5/7/2010 8:55 AM, Gustavo Eliano wrote:
hi marcel,
i'm still with problems to generate it. diego just talked to me saying
that he will do it. once it is done, i will just do some basic tests to
make sure eveything is there.
if pulsar m7 will be built now, just use the 1.0.1 version that is
already on the stable repository... i hope we will have the build done
until the end of the day
as i mentioned on the bug, maybe it make sense just to remove that
option on the UI since this doesn't seems to be an important feature.
the user would still be able to use 1.0 preverification, setting that
on the project JAD
:)
gep
On Fri, May 7, 2010 at 2:09 AM, Gorkem
Ercan <gercan@xxxxxxx>
wrote:
I was playing with MTJ and i found a issue with the
preverification settings. if the user selects on JavaME preference "Use
specific configuration" (such as CLDC 1.0). This will cause the build
process to fail with an error message like:
Errors occurred during the build.
Errors running builder 'Preverification Builder' on project 'teste'.
For input string: "CLDC"
The workaround for that is just to return the preference to "Use JAD
File Setting". This will fix the problem and the build will work
properly.
The issue is on the mechanism that save the "CLDC-1.0" or "CLDC-1.1".
There is a bug there and the preference is actually saving only the
String "CLDC". This cause a NumberFormatException.