Shane Hartman

Greenhorn
+ Follow
since May 29, 2003
Merit badge: grant badges
For More
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Shane Hartman

We have that setup now, and that is how we know the tests failed and who failed them becuase source control records the name of the developer. Where it has really gotten us is when a new method is added an not test case is built.
20 years ago
What is the best way to keep tests in sync, we have a development group of over 30 programmers and an off-shore arm. While we have been coming down hard on those who do not keep the tests up to date when they make changes, I wonder if their is a better way.
20 years ago
One of the reasons it has become so popular is becuase it is basically free, and provides almost all the functionality of the high dollar ide's like JBuilder. As for deploying to different J2EE servers, eclipse itself cannot do this but a plug-in called MyEclipse Workbench can. It cost $30, but it does provide alot of functionality. It can be found here: http://www.myeclipseide.com/
The reason it prints sample is because your if statement doesn't check for anything and allows the sample method to be processed. Try this..

public final class Test4 {
class Inner {
void test() {
if (Test4.this.flag == true) {
sample();
}
else {
System.out.println("The flag is false");
}
}
}
private boolean flag = false;
public void sample() {
System.out.println("Sample");
}

public Test4() {
(new Inner()).test();
}
public static void main(String args []) {
new Test4();
}
}
[ May 29, 2003: Message edited by: Shane Hartman ]