krausening-root
Used in:
components
- OverviewOverview
- VersionsVersions
- DependentsDependents
- DependenciesDependencies
<dependency>
<groupId>org.technologybrewery.krausening</groupId>
<artifactId>krausening-root</artifactId>
<version>21</version>
</dependency><project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<parent>
<groupId>org.technologybrewery</groupId>
<artifactId>parent</artifactId>
<version>14</version>
</parent>
<modelVersion>4.0.0</modelVersion>
<groupId>org.technologybrewery.krausening</groupId>
<artifactId>krausening-root</artifactId>
<version>21</version>
<packaging>pom</packaging>
<name>Krausening</name>
<description>Krausening is a library that allows for the externalization of property and configuration files from
deployment units, such as WARs, EARs, uber JARs, etc. By ensuring that property files are external to deployment
packages, these packages can be easily reused as-is to deploy to heterogeneous environments, circumventing
the need to hack apart or rebuild the package to support property file modification.
</description>
<url>https://github.com/TechnologyBrewery/krausening</url>
<licenses>
<license>
<name>MIT License</name>
<url>http://www.opensource.org/licenses/mit-license.php</url>
<distribution>repo</distribution>
</license>
</licenses>
<developers>
<developer>
<name>Ryan Ashcraft</name>
<email>dryanashcraft@gmail.com</email>
<organization>TechnologyBrewery.org</organization>
<organizationUrl>https://technologybrewery.org</organizationUrl>
</developer>
<developer>
<name>Eric Konieczny</name>
<email>ekoniec1@gmail.com</email>
<organization>TechnologyBrewery.org</organization>
<organizationUrl>https://technologybrewery.org</organizationUrl>
</developer>
</developers>
<scm>
<connection>scm:git:ssh://git@github.com/TechnologyBrewery/krausening.git</connection>
<developerConnection>scm:git:ssh://git@github.com/TechnologyBrewery/krausening.git</developerConnection>
<url>https://github.com/TechnologyBrewery/krausening</url>
<tag>krausening-root-21</tag>
</scm>
<modules>
<module>krausening</module>
<module>krausening-python</module>
</modules>
<build>
<pluginManagement>
<plugins>
<plugin>
<groupId>org.technologybrewery.habushu</groupId>
<artifactId>habushu-maven-plugin</artifactId>
<version>3.1.0</version>
<extensions>true</extensions>
</plugin>
</plugins>
</pluginManagement>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<configuration>
<autoVersionSubmodules>true</autoVersionSubmodules>
<releaseProfiles>central-release</releaseProfiles>
<!-- During release preparation, Habushu will automatically update the versions of Habushu modules
within their pyproject.toml configurations, however the maven-release-plugin will only commit
updates to pom.xml files. In order to version control both pom.xml and pyproject.toml files
that are updated during release preparation, customize the preparation and completion goals
to additionally execute the scm:checkin goals -->
<preparationGoals>clean verify scm:checkin -Dmessage="[maven-release-plugin] :bookmark: prepare release"</preparationGoals>
<completionGoals>clean verify scm:checkin -Dmessage="[maven-release-plugin] :bookmark: prepare for next development iteration"</completionGoals>
<goals>deploy</goals>
</configuration>
</plugin>
</plugins>
</build>
</project>