Get Your Dependencies: What They Are and How to Obtain Them

With your tracking in place, the next step is to gather all the software, tools, code, and access rights you will need to perform the upgrade. Having all dependencies ready and provisioned before starting development is crucial to avoid delays and interruptions.

This guide provides a checklist of the key dependencies you will need to acquire.

Checklist Item 1: The Quantexa Core Dependency Bundles

These bundles contain the core Quantexa product artifacts (libraries and other dependencies) required to build the project against the new versions.

Action: Obtain the dependency bundles for every version "hop" in your upgrade path. For example, an upgrade from v2.5 to v2.8 requires the bundles for v2.6, v2.7, and v2.8.

• How to Obtain: These bundles are not publicly downloadable. You must request them from your Quantexa contact. They will provide you with the necessary files.
  
  
• What to Do: Once received, upload the artifacts to your organization's repository management tool (e.g., Nexus, Artifactory). Ensure that both Maven and NPM artifacts are provisioned. The official documentation provides an example of how to upload to Nexus.
  
  
• Missing Dependencies: If you encounter issues with missing third-party dependencies during your build, it may be because your environment has no access to public repositories like Maven Central. The bundles are designed to be self-contained, so if you believe something is missing from the bundle itself, please raise a post in Quantexa Platform Support on the Community.

Checklist Item 2: Component-Specific Bundles (If Applicable)

If your solution uses certain Quantexa components like Data Packs, Decision Systems, or QPython, these have their own dependency bundles.

Action: Check if your "In Scope Tasks" list from your upgrade plan includes upgrades to these components. If so, you must also request the specific dependency bundles for the target versions of these components from your Quantexa contact.

Checklist Item 3: The Repository Tool

The Repository Tool is the primary mechanism for automating the code migration between versions in an incremental upgrade.

Action: Obtain the Repository Tool executable and the specific migration configuration files for every version "hop".

• How to Obtain: The tool and its configuration can be provided by your Quantexa contact. Further guidance can be found in the documentation: Download Repo-Tool.

Checklist Item 4: Project Example

project-example is Quantexa's reference implementation and an invaluable resource. It contains best-practice examples and shows how to correctly apply the migrations for each version. Having a local copy is highly recommended.

Action: Get access to the project-example Git repository and, if necessary, transfer a copy to your development environment.

• How to Obtain: Follow the guidance here to get access: Accessing project-example.

Checklist Item 5: Database Migration Scripts (If Applicable)

Platform upgrades may introduce database schema changes. For some database technologies (like Oracle), these migrations must be run manually.

Action: Discuss with your Quantexa Architect whether manual database migrations are required for your specific technology stack and target version. If they are, you must request the DDL (Data Definition Language) scripts from your Quantexa contact.

Checklist Item 6: People and Places (Environments & Access)

Software and code are only part of the equation. Ensure the team is fully enabled and the necessary environments are available.

Action: Confirm the following before development begins:

• Team Onboarding: Ensure all developers on the upgrade team have been fully onboarded.
  
  
• System Access: Verify that every team member has the required access to all necessary systems (e.g., Git repository, artifact repository, JIRA, development/test environments).
  
  
• Environment Availability: Confirm that the required development and testing environments have been provisioned and are available for the project. These non-production environments are critical for isolating the upgrade work.

With all these dependencies gathered and correctly placed, your team is now equipped with everything it needs to begin the hands-on development work.