You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "John Casey (JIRA)" <ji...@codehaus.org> on 2007/03/28 19:06:29 UTC

[jira] Updated: (MASSEMBLY-112) project artifact included in dependencies

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

John Casey updated MASSEMBLY-112:
---------------------------------

    Fix Version/s:     (was: 2.2)
                   2.2-beta-1

> project artifact included in dependencies
> -----------------------------------------
>
>                 Key: MASSEMBLY-112
>                 URL: http://jira.codehaus.org/browse/MASSEMBLY-112
>             Project: Maven 2.x Assembly Plugin
>          Issue Type: Bug
>    Affects Versions: 2.1
>            Reporter: Martijn Dashorst
>         Assigned To: John Casey
>             Fix For: 2.2-beta-1
>
>         Attachments: foo.zip
>
>
> The dependency set for a war packaged project includes the final war file into the dependencies. There is no way to exclude it.
> The attached zip file shows a project which exibits this behavior.
> The final zip contains the following structure:
> foo/pom.xml
> foo/lib
> foo/lib/commons-logging-1.0.4.jar
> foo/lib/foo.war
> foo/src
> foo/src/assembly
> foo/src/assembly/bin.xml
> foo/src/main
> and several source files (left them out for brevity). Please note that the assembly includes the final war file in the lib directory, where it doesn't belong. Also note that the servlet api dependency is not included (see other issue).

-- 
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