[
https://jira.codehaus.org/browse/MASSEMBLY-628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=342575#comment-342575
]
Karl Heinz Marbaise edited comment on MASSEMBLY-628 at 3/7/14 12:38 PM:
------------------------------------------------------------------------
First the mentioned warning is not bogus it shows you exactly that something is
wrong in your build and should be changed, cause you are trying to attach a dir
as artifacts to your project which is not possible (If you like to add other
files to your project you might use
[build-helper-maven-plugin|http://mojo.codehaus.org/build-helper-maven-plugin/]).
The point is if you use
{code}
<formats>
<format>dir</format>
<format>tar.gz</format>
</formats>
{code}
maven-assembly-plugin can't fulfill your requirements which is expressed by the
given warning.
If you would have had created a separate execution block for
maven-assembly-plugin and a separate assembly-descriptor where you have changed
the configuration
{code}
<configuration>
...
<attach>false</attach>
</configuration>
...
<formats>
<format>dir</format>
</formats>
{code}
You won't get a warning and maven-assembly-plugin eased itself, cause you are
doing it the right way.
And that's the reason why this issue will be left closed and defined as {{Not A
Bug}}.
was (Author: khmarbaise):
First the mentioned warning is not bogues it shows you exactly that something
is wrong in your build and should be changed, cause you are trying to attach a
dir as artifacts to your project which is not possible (If you like to add
other files to your project you might use
[build-helper-maven-plugin|http://mojo.codehaus.org/build-helper-maven-plugin/]).
The point is if you use
{code}
<formats>
<format>dir</format>
<format>tar.gz</format>
</formats>
{code}
maven-assembly-plugin can't fulfill your requirements which is expressed by the
given warning.
If you would have had created a separate execution block for
maven-assembly-plugin and a separate assembly-descriptor where you have changed
the configuration
{code}
<configuration>
...
<attach>false</attach>
</configuration>
...
<formats>
<format>dir</format>
</formats>
{code}
You won't get a warning and maven-assembly-plugin eased itself, cause you are
doing it the right way.
And that's the reason why this issue will be left closed and defined as {{Not A
Bug}}.
> Bogus warning when assembling to a directory
> --------------------------------------------
>
> Key: MASSEMBLY-628
> URL: https://jira.codehaus.org/browse/MASSEMBLY-628
> Project: Maven 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 was sent by Atlassian JIRA
(v6.1.6#6162)
