Sorry for starting this new thread, but looking at the bugs database, I found it very emty and unconfigured!?
Running on Eclipse 3.0.2 using Classpath Helper 1.1.1 I found a problem, that CPH simply ignores the existence of JAR files located in another project.
Something like
<classpathentry kind="lib" path="/libraries/lib/external/log4j-1.2.9/log4j-1.2.9.jar"/>
is ignored and the log4j library doesn't show up - as well the references are reported as missing...
Please help!
Thank you,
kind regrads
Tom
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hey Tom,
You are absolutely right. I actually ran into this at work about two days ago. It actually shocked me since it hadn't been reported before. It was a relatively quick fix. (and the bug is in the bug tracker 1408426). The Eclipse JDT APIs have many code paths and I occasionally find new ones I didn't fully understand, although like I said I was sort of surprised by this one.
I'm right in the middle of finishing 1.1.2 which actually has a few minor bug fixes in addition to this one.
I sort of have the code ripped apart, but let me do some testing tonight, the new code is related to resource files (being able to see them on the classpath like classes), so it probably won't effect the core functionality. Especially given that the view components aren't yet aware of files other than classes.
If I can release a quick 1.1.2 with your fix I will, otherwise I expect it to take around 2-3 weeks to make the changes I want for the properties, xml, etc files.
Thanks for your feedback.
Bryant
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sorry for starting this new thread, but looking at the bugs database, I found it very emty and unconfigured!?
Running on Eclipse 3.0.2 using Classpath Helper 1.1.1 I found a problem, that CPH simply ignores the existence of JAR files located in another project.
Something like
<classpathentry kind="lib" path="/libraries/lib/external/log4j-1.2.9/log4j-1.2.9.jar"/>
is ignored and the log4j library doesn't show up - as well the references are reported as missing...
Please help!
Thank you,
kind regrads
Tom
Hey Tom,
You are absolutely right. I actually ran into this at work about two days ago. It actually shocked me since it hadn't been reported before. It was a relatively quick fix. (and the bug is in the bug tracker 1408426). The Eclipse JDT APIs have many code paths and I occasionally find new ones I didn't fully understand, although like I said I was sort of surprised by this one.
http://sourceforge.net/tracker/index.php?func=detail&aid=1408426&group_id=147285&atid=767907
I'm right in the middle of finishing 1.1.2 which actually has a few minor bug fixes in addition to this one.
I sort of have the code ripped apart, but let me do some testing tonight, the new code is related to resource files (being able to see them on the classpath like classes), so it probably won't effect the core functionality. Especially given that the view components aren't yet aware of files other than classes.
If I can release a quick 1.1.2 with your fix I will, otherwise I expect it to take around 2-3 weeks to make the changes I want for the properties, xml, etc files.
Thanks for your feedback.
Bryant
Okay, I've released 1.1.2, the changes I'm making are not yet called via the front end.
Please let me know if this addresses the issue with not seeing you dependencies.
PS (Source Forge's ftp service seems a bit finicky right now, if the files aren't visible as of yet I will make sure they get re-uploaded.)
Bryant