Skip to main content

nsx-prime


2023.1.7 (2023-09-18)

Fixed

  • Fixed NsxPrimeInstaller to once again allow overwriting of files.

2023.1.6 (2023-09-18)

Fixed

  • Updated to nsx-runtime version 2023.8.1 to repackage API changes.

2023.1.5 (2023-09-06)

Fixed

  • Replaced use of deprecated DirUtil.copyFile() method.

2023.1.4 (2023-06-30)

Fixed

  • Replaced FolderDeleter with more stable implementation.

2023.1.3 (2023-06-07)

Fixed

  • Delete expansions directory in one walk operation.

2023.1.2 (2023-06-01)

Fixed

  • SCM information was filtered by flatten-maven-plugin

2023.1.1 (2023-06-01)

Added

  • Added SCM information to deployed pom.xml artifact

2023.1.0 (2023-05-11)

Changed

  • Bumped version to 2023.1.x because changing to expansion-resource-resolvers includes new dependencies/
  • Added missing nsx-shared-process dependency to heartless
  • Removed dependency on commons-lang3 and nsx-shared-owasp

2023.0.3 (2023-05-10)

Changed

  • Refactored FolderDeleter to use nio files
  • Updated expansion-resource-resolvers to 1.3.0 to remove dependencies on commons-io

2023.0.2 (2023-05-09)

Changed

  • Removed direct dependency on commons-io and common-cli, now uses nio Files instead

2023.0.1 (2023-05-09)

Fixed

  • Fixed NullPointerException in harvest with clean option if no application is used

Updated

  • Updated prime-core to v2023.2.3

2023.0.0 (2023-02-02)

Changed

  • Expand/Harvest tasks will now only refetch SNAPSHOTS if --update is provided

Updated

  • Updated prime-core to v2023.0.2

2022.0.2 (2022-11-07)

Fixed

  • Fixed NullPointerException with clean option if no application is used

2022.0.1 (2022-09-15)

Updated

  • Update expansion-resource-resolvers to 1.1.1 to fix an issue that caused it to fetch SNAPSHOT versions multiple times

2022.0.0 (2022-09-05)

Changed

  • Replaced builtin ResourceManagementFactory with expansion-resource-resolvers

Updated

  • Updated dependencies

2021.7.0 (2021-11-24)

Added

  • excluded metamodel-runtime from heartless packaging
    • heartless used out of the box by expanders-maven-plugin 2021.7.0+
    • prime-core and metamodel-runtime are now dynamically determined based on transitive expansion resource dependencies

2021.6.0 (2021-11-19)

Updated

  • Update prime-core 2021.5.12 -> 2021.6.3
  • Update metamodel-runtime 4.1.4 -> 4.1.9

2021.5.8 (2021-10-01)

Updated

  • Update prime-core 2021.5.10 -> 2021.5.12

2021.5.7 (2021-09-29)

Updated

  • Update prime-core 2021.5.9 -> 2021.5.10
  • Update metamodel-runtime 4.0.1 -> 4.1.4

2021.5.6 (2021-09-27)

Updated

  • Update prime-core 2021.5.8 -> 2021.5.9

2021.5.5 (2021-09-23)

Updated

  • Update prime-core 2021.5.6 -> 2021.5.8

2021.5.4 (2021-09-22)

Updated

  • Update prime-core 2021.5.5 -> 2021.5.6

2021.5.3 (2021-09-22)

Updated

  • Update prime-core 2021.5.4 -> 2021.5.5

2021.5.2 (2021-09-20)

Updated

  • Update prime-core 2021.5.2 -> 2021.5.4

2021.5.1 (2021-09-15)

Updated

  • Update metamodel-runtime 4.0.0 -> 4.0.1

2021.5.0 (2021-09-10)

Updated

  • Update prime-core 2021.4.2 -> 2021.5.1

2021.4.3 (2021-08-31)

Updated

  • Update prime-core 2021.4.1 -> 2021.4.2

2021.4.2 (2021-08-23)

Updated

  • Update prime-core 2021.4.0 -> 2021.4.1

2021.4.1 (2021-08-23)

  • Re-release, fixed some tests

2021.4.0 (2021-08-23)

Changed

  • Changed model loading to use the ModelLoader class of prime-core

Removed

  • Removed several classes that are no longer used:
    • ExpansionClassLoaderBuilder
    • ExpansionResourceDependencyValidator
    • TransitiveExpansionResourceResolver
    • ExpansionConfigLoader
    • ExpansionResourceFetcher
    • ApplicationLoader
    • ApplicationReader
    • BaseConfigLoader
    • DataLoader
    • ExpansionResourceLoader
    • NsfInstallationLoader
    • SettingDirectoriesLoader
    • ModelResourceExtractor

2021.3.1 (2021-07-15)

Updated

  • Updated prime-core 2021.3.0 -> 2021.3.1

2021.3.0 (2021-07-05)

Added

  • [experimental] NsxPrime no longer needs to be installed before expanding, instead NSX_PRIME_WORKING_DIRECTORY env var (e.g. 'target/nsx') can be defined
  • [experimental] Added heartless jar-with-dependencies packaging, but without prime-core

Changed

  • used elements/prime-core version is determined at runtime, not during nsx-prime's build (required for heartless prime-core swapping)

Updated

  • Updated prime-core 2021.2.2 -> 2021.3.0

2021.2.2 (2021-07-01)

