expanders-maven-plugin
2022.5.0 (2022-11-07)
Added
- Added
update-expansion-settings
mojo. This updates the expansion-resources in the expansionSettings.xml to the latest released versions. If the option-DuseDependencies
is included, the dependencies in dependencyManagement will be used instead. - Added
set-expansion-resource
mojo. This updates a single expansion-resource to a specific version.
Updated
- Updated model-transmutations to 1.2.3
- Updated prime-core to 2022.10.6
2022.4.3 (2022-11-03)
- Re-release 2022.4.2
2022.4.0 (2022-10-05)
Updated
- Updated model-validations to 2.3.1
- Updated metamodel-runtime to 4.11.1
- Updated prime-core to 2022.9.0
2022.3.0 (2022-09-21)
Added
expansionResource
goal:
- Added
exclusions
parameter to exclude specific directories from being scanned
Updated
- Updated prime-core to 2022.8.0
2022.2.2 (2022-09-05)
Fixed
- Fixed
transmute-model
goal not correctly fetching the model-transmutations jar - Fixed
transmute-model
failing if no target folder is present
Updated
- Updated nsx-prime to 2022.0.0, fixing an issue that caused NullPointerExceptions when using clean expand with a custom program type
2022.2.1 (2022-08-31)
Updated
- Updated model-transmutations to v1.2.0 to support metamodel transmutations
2022.2.0 (2022-08-23)
Added
- Added
transmute-model
goal, to modify the model using model-transmutations
Changed
- Updated 3rd party dependencies:
- Libraries:
commons-io:commons-io
:2.6 -> 2.11.0
junit:junit
:4.13 -> 4.13.2
(test only)org.slf4j:slf4j-simple
:1.7.25 -> 1.7.36
- Libraries:
2022.1.6 (2022-05-25)
Updated
- Updated expansion-resource-development to v1.10.1 to fix an issue that cause
validate-data
2022.1.4 (2022-05-16)
Fixed
- Fixed error with a version conflict even if the expansionSettings were valid if a newer prime-core was added.
2022.1.2 (2022-04-27)
Changed
- Changed classPath resolution so that prime-core can support ClassPathDependencies instead of being a fat jar.
2022.1.0 (2022-04-26)
Added
- [NSX-300][VEGA-130] Added option to include class-path dependencies in
expansion-resource
goal. This option requires prime-core 2022.4.0 to work. Hence the build will fail if the prime-core dependency is older than that.
2022.0.1 (2022-04-06)
Fixed
- Fixed output interleaving with maven log
- [validate-model] Fixed incomplete output with option
printReport
- [validate-model] Fixed classloading issue
2022.0.0 (2022-04-05)
Added
- Added
validate-model
mojo, to validate the model using model-validations.
Fixed
- canceling expansion via ctrl+c now should terminate the underlying expansion process instead of only terminating the outer maven process
2021.7.0 (2021-11-24)
Changed
- switched to heartless nsx-prime
- prime-core and metamodel-runtime are now provided from expansionResource dependencies or expanders-maven-plugin dependencies (whichever is higher)
- nsx-prime is no longer installed/copied to the target directory
- instead, the jar in local maven repository is used directly
- [VEGA-181]
expansion-resource
mojo no longer requires explicit prime-core/elements-shared dependency
Updated
- prime-core 2021.6.3 -> 2021.7.0
- it is now also a direct dependency (instead of just a test dependency)
- nsx-prime 2021.6.0 -> 2021.7.0
- switched from jar-with-dependencies to explicitly excluding prime-core and metamodel-runtime (same as heartless)
- expansion-resource-development 1.8.1 -> 1.9.0
2021.6.0 (2021-11-19)
Updated
- nsx-prime 2021.5.8 -> 2021.6.0
- prime-core 2021.5.12 -> 2021.6.3
- metamodel-runtime 4.1.4 -> 4.1.9
2021.5.12 (2021-09-29)
Updated
- nsx-prime 2021.5.6 -> 2021.5.7
- prime-core 2021.5.9 -> 2021.5.10
- metamodel-runtime 4.0.1 -> 4.1.4
2021.5.9 (2021-09-23)
Fixed
- Fixed prime-core version not being resolved through transitive dependencies
Added
- Added output for dependency resolving
2021.5.6 (2021-09-20)
Added
- added
expansion.settings
user property forexpansionSettings
property of expand/harvest/... mojos
Updated
- nsx-prime 2021.5.1 -> 2021.5.2
- prime-core 2021.5.2 -> 2021.5.4
2021.5.0 (2021-08-23)
Added
- Added support for prime-core 2021.4.0
Changed
- Expansion-resources should now explicitly define a dependency on prime-core. This defines the minimum version of prime-core.
2021.3.1 (2021-06-18)
Updated
- updated nsx-prime 2021.2.0 -> 2021.2.1
- updated prime-core 2021.2.1 -> 2021.2.2
Fixed
- Fixed support for non-semver versions in expansion-resources
2021.3.0 (2021-06-15)
Updated
- updated nsx-prime 2021.1.1 -> 2021.2.0
- updated prime-core 2021.1.2 -> 2021.2.1
2021.2.0 (2021-06-04)
Removed
- Removed deprecated
net.democritus
groupId redeployment- Use
net.democritus.maven.plugins
only
- Use
2021.1.0 (2021-04-15)
Updated
- updated nsx-prime 2021.0.0 -> 2021.1.0
- updated prime-core 2020.13.2 -> 2021.1.2
2021.0.0 (2021-04-09)
Added
- Added ListDependencies mojo to list all ExpansionResources of an ExpansionResource project, ExpansionSettings, or an Expansion trace zip
Updated
- updated nsx-prime 2020.12.0 -> 2021.0.0
- updated nsx-runtime 2020.9.0 -> 2021.0.0
Removed
- removed support for Expanders <4.4.x (in line with changes in nsx-prime 2021.0.0)
- removed
expansion.debug.port
parameter (useexpansion.debug.address
instead) - migrated mojo
jacoco
toexpansion-validation-maven-plugin
2020.18.0 (2021-01-11)
Changed
debugPort
option is now replaced withdebugAddress
. This can be set to<port>
or<hostname>:<port>
(when working with java 9+).
2020.17.0 (2021-01-06)
Removed
- Removed distributionManagement relocation to new groupId
- this should address the issue of using wrong plugin groupId/version
2020.16.0 (2020-12-02)
Added
- Added support for description fields in ExpansionResource, Expander and AdditionalExpansionStep
Updated
- updated nsx-prime 2020.11.1 -> 2020.12.0
2020.14.0 (2020-10-28)
Added
- Added option
expansion.debug.port
to allow for debug during expansion
Updated
- updated nsx-prime 2020.9.4 -> 2020.10.0
2020.13.3 (2020-10-20)
Fixed
- Fixed expansionSettings, expandPom, pluginVersion, and mavenBuildDir parameters being read-only
2020.13.1 (2020-10-19)
Fixed
- Fixed expansionSettings loading changes to maintain compatibility with different nsx-prime versions
2020.13.0 (2020-10-16)
Changed
- groupId change
- expanders-maven-plugin now uses groupId
net.democritus.maven.plugins
- to ease the transition, we will continue to deploy under the old groupId for the time being
- expanders-maven-plugin now uses groupId
2020.12.1 (2020-10-12)
Fixed
- [expansion-resource] The generated elements version is now also based on any prime-core dependency in the project
2020.12.0 (2020-09-08)
Changed
- Uses nsx-prime 2020.9.x, which introduces prime-core
Fixed
- [expansion-resource] Fixed an issue where multiple versions of the same expansion-resource dependency would not be pruned before generating a new expansion-resource manifest
2020.11.3 (2020-10-09)
Updated
- Updated nsx-parent 2019.5 -> 2020.9.1
Fixed
- Fixed resolution throwing NullPointerException when expansionSettings file is missing
2020.11.0 (2020-09-08)
Added
- added
init-project
goal that generates apom-expand.xml
file for new nsx projects - added experimental
jacoco
goal to filter custom code in jacoco reports
Fixed
- different versions of the same expansion-resource are now filtered out of the dependencies when generating a manifest
2020.10.0 (2020-07-09)
- added
skipExpansion
support for skipping expand mojo (use-Dexpansion.skip=true
on command line) - added experimental
primeTask
for running arbitrary nsx-prime tasks
2020.9.0 (2020-06-15)
- nsx-prime is now invoked directly with java, instead of going through it's nsf.sh/nsf.bat scripts
- added sl4j to classpath when invoking nsx-prime
- running maven in debug mode now sets nsx-prime's logging to debug mode
- For expansionResource mojo:
- Fixed issues with transitive dependency where the dependency was set to "provided" in the original project
- filter out duplicate dependencies
2020.8.0 (2020-05-29)
- Added experimental nsfArgs to customize nsx-prime invocation
- Updated dependencies
- Fixed ExpansionResource mojo not using external maven to fetch artifacts
- Fixed edge-case where cmd.exe was somehow no in %PATH% by using %CompSpec% and %SystemRoot% instead
- Removed support for useInternalMaven (= maven invoker inside nsx-prime)
2020.6.0 (2020-04-14)
- Minimal required maven is 3.5.4
- Added useInternalMaven configuration to expand and harvest mojos to manage dependencies from maven plugin instead of nsx-prime
- has no effect on nsx-prime <2020.6.0
- Removed InstallMojo
2020.5.1 (2020-03-26)
- Updated to Java8 runtime
2020.3.5 (2020-03-06)
- Added validate-data mojo
2020.3.1 (2020-02-21)
- Expansion-resource mojo configuration and behavior is now more in sync with harvest & expand mojos.
2020.1.0 (2020-01-22)
- Added expansionResource mojo
2019.8.2 (2020-01-06)
- nsfInstallation versions are configurable
- maven settings.xml used by nsx-prime can be configured to be empty or custom
- fixed harvest mojo ignoring clean flag
- automatically set MAVEN_HOME to be used by nsx-prime
2019.8.0 (2019-12-06)
- Updated nsx-prime to 2019.8.0
- Added install mojo