Originally posted by Craig Demyanovich:
I've found another annoyance with Eclipse: the integrated Ant seems to have a problem with build files that access the system environment via Ant's feature to do so.
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Originally posted by Craig Demyanovich:
Like Frank Carver, I'm feeling a bit of the straitjacket. I use IDEA, and it makes very few assumptions about what I'm doing with my project's files.
For my projects, I like to keep JUnit TestCases in the same package as the class to be tested, but I keep them in a separate subtree of the source tree:
IDEA has no problem with this layout. Eclipse, however, indicates a number of errors in my TestCase classes that production classes can't be found. Unless I have misused/misconfigured Eclipse, this behavior will surely hinder my adoption of it. I hope that someone can correct me.
Thanks,
Craig
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Originally posted by Frank Carver:
Like: it will run Ant scripts for you but you have to jump through hoops to avoid getting lots of wierd error messages about compilers. Why should it be so hard?
Like: it will call JUnit to run your tests but you have no control about where it sets the "current directory" to, so all my tests which access files fail.
Like: I can't find out how to make it automatically write out modified files before running Ant or JUnit
Like: It has some idea of what projects are on the system and won't let me create a new one with a name which already "exists" - yet I can't find the contentious name anywhere in the lists of projects or in the Eclipse config files.
I haven't really looked at any of the other major contenders (JBuilder, Forte/netbeans, IDEA, ...) Do they also have the same "straitjacket" mentality?
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Originally posted by Ilja Preuss:
Mhh, we don't have any problems with this, neither on windows nor linux.
I suppose you tried the script from the command line and didn't get this error?
Originally posted by Ilja Preuss:
I just tried that and it seems to work out fine.
Did you set up both main and test as source folders?
Originally posted by Frank Carver:
Ilja wrote: I didn't ever get any weird error messages about compilers from the ant integration. Can you please elaborate?
I can't believe you never saw this one, Kyle gave an answer in this thread.
You can configure the working directory in the launch configuration editor (use the "Run..." menu item).
I've looked there, and I can see entries for some Ant build files but nothing relating to JUnit. Can you give me a bit more detail on how I set the working directory for JUnit?
For JUnit, you should get a dialog giving you the option to save all "dirty" editors when starting a test. Nope, it just runs it, ignoring the changes, no dialogs or anything, both if I quit the JUnit pane and start it from the menu, and if I just click the "little man" in the JUnit pane title bar.
Did you take a look at the Navigator? The Package Explorer doesn't show non-java or closed projects.
I'm not sure what you mean here. I think one of my main problems with Eclipse is stil that I don't understand the "shape" of it.
What is a Navigator, what is it for, and how to I get to it? There doesn't seem anything useful in the "Navigate" menu. I may have been already using it, but I'm not sure how I would know !
I'm still looking for some documentation which bridges the gap between a "type in this example and say yes to everything" tutorial and the "how to build a new plug-in" programmer information.
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Originally posted by Frank Carver:
Sorry, I guess I wasn't clear enough. I meant the "Run..." menu item in the "Run" menu (the one below the "Run as" menu item). There you can set the working directory for every single launch configuration.
Is that how you run JUnit, then? I've always done it by selecting my "AllTests" class and then clicking Run>>Run JUnit Test . It was there on the menu so I never thought to look to see if it was also hiding somewhere else. Is there a way of putting one of these configured "launches" as something like a button on a menu bar, so I don't need to wade through Run>>Run... etc each time?
Aha! Eventually you've hammered it through my skull. I've added the Navigator to my Java Perspective and now I can see my phantom empty project (and remove it).
Can you have a stab at explaining what it is about a project that makes it a "Java" project, rather than just a collection of files, some of which are Java files?
You can help to fill this gap by documenting your problems and their solutions at the Eclipse Wiki, though.
OK, I guess I deserved that. I'll try and put something together ...
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Originally posted by Craig Demyanovich:
I still find it confusing, though, that the Package Explorer (not the Navigator, as I said earlier) shows the following structure:
Why is src shown as a plain folder in addition to the two representations above it? What purpose does it serve, since it seems useless to have it?
Many thanks for sharing your thoughts throughout this thread.
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
pie. tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
https://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton
|