Releasing version 1.0 of your solution

Getting ready

This is about creating the final artifacts for installation of your solution, and preparing your development environment for working on the next release (let's call it 1.1).

Create the Install Package for your codeless Application

This is simple enough and is fully documented in Deploying-codeless-applications. The quick steps relevant to the tutorial are shown below.

By default, the version will be set to 1.0.0, and this is usually what you want for your first release.

From the Application main page, use the Create Install Package command in the Actions menu to start the wizard.

Mostly clicking Next to get through the wizard, until you can set your application value:

Click next to continue, click Create Package.

After the package is created, you can download it.

This usually into your local machine's Downloads area.

If you unzip the package, you will find each type of definition object has its own .def file. This can be placed into source code control, or kept somewhere else as a backup.

Create the Install Package for your Coded Library

Assuming you have done Module 3 and have the Meal Order Library to distribute as well, you need to package that as well. Since you built this with command-line tools and other IDEs, you should be comfortable using that approach to package it as well.  This step ensures that you have the latest files (both definitions, and code) in one place, so that you can manage these with a Source Code Repository or any other means of handling files. It also allows you to resume development of a new version.

The maven Archetype generated your original pom.xml file for your project, and by default, the version was set to 1.0-SNAPSHOT. This is appropriate to use during development, but you will need to change this at least twice: once to set the packaged version to 1.0.0, and again to reset it to 1.1-SNAPSHOT to resume development of the new version. Let's walk through the steps:

1. Update the version in the pom.xml file.

   pom.xml snippet

       <groupId>com.example</groupId>
      <artifactId>meal-program-lib-all</artifactId>
      <version>1.0.0</version>
      <packaging>pom</packaging>

2. Create the Install Package, which which you can download as com.example.meal-program-lib-1.0-SNAPSHOT.zip. 
   
   

   Export and Package

   projects\meal-order-lib> mvn -Pexport package

3. In order to resume development, you could decide to update the version again so it shows up correctly in BMC Helix Innovation Studio.
   
   

   pom.xml snippet

       <groupId>com.example</groupId>
      <artifactId>meal-program-lib-all</artifactId>
      <version>1.1-SNAPSHOT</version>
      <packaging>pom</packaging>

   Now deploy it back to your BMC Helix Innovation Studio instance. The correct version should show up now in BMC Helix Innovation Studio.

   
   

What you Learned

• Codeless applications and libraries are versioned at the time of packaging, using BMC Helix Innovation Studio.
• Coded applications and libraries are also versioned at this time, by performing a manual adjustment to the POM.xml.
• In either case, the developer is responsible for tracking and managing the source files of the application.