I'm downloading these games fo my nokia onto the computer then uploading them onto my phone, in the past i've been able to do this with no problems but now it comes up with this message when i try to open the file:
Failed to load Main-Class manifest attribute from C:DOCUMEN... etc..
What do i do..?!
> looks like whoever wrote the game only tested it on a
> simulator on their local machine. the manifest
> appears to refer to something in my documents.
> the clown
But it worked in my IDE!!!!!! Why does it not work from blah, blah, blah!!!!
;-)
> > looks like whoever wrote the game only tested it on
> a
> > simulator on their local machine. the manifest
> > appears to refer to something in my
> documents.
> > the clown
>
> But it worked in my IDE!!!!!! Why does it not work
> from blah, blah, blah!!!!
>
>
> ;-)
worrying, isn't it?! even more worrying is when a developer makes those noises about a utility they wrote for - and released to - a merchant bank, as I saw a few years ago. again, hard-coded paths to somewhere on the guys own box were in production code. argh!
> worrying, isn't it?! even more worrying is when a
> developer makes those noises about a utility they
> wrote for - and released to - a merchant bank, as I
> saw a few years ago. again, hard-coded paths to
> somewhere on the guys own box were in production
> code. argh!
Great!!! If it actually made it to production, though, the bank is at least partially responsible. Where was the QA/Integretion Test machine/environment, which should, of course, never be located on the same machine/in the same environment as the development machine/environment. And, should never allow unrestricted/unsupervised access to any developer(s).
> > worrying, isn't it?! even more worrying is when a
> > developer makes those noises about a utility they
> > wrote for - and released to - a merchant bank, as
> I
> > saw a few years ago. again, hard-coded paths to
> > somewhere on the guys own box were in production
> > code. argh!
>
> Great!!! If it actually made it to production,
> though, the bank is at least partially responsible.
> Where was the QA/Integretion Test
> machine/environment, which should, of course, never
> be located on the same machine/in the same
> environment as the development
> machine/environment. And, should never allow
> unrestricted/unsupervised access to any developer(s).
thankfully the banks QA did catch it, which is where I came in. about 10 minutes later I found what the guy had done. interestingly, we both left the company at the same time and interviewed for the same job. I had to review his code in my interview. guess who got the job :-)
> thankfully the banks QA did catch it, which is where
> I came in. about 10 minutes later I found what the
> guy had done. interestingly, we both left the company
> at the same time and interviewed for the same job. I
> had to review his code in my interview. guess who got
> the job :-)
Well, that is, at least, a kind of just rewards. ;-)
