[ 
http://jira.codehaus.org/browse/MASSEMBLY-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_121505
 ] 

David Hoffer commented on MASSEMBLY-109:
----------------------------------------

Hum, it seems I still have this (or similar) issue with 2.2-beta-1 running on 
2.0.8.

I have very simpile POM project with two modules.  My POM is configured as:

<plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-assembly-plugin</artifactId>
                <version>2.2-beta-1</version>
                <executions>
                    <execution>
                        <phase>package</phase>
                        <goals>
                            <goal>directory-inline</goal>
                            <goal>attached</goal>
                        </goals>
                    </execution>
                </executions>
                <configuration>
                    <descriptor>src/main/assembly/assembly-bin.xml</descriptor>
                </configuration>
            </plugin>


This is the error I get when I run 'clean install' goals.  For other projects 
prior to 2.0.8 and with 2.1 this worked just fine.


C:\svn\components\xrite-colorlib-project\trunk>mvn clean install
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO]   xrite-colorlib-project
[INFO]   xrite-colorlib-api
[INFO]   xrite-colorlib
WAGON_VERSION: 1.0-beta-2
[INFO] ------------------------------------------------------------------------
[INFO] Building xrite-colorlib-project
[INFO]    task-segment: [clean, install]
[INFO] ------------------------------------------------------------------------
[INFO] artifact org.apache.maven.plugins:maven-clean-plugin: checking for update
s from central
[INFO] artifact org.apache.maven.plugins:maven-compiler-plugin: checking for upd
ates from central
[INFO] artifact org.apache.maven.plugins:maven-site-plugin: checking for updates
 from central
[INFO] [clean:clean]
[INFO] Deleting directory C:\svn\components\xrite-colorlib-project\trunk\target
[INFO] [cobertura:clean {execution: default}]
[INFO] [cobertura:clean {execution: default}]
[INFO] [site:attach-descriptor]
[WARNING] DEPRECATED [descriptor]: Please use descriptors instead
[INFO] [assembly:directory-inline {execution: default}]
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error creating assembly: Artifact: com.xrite:xrite-colorlib:jar:1.28-SNAP
SHOT (included by module) does not have an artifact with a file. Please ensure t
he package phase is run before the assembly is generated.


>  Assembly task does not include deeper nested modules  
> -------------------------------------------------------
>
>                 Key: MASSEMBLY-109
>                 URL: http://jira.codehaus.org/browse/MASSEMBLY-109
>             Project: Maven 2.x Assembly Plugin
>          Issue Type: Bug
>    Affects Versions: 2.1
>         Environment: Linux, Sun jdk 5.0
>            Reporter: gunter zeilinger
>            Assignee: John Casey
>             Fix For: 2.2-beta-1
>
>         Attachments: assembly-modules-problem.tar.bz2, 
> scratch-assembly.tar.bz2
>
>
> If one of the modules of the root pom is itself a "pom" packaging project,  
> specifying
>   <moduleSets>
>     <moduleSet>
>       <binaries>
>         <outputDirectory>lib</outputDirectory>
>         <includeDependencies>true</includeDependencies>
>         <unpack>false</unpack>
>       </binaries>
>     </moduleSet>
>   </moduleSets>
> in the descriptor fails with 
> [INFO] Included module: dcm4che:dcm4che-tool:pom:1 does not have an artifact 
> with a file. Please ensure the package phase is run before the assembly is 
> generated.
> Excluding it by (e.g.)
>    <moduleSets>
>     <moduleSet>
>       <excludes>
>         <exclude>dcm4che:dcm4che-tool</exclude>
>       </excludes>
> :      
> excludes also the artifacts from its sub-modules.
> Also listing such deeper nested modules by its groupId:artifactId as 
> <includes> (e.g:)
>    <moduleSets>
>     <moduleSet>
>       <includes>
>         <include>dcm4che:dcm4che-tool-dcm2txt</include>
>         <include>dcm4che:dcm4che-tool-dcm2xml</include>
>         <include>dcm4che:dcm4che-tool-pdf2dcm</include>
>         <include>dcm4che:dcm4che-tool-xml2dcm</include>
> :
> does not help.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to