This content has been marked as final. Show 7 replies
Only the owner has write permission to that directory. If you're not the owner, you don't.
Yes indeed, but i launch idlj as the owner of the directory.
I set permissions to 777 for this directory and its parent and tried again.
I'have downloaded sources of idlj in OpenJDK 7 project.
Using this version it works.
But if i display "-version" on downloaded "source" version and the released one in my java install they are the same...
IDL-to-Java compiler (portable), version "3.2"
It works fine with a fresh jdk 1.7 but the version number has not been increased...
java version "1.7.0-ea"
Java(TM) SE Runtime Environment (build 1.7.0-ea-b103)
Java HotSpot(TM) 64-Bit Server VM (build 19.0-b04, mixed mode)
Looks like this has been around for a long time. The corba idlj compiler has some bad argument parsing code. If the path to your idl source file starts with "/d", "/D", "/i", or "/I" the idlj compiler will fail with no exit code, Make doesn't stop, and it can cascade into a build failure. The beginning / in these cases is treated as a '-' (it allows for - options and / options), the option name starts with 'd' or 'i', so the rest is assumed to be an option argument to '-d' or '-i', e.g. 'idlj /Doh/filename.idl' is treated as 'idlj -d oh/filename.idl' and fails.
Bottom line, either use a relative path that does not start with /, or use a full path that does not start with /[Dd][Ii].
That's incredible. It's not as though argument parsing is rocket science.