Community
Participate
Working Groups
I20030925 + newest code (Jdt Core + Jdt UI for I20030930). Note: this is not reproducable but I've seen it at least twice: 1. start with fresh worksapce 2. create Java project "JUnit" 3. import JUnit source from zip file ==> background build kicks in (ok) everything got correctly compiled BUT: Neither Package Explorer nor Java Browsing views show any Java elements besides the Java project itself. Closing and reopening the views doesn't help. Closing and reopening the project fixes the problem. Nothing in .log. Martin, might this be caused by our content provider changes?
Sound's more like a problem in jdt.core. If refresh doesn't help it seems to me that the model is not complete. Was this with PRIMARY_WORKING_COPIES or without?
PRIMARY_WORKING_COPIES= false. Happened during smoke test but Markus also saw this in his dev workspace. I assume it is related with background building.
Asdking JDT/Core if this is related to bug 43847
Sounds like a dup of bug 43670. Are you sure you were using a better JDTCore ?
Yes, the one you released for the build (v_373 - we could not take the advertised version v_374 since it did not exist). Note: it is sometimes hard for us to know which JAR belongs to which CVS code since you only update the JAR on your web page but you don't update the CVS tag on that page. Currently there's a JAR from yesterday but it says: Corresponding sources are versioned using tag v_370
The web page is wrong. The build note is the one telling the truth: Eclipse SDK 3.0M4 Build - ?th September 2003 Project org.eclipse.jdt.core v_373 (cvs). Also once you grab the JAR, you can tell its version with the following command: java -classpath jdtcore.jar org.eclipse.jdt.internal.compiler.batch.Main - version
v_374 isn't released yet, it is the next version in progress.
The thing why I brought this up is because we don't import the J Core JAR on our build machine: we use the tagged code. This makes it easier for us: we export the J Core stuff together with our stuff on a daily basis to a plugin-export location. Therefore it would be very handy if you could provide a tag at least for the official patches.
This isn't a likely thing we can promise, we will only version once we think we are done, and usually there are a few tweaks to perform in the last day before integration.
That's no problem as long as we can rely on the information on the web page. If there's a JAR and an outdated tag then this is the problem. If you post a patch and remove the tag info if outdated then we know we have to take the JAR since there's no tag yet.
I got this bug again 2 times again. (using jdt.core v_373b). - Start with a new workspace - Create a new Java Project, use project as source folder and output location - File->Import..->Zipfile junitsrc.zip - Look in the package explorer: The sources are imported but there are no package fragments, only resource folders. It seems as if no source folder is configured. However, looking at the build path page: Everething is fine - Close and open the project to get the correct view
Martin, I cannot reproduce your problem even if I precisely following your scenario with version v373b. I've also use latest versions (v373c and HEAD stream) and still cannot reproduce it. Are you sure you gave us correct steps for this issue? Frederic
I finally found where the problem was. In your scenario you said that project should be source folder and output location. This is wrong as to reproduce the problem output location has to be different than source folder. I've tried with JUnit/bin for output location and project for source folder and reproduce the bug *systematically*. The good news is that now we're able to reproduce the problem, Jerome identifies it as a duplicate of bug 44066. I've verified that whith his fix, this issue does not longer happen with version v373c and after. *** This bug has been marked as a duplicate of 44066 ***
