Simes Brown

Originally posted by Maximilian Trenks:
Hi there,
I installed the 1.4.1 runtime and tried to let it run with eclipse. In the preferences I set JVM version to 1.4. In the project settings I replaced the old rt.jar with the new rt.jar .
And I also put the new JRE into the Installed JREs in preferences/Java.
Guess what, it doesn't work ....

For recent versions of Eclipse, you don't need to include rt.jar in the project settings, as it is implicit in the "JRE System Library" entry, which is the entry you need to change. Open the project settings, go to "Java Build Path", "Libraries", click on the "JRE System Library" entry, click "Edit..." and choose the new JRE from the drop-down list. If it's not there, you can use the "Add Library..." button on this same properties page to add it.
This applies only to recent versions, of course - earlier ones only have the JRE_LIB variable. I can't say how you change this variable as I'm no longer running the earlier release. But heck, it's free - upgrade!
Simes.

Originally posted by Marina Popova:

After doing this I really appreciated JBuilder's ease of adding directories/files to the projects... You create a new project there and
then just do "Add files..." to your project from any directory and it is smart enough to figure out what package they are in and add the whole
directory to the project...
I still hope that it is rather my inexperience with Eclipse that prevents me from creating projects this way. Could somebody explain what I did wrong in setting up this project?

Have you tried using the Import wizard? Create a new project, right click the project's source folder (if there is one, otherwise right click the project), choose "Import...", and "File System", then import the directories you want.

Another problem I found is when I tried to define the "WEBLOGIC610" classpath variable. It shows the default value of "C:/....". No matter how
many times I tried to edit it - next time I examine the classpath variable the old value is there again, and Lomboz (a J2EE plugin) is using the wrong value in its Server Definitions...

I don't see this problem. Which version of Eclipse are you using?
Simes.

I am, and have been for some time. I don't do much GUI work - most of what I'm working on is server-side classes - so I've not dealt with SWT very much.
I'm very fond of it, though. If it weren't already free, the refactoring support alone would be worth the money.
Simes.

I don't know if there's a way to get Eclipse to accept file structures differently to the ones it usually uses. As a workaround if you're on Unix or a unix-alike you could create the dk/project/outteam hierarchy and have the tool folder be a symbolic link to your dk.project.outteam.tool folder.
If not, it might be possible to work something with Eclipse's import and export features, but that would probably become something of a chore.
Simes.

Originally posted by Anders Olsen:
In my project, I have some Java classes where the declared package statement in the classes does not match the path to the source file. I'm well aware of that, and I have good reasons for it, so I'm not about to change it.
Eclipse sees this as an error, and complains that "The declared package does not match the expected package". How do I tell Eclipse to accept my package statement as it is? The Java compiler has no problems with it.
Thanks
Regards
Anders

Eclipse uses directories to represent package paths to source in the same way that they are used to represent package paths to classes - in some cases the source and class files can be in the same directory.
So Class.java in the "com.whatever.stuff" packages will be in the directory "com/whatever/stuff". Which makes sense, at least to me. It certainly seems to be the common way of doing things.
So that's Eclipse's "good reason for this" - what's yours?
Simes.

Another vote here for Eclipse, and also for EditPlus for other text file editing requirements.