maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephane Nicoll (JIRA)" <>
Subject [jira] Commented: (MASSEMBLY-210) repository does not include the parent pom
Date Fri, 01 Jun 2007 09:03:59 GMT


Stephane Nicoll commented on MASSEMBLY-210:

I have this with the current build of the plugin. (mvn 2.0.6)

[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Internal error in the plugin manager executing goal 'org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-2-SNAPSHOT:attached':
Unable to find the mojo 'org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-2-SNAPSHOT:attached'
in the plugin 'org.apache.maven.plugins:maven-assembly-plugin'
Component descriptor cannot be found in the component repository: org.apache.maven.artifact.factory.ArtifactFactorydefault.

> repository does not include the parent pom
> ------------------------------------------
>                 Key: MASSEMBLY-210
>                 URL:
>             Project: Maven 2.x Assembly Plugin
>          Issue Type: Bug
>    Affects Versions: 2.2-beta-1
>            Reporter: Stephane Nicoll
>            Assignee: John Casey
>             Fix For: 2.2-beta-2
> I am running the assembly on a project with a parent pom. <?xml version="1.0" encoding="ISO-8859-15"?>
<assembly> <id>dist</id> <formats> <format>zip</format>
</formats> <includeBaseDirectory>true</includeBaseDirectory> <baseDirectory>foo-${version}</baseDirectory>
<fileSets> <fileSet> <directory>.</directory> <outputDirectory>foo-base</outputDirectory>
<useDefaultExcludes>true</useDefaultExcludes> <excludes> <exclude>*/target/*</exclude>
</excludes> </fileSet> </fileSets> <repositories> <repository>
<outputDirectory>repository</outputDirectory> <scope>test</scope>
</repository> </repositories> </assembly> 
> The parent pom is not included at all.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message