Community
Participate
Working Groups
Problem: When editing a Java class that imports from the the J3D libraries, the problem highlighter reports that it is unable to resolve the package javax.media.j3d, even though the appropriate jar is added to the project. The project can be compiled and run without errors. This package resolution failure causes all references to any J3D class to result in a highlighted error (which can be a LOT). Versions: Eclipse 20020410, Windows 2000, JDK 1.3.1, J3D 1.2.1_04 Steps to reproduce: - Add J3D libraries to a project - Add import to J3D package (javax.media.j3d.*) in a class - Turn on error highlighting - import line reports a 'cannot be resolved' error No other 3rd party library has exhibited the same problem.
J3D lib isn't part of the JDK, suspecting bogus classfiles in it ? Olivier - can you get a copy of J3D (through Adrian) and reproduce it ?
I made a request to get the same version of Java3D. I will check the .class files as soon as I get it.
Which version are you using? DirectX or OpenGL?
I'm using the OpenGL version.
Additional info: This also occurs when importing from the com.sun.j3d.utils package (in j3dutils.jar).
How did you get the Java3D library? Did you get the source files or binaries? I have requested it, but it seems that it only exists in source format. If you got it from source, which compiler did you use to compile it? Thanks for your answers. I need them to get the Java3D library that could allow me to reproduce your problem.
It's available at http://java.sun.com/products/java-media/3D/download.html I'm using the OpenGL SDK for Windows. J3D is only available in binary form from that page. If you want, I'll attach the version I use to the bug report, but the files come to ~3MB.
I know it is available at this link, but I cannot download it directly from the Sun web site because of license issues. I simply wanted to know if this library exists from binaries. Your answer confirms that. Thanks. I will forward it to the appropriate person. Please don't add an attachement. This is related to the license of the J3D library.
The JAR pkg fragment root info generation can be fooled if first finding a directory JAR entry matching with a package folder (will not create parent packages) and then when adding a classfile into it, it will think the parents don't need to be created since the fragment is already existing. e.g. if JAR contains exactly these 2 entries in this order, packA/packB/ packA/packB/X.class we will never create package packA/ and thus provide incorrect missing package errors. Fixed, will be released into integration build 20020430. Please reopen if symptoms were to occur again (given we haven't used the exact same test case as java3d is licensed).
Thanks, works great now.
I've installed the F1 (22 May) build into a clean directory and have the same problem with the J3D libraries. This could be verified by downloading the libraries from http://developer.java.sun.com/developer/earlyAccess/java3D/ (you'll need to register). There shouldn't be any licensing issues using these libraries to verify a fix.
Could you please let me know which version did you download and give me some steps to reproduce? Thanks. The fix is still there, so this might be another problem. Are you sure you don't have any .log in your .metadata folder. Please detail as much as possible the steps to reproduce. Thanks.
Still works for me under the F1 build (doesn't that sound so sporty?). Must be another problem.
Thanks for confirming my suspicions. Please, Henrietta, give us some steps to reproduce and specify which version you downloaded. You might want to open a new PR if it ends up being another problem. Thanks.
Well thanks for the sporty F1 response gents. I've tried again with the Windows DirectX version of the beta 2 j3d libraries and they're working as expected. I then went back to check that the beta 1 libraries were still causing a problem but they weren't ... I'll just put it down to an inexplicable transient hiccup.
Ok to close then?
OK by me.
If this occurs again, please open a new bug report. It might be a different problem. The indexer crashed or corrupted indexes or something like that. Closed.
Verified in F2.
