Summary: | can't get assert to work with mac os x java 1.4.1 | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Hal Perkins <hal> | ||||||
Component: | Core | Assignee: | JDT-Core-Inbox <jdt-core-inbox> | ||||||
Status: | RESOLVED INVALID | QA Contact: | |||||||
Severity: | normal | ||||||||
Priority: | P3 | CC: | Olivier_Thomann | ||||||
Version: | 2.1 | ||||||||
Target Milestone: | 2.1 RC3 | ||||||||
Hardware: | Macintosh | ||||||||
OS: | Mac OS X - Carbon (unsup.) | ||||||||
Whiteboard: | |||||||||
Attachments: |
|
Description
Hal Perkins
2003-03-11 02:07:46 EST
Could you please attach the .java file and the .class file corresponding to the class that has the assert statements? Also which JRE are you using at runtime? Could you please paste in the command line used to run your program: in the Debug view, select the javaw.exe process, bring up the properties, and copy the command line info. Are you enabling assertions with -ea on runtime? Created attachment 4003 [details]
source file AssertTest.java
Here's the source file. I'll attach the .class file next.
I'm afraid I'm a very new eclipse user - trying to learn my way around for
possible use in the courses I teach at University of Washington. I tried
running this from inside eclipse, so there are no command line arguments and I
can't find anything about javaw in the debug view. The Debug pane reports that
it is running
/System/Library/Frameworks/Java.VM.framework/Versions/1.4.1/Home/bin/java.
I'm hoping that it will eventually be simple to configure asserts with some
combination of simple options from within the environment. Suggestions
appreciated. Thanks.
Created attachment 4004 [details]
compiled version of test file
Found the run arguments panel and adding -ea to the vm arguments got the asserts to work. Please close this one out. Sorry for the trouble. Hal This should be closed as INVALID. FIXED means that an action has been taken to fix the problem which is not the case here. This wasn't a problem with Eclipse, but rather a problem with the configuration of the launching configuration. |