Abstract: Detecting configuration problems in an ECLIPSE-based software application can be detected. Such a method can begin with the receipt of a user-command to test a configuration of an ECLIPSE-based software application or with a detection of a feature addition/update when an auto-testing feature is enabled. Information about the available sites for the ECLIPSE-based application can then be obtained. Then, a list of software elements required to operate the ECLIPSE-based software application can be compiled. At least one data attribute can be extracted from the meta data of each software element in the compiled list. The extracted data attributes can then be analyzed. When the analysis identifies a configuration problem, the existence of the configuration problem can be validated.

Abstract: The present invention comprises utility capable of detecting various issues with plug-ins and fragments in Eclipse and Eclipse-based products. In order to find issues, the utility first seeks information about the sites available in the given product. Once the sites have been located, the utility seeks information about the plug-ins and fragments in each site that are expected to resolve in the product. Once the utility has determined what particular plug-ins and fragments are expected to resolve in each site, it parses both the text and XML manifest of each candidate plug-in and fragments in order to gather the following information: Once the above information of each candidate plug-in and fragment has been gathered, the utility analyzes the particular information in details and performs a series of tests to find whether the candidate plug-ins and fragments have issues.

Abstract: Detecting configuration problems in an ECLIPSE-based software application can be detected. Such a method can begin with the receipt of a user-command to test a configuration of an ECLIPSE-based software application or with a detection of a feature addition/update when an auto-testing feature is enabled. Information about the available sites for the ECLIPSE-based application can then be obtained. Then, a list of software elements required to operate the ECLIPSE-based software application can be compiled. At least one data attribute can be extracted from the meta data of each software element in the compiled list. The extracted data attributes can then be analyzed. When the analysis identifies a configuration problem, the existence of the configuration problem can be validated.

Abstract: The present invention discloses an automated method for detecting configuration problems in an ECLIPSE-based software application. Such a method can begin with the receipt of a user-command to test a configuration of an ECLIPSE-based software application or with a detection of a feature addition/update when an auto-testing feature is enabled. Information about the available sites for the ECLIPSE-based application can then be obtained. Then, a list of software elements required to operate the ECLIPSE-based software application can be compiled. At least one data attribute can be extracted from the meta data of each software element in the compiled list. The extracted data attributes can then be analyzed. When the analysis identifies a configuration problem, the existence of the configuration problem can be validated.

Abstract: The present invention discloses an automated method for detecting configuration problems in an ECLIPSE-based software application. Such a method can begin with the receipt of a user-command to test a configuration of an ECLIPSE-based software application or with a detection of a feature addition/update when an auto-testing feature is enabled. Information about the available sites for the ECLIPSE-based application can then be obtained. Then, a list of software elements required to operate the ECLIPSE-based software application can be compiled. At least one data attribute can be extracted from the meta data of each software element in the compiled list. The extracted data attributes can then be analyzed. When the analysis identifies a configuration problem, the existence of the configuration problem can be validated.

Abstract: The present invention comprises utility capable of detecting various issues with plug-ins and fragments in Eclipse and Eclipse-based products. In order to find issues, the utility first seeks information about the sites available in the given product. Once the sites have been located, the utility seeks information about the plug-ins and fragments in each site that are expected to resolve in the product. Once the utility has determined what particular plug-ins and fragments are expected to resolve in each site, it parses both the text and XML manifest of each candidate plug-in and fragments in order to gather the following information: Once the above information of each candidate plug-in and fragment has been gathered, the utility analyzes the particular information in details and performs a series of tests to find whether the candidate plug-ins and fragments have issues.