This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 38508 - testServerExecutionCompatibility is broken
Summary: testServerExecutionCompatibility is broken
Status: CLOSED WONTFIX
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Infrastructure (show other bugs)
Version: 4.x
Hardware: All All
: P3 blocker (vote)
Assignee: Nam Nguyen
URL:
Keywords: TEST
Depends on:
Blocks:
 
Reported: 2004-01-07 17:03 UTC by pzajac
Modified: 2006-03-24 09:44 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
exception stacktrace (3.91 KB, text/plain)
2004-01-07 17:03 UTC, pzajac 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description pzajac 2004-01-07 17:03:05 UTC 
compatibility with nb35 is broken:
java.lang.ClassNotFoundException:
org.netbeans.modules.j2ee.impl.ServerOptions
Comment 1 pzajac 2004-01-07 17:03:26 UTC 
Created attachment 12766 [details]
exception stacktrace
Comment 2 Nam Nguyen 2004-02-27 08:11:30 UTC 
Will resolve in 4.0
Comment 3 pzajac 2004-03-08 17:00:57 UTC 
Nam,
why you has changed the target milestone to prome-D ?
Are you really sure that this issue will be solved in promo-D?  

Did you mean:
If compatibility of settings are broken between Nb35 and Nb36 the
settings will be compatible between nb35 and nb 40. 

IMHO it is nonsence.
Comment 4 Nam Nguyen 2004-03-08 17:47:11 UTC 
No I didn't means that.  It is just means that we will not fix it in
3.6 because we don't have enough time.  Whether we should fix it for
promoD remains to be decided.  I am not sure about relation b/w the
test case and upgrade situation, but from the studio side, I think
that the upgrade scenario would be from NB 3.5 directly to NB4.0.

Petr, I meant to delay the decision, but now that you bring this up,
lets discuss it further.

Do you think we should fix this with 3.6 too? Or do you tbink we don't
have fix this if the class it no longer used?  Is it responsibility of
the module to provide obsolete unsused class to avoid exception?  Or
the upgrade facility just need to catch and log exceptions silently? 
IMO, the latter is what should happen and we don't have to fix this.
Comment 5 Nam Nguyen 2004-03-30 01:03:29 UTC 
The ServerOptions class contains user choice of default appserver and
webserver instances.  Since plugin providing implementation instances
are no longer there and the actual use-case of lost info is
insignificant, close bug as WONTFIX.
Comment 6 pzajac 2004-05-05 10:48:43 UTC 
v