这应该能把戏:

<plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-release-plugin</artifactId>
    <version>2.3.2</version>
    <executions>
        <execution>
            <id>default</id>
            <goals>
                <goal>perform</goal>
            </goals>
            <configuration>
                <pomFileName>your_path/your_pom.xml</pomFileName>
            </configuration>
        </execution>
    </executions>
</plugin>

您可以用通常的的同样方式进行操作。 http://www. sonatype.com/book/mvnref-book/review/transing- section- particle- options.html#running- control- custom- place- options" rel=“ norefererr”> >tell Maven, 以便从位于其他地方 的POM运行: -f 选项。 mvn-help 如此描述:

-f,--file <arg>    Force the use of an alternate POM
                   file.

要在发布中做到这一点, 您只需要将合适的选项传递到发布插件 。 您可以使用 < a href=" http:// maven. apache. org/ plugins/ maven- release- plitin/ perform- mojo. html# arguments" rel= “ noreferrer” >perform target s “ arguments” 属性 来做到这一点。 此属性只是告诉发布插件一些附加参数, 以附加到发布时它运行的 < code> mvn 命令。 您可以在发布插件配置中附加 < code>- D参数=" - f path/to/pom " 或将其永久设置在 pom 中, 类似 。

<plugin>
    <artifactId>maven-release-plugin</artifactId>
    <version>2.3</version>
    <configuration>
        <arguments>-f path/to/pom</arguments>
    </configuration>
</plugin>

这个问题是在10多年前提出的,因此我想提供更最新的答案。

截至2022年10月,目前/现代马文在子目录中没有任何问题。maven插件的当前版本是。

• The <scm> element to point to the git repo (at top of repo, like you normally would). See Maven docs here, scm
• The <distributionManagement> element See Maven docs here, distributionManagement.

NOTE:也可以通过命令行通过这些参数,但我更希望将这些参数放入一个文件(pom.xml,为 ,或甚至设置.xml),以便更好地记录进程,使团队中的其他 deds更容易被部署。

NOTE:我在爪哇11中使用了3.8.5版马文版本,但AFAIK Java的版本并不重要。最新版本马文为3.8.6(此时此刻)。我相信这对爪哇8有效。此时,马文4在阿尔法。

How it works

Assumptions

在这一例子中,使用了以下方法:

• GitHub Repo: https://github.com/user123/proj456
• Apps: app1, app2, lib1, lib2
• NEXUS/Maven Repos: https://mynexus.example.com/repository/*

Each of the apps or libraries are in a separate directory with no parent POM being used (in this example). So you can t type mvn clean install from the top level directory. This is similar to the original OP question. As one commenter said, this is type of problem happens in a polyglot repo where multiple languages and technologies are used.

Explanation of POM configuration needed

在 lib1 中, pom 定义如下( 仅显示 Maven 发布插件的设置 ) 。 < nuger> NOTE: 这是此仓库的所有 POM 中将包含的 < em> SAME 信息 。

    <scm>
        <connection>scm:[email protected]:user123/proj456.git</connection>
        <developerConnection>scm:[email protected]:user123/proj456.git</developerConnection>
        <tag>HEAD</tag>
    </scm>
    <distributionManagement>
        <downloadUrl>https://mynexus.example.com/repository/maven-public</downloadUrl>
        <repository>
            <id>proj456-release</id>
            <name>proj456 release distro</name>
            <url>https://mynexus.example.com/repository/proj456-release</url>
        </repository>
        <snapshotRepository>
            <uniqueVersion>true</uniqueVersion>
            <id>proj456-snapshot</id>
            <name>proj456 snapshot</name>
            <url>https://mynexus.example.com/repository/proj456-snapshot</url>
        </snapshotRepository>
    </distributionManagement>

注意: 您的设置. xml 文件需要包含您的登录或指定证书, 以便看起来像 :

    <servers>
        <server>
            <id>proj456-releases</id>
            <username>user123</username>
            <password>not-shown</password>
        </server>
        <server>
            <id>proj456-snapshot</id>
            <username>user123</username>
            <password>not-shown</password>
        </server>
    </servers>

当您对您正在制作的每个maven 文物有单独的 git repo 时, 每一个标记的 < code@ lt; scm> 标记将有所不同 。

Creating a release

使用正常的 Maven 释放命令, 仅来自子目录 :

cd $HOME/work/proj456
ls -1
app1
app2
lib1
lib2

# Now CD to the directory you want to create a release for
cd lib1
mvn release:clean
mvn release:prepare release:perform

At the end of this process, the maven release plugin will do all the things it normally does. For example,

1. The -SNAPSHOT version in the POM is replaced with a release version (that you specify).
2. A git commit is created with the release version.
3. A maven build and package is created with that release.
4. The maven package is pushed (uploaded) to the NEXUS repo (or maven central).
5. The pom.xml is bumped to the next version (with -SNAPSHOT added) and git commit is made so future development occurs on next SNAPSHOT version.

See maven docs for maven release plugin for a complete list of the steps.

The first thing is to understand git which has it s convention that every project has it s own repository. The next thing is that Maven has it s conventions and putting the pom.xml into the root of it s project is the most obvious one. Furthermore you are trying to fight against Maven and i will predict that you will lose the combat and make your life not easy. If your projects A and B are related (same versio number or same release times) in some kind you should think about a multi-module build which results in a structure like this:

root (Git Repos)
  +-- pom.xml
       +--- projectA (pom.xml)
       +--- projectB (pom.xml)

并且您可以在根部的单步内发布项目A(更好地称它为模块)和模块b。