[Bluej-discuss] endless compilation without diagnostic

[Michael Kölling]

I have seen something similar (in fact, it's logged as a bug) for  
projects where the path (a folder name) contains non-ascii characters.

(That should, however, be the same in this and previous versions.)

Could it be that your project folder (or any parent folder) name  
includes non-English characters? Unfortunately, currently that  
creates a character encoding problem that results in the behaviour  
you describe.

We are working on a solution, but since it is complicated, we decided  
not to include it in the previous release.

Michael


On 5 May 2006, at 14:57, Javier Mas wrote:

> I have just upgraded to BlueJ 2.1.3 running on Java 1.5.0_06  with
> MacOS Tiger 10.4.6.
> I deeply regret having done so.
>
> Now the compiler simply shows no message. If I simply omit a single
> semicolon (on purpose)
> and close the class code window the corresponding icon on the project
> window
> now shows a small broken arrow (I assume it has detected the  
> error!!!).
>
> If I now  click on the  compile button, the message "compiling"
> appears on
> the left lower corner of the Project window
> and stays there forewer.  This occurs even with a plain new class that
> I make by clicking on the New Class button.
>
> The only way through, in cases where I can fix the mistake, is
> to rebuild the hole project.
>
> ¿Nobody has the same problem?
>
>
> Javier
>
>
> _______________________________________________
> mailing list bluej-discuss at bluej.org
> To unsubscribe or change your preferences, go to
> http://lists.bluej.org/mailman/listinfo/bluej-discuss