[
https://issues.apache.org/jira/browse/MINSTALL-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17852117#comment-17852117
]
Tamas Cservenak commented on MINSTALL-200:
------------------------------------------
Direct mojo invocation like {{jar:jar}} instructs Maven "do create a JAR for
the project", and Maven obeys (creates empty JAR with Maven metadata only as
there are no classes). If using lifecycle (ie. invoking {{{}package{}}}), it
would _not been invoked_ as packaging=pom does not use JAR plugin at all.
Basically by direct mojo invocations you are circumventing the lifecycle (and
packaging) of Maven. That is another problem (see related MNG issues) that
Maven allows doing this, and will end up in "inconsistent internal state"
(Maven Project of packaging POM will have JAR attached as main JAR, replacing
the POM artifact). But again, user instructed Maven to do so, by invoking
{{jar:jar}} on a module, that would otherwise never invoke this goal as part of
lifecycle.
> "mvn jar:jar install:install" installs a jar instead of a pom
> -------------------------------------------------------------
>
> Key: MINSTALL-200
> URL: https://issues.apache.org/jira/browse/MINSTALL-200
> Project: Maven Install Plugin
> Issue Type: Bug
> Components: install:install
> Affects Versions: 3.1.2
> Reporter: Urs Keller
> Priority: Minor
>
> {code:java}
> <?xml version="1.0" encoding="UTF-8"?>
> <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
> https://maven.apache.org/xsd/maven-4.0.0.xsd">
> <modelVersion>4.0.0</modelVersion>
> <groupId>com.example</groupId>
> <artifactId>test-project-parent</artifactId>
> <version>main-SNAPSHOT</version>
> <packaging>pom</packaging>
> <build>
> <pluginManagement>
> <plugins>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-install-plugin</artifactId>
> <version>3.1.2</version>
> </plugin>
> </plugins>
> </pluginManagement>
> </build>
> </project>
> {code}
> {code:java}
> $ rm -rf ~/.m2/repository/com/example/test-project-parent
> $ mvn jar:jar install:install
> $ file ~/.m2/repository/com/example/test-project-parent/main-SNAPSHOT/*
> .../test-project-parent-main-SNAPSHOT.pom: Zip archive data, at least v1.0 to
> extract, compression method=store
>
> {code}
> The behaviour is different in 3.1.1 where this command will install the pom.
> The output looks like this:
> {code:java}
> .../test-project-parent-main-SNAPSHOT.pom: XML 1.0 document text, ASCII text
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)