[jira] (MASSEMBLY-664) Using pom artifact as a dependency results in build failures

["Karl Heinz Marbaise (JIRA)" <ji...@codehaus.org>]

     [ https://jira.codehaus.org/browse/MASSEMBLY-664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Karl Heinz Marbaise closed MASSEMBLY-664.
-----------------------------------------

    Resolution: Cannot Reproduce

I have created a [sample project based on your pom|https://github.com/khmarbaise/massembly/tree/master/massembly-664] (I just used a different artifact as dependency with the packaging type pom) which results into the following message:
{code}
[INFO] --- maven-site-plugin:3.3:attach-descriptor (attach-descriptor) @ massembly-664 ---
[INFO] 
[INFO] --- maven-assembly-plugin:2.4:single (default) @ massembly-664 ---
[WARNING] Cannot include project artifact: com.soebes.test.assembly:massembly-664:pom:0.0.1-SNAPSHOT; it doesn't have an associated file or directory.
[INFO] Building jar: /Users/kama/ws-git/apache/massembly/massembly-664/target/massembly-664-0.0.1-SNAPSHOT-jar-with-dependencies.jar
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.955s
[INFO] Finished at: Sat Mar 08 15:08:01 CET 2014
[INFO] Final Memory: 16M/981M
[INFO] ------------------------------------------------------------------------
{code}
This looks like either your example pom is not equivalent to the original problem or i missed something. The things which looks different to me is the part {{single failed: For artifact {null:null:null:jar}: The groupId cannot be empty. -> [Help 1]}} which i can't reproduce.
So I will close this issue. If you have any objections or would like to change the example to get a better analysis to the problem you simple fork it on Github and send pull request for the example project so we can discuss the problem and of course we can reopen the issue.


> Using pom artifact as a dependency results in build failures
> ------------------------------------------------------------
>
>                 Key: MASSEMBLY-664
>                 URL: https://jira.codehaus.org/browse/MASSEMBLY-664
>             Project: Maven Assembly Plugin
>          Issue Type: Bug
>    Affects Versions: 2.4
>         Environment: Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 06:51:28-0700)
> Maven home: C:\gnu\maven
> Java version: 1.6.0_37, vendor: Sun Microsystems Inc.
> Java home: C:\Program Files (x86)\Java\jdk1.6.0_37\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "x86", family: "windows"
>            Reporter: Belai Beshah
>         Attachments: pom.xml
>
>
> A project with an artifact of <type>pom</type> dependency fails with the following error: 
> {noformat}
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:2.4:single (default) on project zip-error-sample: Execution default of goal org.apache.maven.plugins:maven-assembly-plugin:2.4:single failed: For artifact {null:null:null:jar}: The groupId cannot be empty. -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)