1.0.1

Version 1.0.1 of the CICS bundle Gradle plugin is now available.

Breaking changes

This release contains the following breaking change:

• #80 Change src/main/resources to src/main/bundleParts and allow config

  More details: Previously, non-Java-based CICS bundle parts such as programs or URI maps could be placed in src/main/resources to have them included into the bundle. This had a confusing effect when using the standalone project form, because these bundle parts were picked up by both the CICS bundle plugin and the Java plugin, so they ended up both inside the CICS bundle and inside the JAR/WAR/etc.

  Now, non-Java-based CICS bundle parts should be put in src/main/bundleParts, and they will only end up in the CICS bundle.

  You can also configure the location of this folder, relative to src/main:

  cicsBundle {
      build {
          bundlePartsDirectory = 'myBundleParts'
      }
  }

Fixes and chores

This release includes the following fixes:

• #83 Store password as char array
• #79 Update test projects to enable deployment to real CICS system
• #75 Rename web-app to webapp in samples

1.0.0

Version 1.0.0 of the CICS bundle Gradle plugin is now available.

New capabilities

The main new feature is the support for explicitly configured bundle parts (#63), allowing the override of the name or the JVM server to be used. For example:

dependencies {
    // Normal dependency with no overrides.
    cicsBundlePart 'org.codehaus.cargo:simple-ear:1.7.7@ear'

    // Override name and jvmserver of simple-bundle-1.7.7.
    cicsBundleOsgi {
        dependency = cicsBundle(group: 'org.codehaus.cargo', name: 'simple-bundle', version: '1.7.7', ext: 'jar')
        name = 'new-name'
        jvmserver = 'NEWJVMS'
    }

    // Override file extension of simple-war-1.7.7 so it is processed as an ear instead.
    cicsBundleEar(dependency: cicsBundle('org.codehaus.cargo:simple-war:1.7.7@war'))
}

Breaking changes

This release contains the following breaking change:

• #66 Rename cicsBundle configuration to cicsBundlePart

  More details: As part of a review of terminology before getting to this 1.0.0 release, we've renamed the cicsBundle configuration, which is used to define CICS bundle part dependencies, to cicsBundlePart. To deal with this, simply change the spelling in the dependencies section of your build.gradle:

    dependencies {
  -     cicsBundle 'org.codehaus.cargo:simple-ear:1.7.7@ear'
  +     cicsBundlePart 'org.codehaus.cargo:simple-ear:1.7.7@ear'
    }

Fixes and chores

This release includes the following fix:

• #65 Check contents of bundle part files 

v0.0.2

v0.0.2 is a minor new version of the CICS bundle Gradle plugin.

The main changes are:

• The CICS bundle Gradle plugin is now available from Maven Central, in addition to the Gradle Plugin Portal.
  You can consume the plugin from Maven Central instead of the Gradle Plugin Portal by configuring repositories in your settings.gradle as per the Gradle documentation:

  pluginManagement {
      repositories {
          mavenCentral()
      }
  }

• The samples are improved.

v0.0.1

v0.0.1 is our first release of the CICS bundle Gradle plugin, ID com.ibm.cics.bundle.

The CICS bundle Gradle plugin is available from the Gradle Plugin Portal.

This release comes with support for building a CICS bundle module, containing the following types of bundle part:

• EAR
• OSGi bundle
• WAR
• EBA
• EPADAPTER
• EPADAPTERSET
• EVENTBINDING
• FILE
• LIBRARY
• PACKAGESET
• POLICY
• PROGRAM
• TCPIPSERVICE
• TRANSACTION
• URIMAP

You can either have a separate module for the CICS bundle, or convert an existing Java-based module (for example, a JAR or WAR module) to also produce a CICS bundle.

See the README for more information.