Community
Participate
Working Groups
JUnit/Plug-in tests do not allow default package names. JUnit/Plug-in test wizards do not force the user to specify a package name. When the user creates a JUnit/Plug-in test with a default package (e.g. empty value), the test class generator displays an error that the package a cannot be empty. This is a problem for several reasons: 1) It is a regression since users were permitted to use the default package in previous versions. 2) JDT permits classes to be created in the default package. 3) Users may want to use the default package. 4) The JUnit/Plug-in test wizard allows the user to specify the default package (e.g. empty value) (the user is only warned that the default package is discouraged).
*** This bug has been marked as a duplicate of 160970 ***
ACTION: Please verify/close this defect.
Reporter: Please verify and close in preparation for shutting down the TPTP 4.4 release. Thanks.
Closing by default since not verified/closed by the originator in the 6+ months since being resolved. Please reopen if the issue is still present in the latest TPTP release or the resolution is not correct.
