-
Notifications
You must be signed in to change notification settings - Fork 8
/
pom.xml
84 lines (76 loc) · 3.7 KB
/
pom.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
<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/maven-v4_0_0.xsd">
<modelVersion>4.0.0</modelVersion>
<parent>
<groupId>org.technologybrewery</groupId>
<artifactId>parent</artifactId>
<version>10</version>
</parent>
<groupId>org.technologybrewery</groupId>
<artifactId>poetry-monorepo-dependency-plugin</artifactId>
<version>1.2.1-SNAPSHOT</version>
<packaging>habushu</packaging>
<name>Poetry Monorepo Dependency Plugin</name>
<description>
Poetry plugin facilitating the usage of more complex monorepo project structures by pinning version dependencies
when building and publishing archives with local path dependencies to other Poetry projects within the same
monorepo
</description>
<url>https://github.com/TechnologyBrewery/poetry-monorepo-dependency-plugin/</url>
<inceptionYear>2022</inceptionYear>
<licenses>
<license>
<name>MIT License</name>
<url>http://www.opensource.org/licenses/mit-license.php</url>
<distribution>repo</distribution>
</license>
</licenses>
<developers>
<developer>
<name>Eric Konieczny</name>
<email>ekoniec1@gmail.com</email>
<organization>Technology Brewery</organization>
<organizationUrl>https://github.com/TechnologyBrewery</organizationUrl>
</developer>
</developers>
<scm>
<connection>scm:git:ssh://git@github.com/TechnologyBrewery/poetry-monorepo-dependency-plugin.git</connection>
<developerConnection>scm:git:ssh://git@github.com/TechnologyBrewery/poetry-monorepo-dependency-plugin.git
</developerConnection>
<url>https://github.com/TechnologyBrewery/poetry-monorepo-dependency-plugin/</url>
<tag>HEAD</tag>
</scm>
<properties>
<version.habushu.plugin>2.16.1</version.habushu.plugin>
</properties>
<build>
<plugins>
<plugin>
<groupId>org.technologybrewery.habushu</groupId>
<artifactId>habushu-maven-plugin</artifactId>
<version>${version.habushu.plugin}</version>
<extensions>true</extensions>
<configuration>
<pythonVersion>3.11.9</pythonVersion>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<configuration>
<autoVersionSubmodules>true</autoVersionSubmodules>
<!-- 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] prepare release"
</preparationGoals>
<completionGoals>clean verify scm:checkin -Dmessage="[maven-release-plugin] prepare for next
development iteration"
</completionGoals>
<goals>deploy</goals>
</configuration>
</plugin>
</plugins>
</build>
</project>