You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Arthur Naseef (JIRA)" <ji...@codehaus.org> on 2013/06/04 22:35:03 UTC
[jira] (MASSEMBLY-628) Bogus warning when assembling to a directory
[ https://jira.codehaus.org/browse/MASSEMBLY-628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=326190#comment-326190 ]
Arthur Naseef commented on MASSEMBLY-628:
-----------------------------------------
I would like to request that this bug be reopened. Getting in the habit of ignorig WARNING messages during the maven build process is a concern.
Looking at the code, I wonder if there's a way to know - at the point in the code that the warning is logged - the "base directory" for the archive and bypass the warning if the directory being "archived" is the base directory. My apologies if I misunderstand the code - I've only looked at it for about 30 minutes so far.
> Bogus warning when assembling to a directory
> --------------------------------------------
>
> Key: MASSEMBLY-628
> URL: https://jira.codehaus.org/browse/MASSEMBLY-628
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.3
> Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 12:31:09-0500)
> Maven home: c:\Users\visola\Downloads\springsource\apache-maven-3.0.3
> Java version: 1.6.0_32, vendor: Sun Microsystems Inc.
> Java home: c:\Program Files\Java\jdk1.6.0_32\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
> maven-assembly-plugin:2.3
> Reporter: Vinicius Isola
> Attachments: test.zip
>
>
> When adding a "dir" format to the assembly file, it will output a bogus warning like the following:
> [WARNING] Assembly file: c:\Users\visola\temp\test\target\test-1.0.0 is not a regular file (it may be a directory). It cannot be attached to the project build for installation or deployment.
> I think it is related to bug: http://jira.codehaus.org/browse/MASSEMBLY-289
> Attached is an example project that can reproduce the problem just running "mvn clean install"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira