International Business Machines Corporation

Nathan Victor Bak

Timothy C Pepper

Ramachandra N Pai

Eric Benjamin Munson

Patricia A Gaughen

Gerrit Huizenga

Avantika R Mathur

Dale M Schultz

Jon A Grimm

Donjuma S Lee

David K Olsen

Ramanchandra N Pai

Huizenga Gerrit

The disclosed herein related to image patching in an integrated development environment executed. To image patch, a first image produced by a latest build is pulled into the integrated development environment and a build snapshot produced by the latest build is acquired from the first image. A comparison is made between the build snapshot and contents of a current workspace of the integrated development environment to determine changed contents. A layer containing the changed contents is patched into the first image to generate a second image.

Image patching in an integrated development environment

Software product build information is bi-directionally linked. At least a first build instance of the software product is built and the first build instance is published by a supplier build repository. Responsive to an entity who is not the supplier indicating a use of the first build instance in a client product, build information relating to the use of the first build instance in the client product is received. The build information relating to the use of the first build instance in the client product is published by the supplier build repository.

Bi-directional linking of product build information

A method, system and computer program product for software debugging using annotation metadata. A set of metadata comprising source code annotation information for a software program is maintained, together with data/metadata relationships between individual units of the metadata and individual units of the source code. A software debugging point is set that is associated with debugging point metadata comprising one or more units the metadata. A debugging action is performed when execution of the software program reaches said debugging point.

Metadata-integrated debugger

A software development service offering of generating and installing software applications packages on computer systems running a set of operating systems including LINUX and UNIX operating systems, by creating a dynamic repository; populating a plurality software packages; running a tool that creates a set of index files, wherein the set of index files includes a menu of the plurality of software packages, wherein each software package in the plurality of software packages contains a set of contents; determining whether a software package is included in a menu of the plurality of software packages; and delivering to a client system the software package requested in a selection request, or delivering to the client system an other software package, when the software package is not included in the menu of the plurality of software packages.

Methods, systems and computer products for a dynamic repository

A computer system, program, or method may provide for quantifying changes in an individual component among a plurality of components in a software development environment where the components are incorporated in a build. This may include calculating a baseline weight of the individual component prior to a change; effecting, in the software development environment, the change to the individual component; calculating a modified weight of the individual component after the change; determining a threshold for a difference between the baseline weight and the modified weight of the individual component; calculating the difference between the baseline weight and the modified weight of the individual component; and providing on the software development computer a notification if the difference exceeds the threshold. The weights of the individual component may use data such as a count of other components required by the individual component, an install size, a runtime memory usage, a depth of a dependency tree, a component license type, a component category for memory location, a component code type, and/or other types of data.

Comparing component weights between builds

Methods, systems, and computer program products may provide pre-merge conflict avoidance in a revision-control system. A pre-merge conflict avoidance method may include identifying by a computer system a portion of interest of a revision-controlled base source code stored in a source-code repository, the base source code being developed by a plurality of developers. The computer system may determine whether at least one of the plurality of developers has made a change to a portion of a first copy of the base source code corresponding to the portion of interest prior to commitment of the first copy of the base source code to the source-code repository. In response to a determination that the at least one developer has made a change to the portion of interest, a notification may be produced about the change to the portion of interest by the at least one developer.

Pre-merge conflict avoidance

A method, apparatus, and article are provided for managing migration of annotations between versions of source code. Annotations associated with patterns of source code are identified. A comparison of the modified source code is conducted in conjunction with the identified annotations in a prior version of the source code to determine if the annotations may be migrated to any portions of the modified source code. The comparison includes an exact match and a partial match. With respect to the partial match, a threshold value is employed to define the parameters of a partial match. All annotations that are determine to be an exact match or a partial match are automatically migrated to a location in the modified source code determine to match within the threshold value.

Transferring annotations across versions of the data

A computer program is pseudo translated within an integrated development environment (IDE). Pseudo translation is performed, within an IDE, on one or more first resource files for the computer program, to generate corresponding one or more second resource files, without modifying one or more source code files for the computer program. The computer program is debugged and/or run, within the IDE, using the second resource files, such that the second resource files remain hidden from a user of the IDE, and without changing the user interface language of the computerized system.

Pseudo translation within integrated development environment

Embodiments of the invention provide for adjusting authentication conditions in real-time. A graph-theoretic data structure is dynamically constructing, having nodes corresponding to received valid and invalid authentication credentials used in attempts to access a system. Based on the graph-theoretic data structure, embodiments compute a probability of an invalid credential being an authentication attempt by a particular type of user. If the probability is beyond a threshold probability, embodiments trigger a security event is to adjust an authentication condition of the system, e.g., to increase or decrease a maximum permissible number of failed login attempts within a certain period of time.

Real-time adjustments to authentication conditions

A method, apparatus, and article of manufacture to dynamically address and resolve an improper shut-down of an application. Internal state data of the application is stored in persistent memory. New internal state data is dynamically created and authenticated following an improper shut-down of the application. Responsive to the authentication, the application is re-started with the authenticated new internal state data, without being subject to an immediate improper shut-down.

Application failure recovery

A machine implemented technique for performing dynamic globalization verification testing in a software user interface includes identifying one or more user interface controls in the software user interface having text strings that have been pseudo translated, generating one or more applicable test cases that test for display defects stemming from the pseudo translations, executing the test cases, and logging defects.

Growing community of inventors

Portland, OR, United States of America

Nathan Victor Bak