J-HowHuang opened a new issue, #1575:
URL: https://github.com/apache/maven-dependency-plugin/issues/1575

   ### Affected version
   
   3.9.0
   
   ### Bug description
   
   The `pom.xml` is configured where `assembly-descriptor` is a sub-module and 
is also a dependency of one of the plugin `maven-assembly-plugin`.
   
   ```
     <modules>
       ...
       <module>assembly-descriptor</module>
       <module>pinot-metrics</module>
     </modules>
   
     <profiles>
       <profile>
         <id>plugin-assembly</id>
         <activation>
           <file>
             <exists>src/main/resources/pinot-plugin.properties</exists>
           </file>
         </activation>
         <build>
           <plugins>
             <plugin>
               <groupId>org.apache.maven.plugins</groupId>
               <artifactId>maven-assembly-plugin</artifactId>
               <dependencies>
                 <dependency>
                   <groupId>org.apache.pinot</groupId>
                   <artifactId>assembly-descriptor</artifactId>
                   <version>${project.version}</version>
                 </dependency>
               </dependencies>
               ...
             </plugin>
           </plugins>
         </build>
       </profile>
   ```
   
   Now there's another sub-module `pinot-dropwizard` in `pinot-metrics` that 
depends on the plugin `maven-assembly-plugin`, it results in:
   
   ```
   [ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-dependency-plugin:3.9.0:go-offline (default-cli) 
on project pinot-dropwizard: The following artifacts could not be resolved: 
org.apache.pinot:assembly-descriptor:jar:1.5.0-SNAPSHOT (absent): Could not 
find artifact org.apache.pinot:assembly-descriptor:jar:1.5.0-SNAPSHOT -> [Help 
1]
   ```
   
   It was not an issue before `3.9.0`.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to