Fixed

  • Provide better error message when elements version is outdated; fixed cases where caught exceptions were not propagated

2021.2.1 (2021-06-18)

Updated

  • Updated prime-core 2021.2.1 -> 2021.2.2

2021.2.0 (2021-06-15)

Updated

  • Updated prime-core 2021.1.0 -> 2021.2.1

Fixed

  • DataResource loading has been reworked to prevent issues with references across files. This removes the requirement to define the DataResource files in the correct order.

2021.1.1 (2021-04-30)

Fixed

  • Fixed issue where Application was being read before extensions were added.

2021.1.0 (2021-04-15)

Updated

  • Updated prime-core 2021.0.3 -> 2021.1.0
  • Updated metamodel-runtime 3.2.0 -> 3.7.0

2021.0.0 (2021-04-09)

Updated

  • Updated prime-core 2020.14.1 -> 2021.0.3

Added

  • Added .git and .gitignore as protected files when clean-expanding

Removed

  • Removed tasks AddOption, AddResource, SetAttribute (and ConfigTask)
    • the implementation didn't correctly handle particularities of the modified files
    • use model-manipulator instead
  • Removed tasks ListVersions (obsolete), ValidateXml (obsolete), Init (replaced by ns-init project)
  • Removed task CleanCache (use mvn clean instead)
  • Removed task GenerateMenu (now provided by Expanders 4.13.x, or by Prime Radiant 2021.1.0)
  • Dropped support for non-PROVIDED expander versions without explicit Expanders expansion-resource
    • add Expanders expansionResource explicitly
    • for legacy use expanders-maven-pluging:2020.18.0 and nsx-prime:2020.12.0
  • Dropped support for nsx-prime auto-supplying default-stack
    • add required expansionResources explicitly
    • for legacy, use expanders-maven-pluging:2020.18.0 and nsx-prime:2020.12.0
  • Dropped support for undocumented providing file name to --expander expansionGoal
  • [internal] Dropped support for NsfInstallation except for repositoriesDirectory
    • internal decoupling from NsfInstallation class

2020.12.0 (2020-12-02)

Updated

  • Updated prime-core 2020.13.2 -> 2020.14.1

2020.11.1 (2020-10-29)

Updated

  • Updated metamodel-runtime 3.1.0 -> 3.2.0

2020.11.0 (2020-10-29)

Updated

  • Updated prime-core 2020.12.1 -> 2020.13.2

2020.10.0 (2020-10-28)

Added

  • Call ModelExtensionLoader to register extensions before reading the models

Updated

  • Updated prime-core 2020.10.3 -> 2020.13.0
  • Updated metamodel-runtime 2.1.0 -> 3.1.0

2020.9.4 (2020-10-21)

Updated

  • Updated nsx-runtime 2020.9.0 -> 2020.11.1

2020.9.3 (2020-10-21)

Merged

  • Merged nsx-prime 2020.8.6

2020.9.2 (2020-10-12)

Fixed

  • Fixed issues where nsf update would not update the script files when using --version RELEASE or --version LATEST

2020.9.1 (2020-10-12)

Fixed

  • Set internal elements version to version of prime-core

Updated

  • prime-core.version 2020.10.0 -> 2020.10.3

2020.9.0 (2020-09-08)

Changed

  • This version of nsx-prime uses prime-core to deliver the elements and expansionControl classes

2020.8.6 (2020-09-29)

Updated

  • Updated nsx-parent 2019.5 -> 2020.9.1
  • Updated elements 2020.8.0 -> 2020.8.4, elements-ioxml 2020.9.4 -> 2020.9.6

2020.8.5 (2020-09-25)

Fixed

  • Fixed expansionResource version comparison not accepting valid SemVer versions
  • Warn when using non-SemVer versions in expansionResource dependencies

2020.8.4 (2020-09-08)

Updated

  • Updated nsx-runtime 2020.7.2 -> 2020.9.0

2020.8.3 (2020-09-07)

Removed

  • Removed obsolete SSL context preparation and JSON maven dependency

2020.8.2 (2020-08-20)

Updated

  • Patch update elements-ioxml 2020.9.0 -> 2020.9.4

2020.8.1 (2020-08-20)

Fixed

  • Updated nsx-runtime to v2020.7.2 to fix incorrect exit codes for CliParser

2020.8.0 (2020-07-07)

Removed

  • Removed support for * and latest versions when using nsx-prime internal maven invocation
  • Removed --latestVersions from nsx-prime install task
  • Removed prime-radiant updating from UpdateTask

2020.7.8 (2020-06-15)

Added

  • Added logging for final listing of expansion resources

2020.7.7 (2020-05-28)

Changed

  • Updated dependencies

Fixed

  • Fixed ExternalPrimeTaskRunner not being able to run from local maven repository

2020.5.0 (2020-03-26)

Changed

  • nsx-prime now targets Java 8

Fixed

  • fixed double-resource fetching and re-extraction

Removed

  • removed parallel maven invocation requesting
  • removed all resource version updating and fetching during extraction phase

2020.3.4 (2020-03-06)

Added

  • Expansion-resources will be validated and sorted based on their dependencies. If a dependency is outdated, nsx-prime will raise an issue
  • If a dependency is missing, it will be added

2020.1.0 (2020-01-22)

Removed

  • removed support for reading components from single files
    • <useComponentFile value="false"/> in expansionSettings.xml is now ignored