Clarify the addition of dependancies in assembly:assembly
---------------------------------------------------------

                 Key: MASSEMBLY-135
                 URL: http://jira.codehaus.org/browse/MASSEMBLY-135
             Project: Maven 2.x Assembly Plugin
          Issue Type: Improvement
    Affects Versions: 2.1
         Environment: n/a
            Reporter: Gwyn Evans


It was unclear to me for quite a while that the assembly plugin could pack 
dependancies  The documentation suggested that it should, by default, do so, 
but when trying wth the built-in "bin" descriptor, nothing happened.  I worked 
around it for a while by having the dependancy plugin copy the jars into my 
target folder, until I came back to it today.

What I found was that if I took the built-in 'bin', created my own[1] and 
simply added

    <dependencySets>
        <dependencySet>
        </dependencySet>
    </dependencySets>

then I got the behaviour I wanted.  

I'd suggest two changes - (1) some comment (in the descriptor format 
description) about how dependancies are not included without the above and (2) 
an additional pre-defined descriptior, e.g. "bin-with-dependancies", as that 
seems to be a common requirement, judging from the M2 mailing list.

/Gwyn

[1]  By the way, I couldn't find any documentation that explained the correct 
syntax for this - 
http://maven.apache.org/plugins/maven-assembly-plugin/howto.html just uses 
<descriptor> & 
http://maven.apache.org/plugins/maven-assembly-plugin/assembly-mojo.html 
mentions <descriptors> be only by trial & error do you find what it should 
contain (OK, convention suggests it would <descriptor>, but the description 
said files, which I first read as the filepath & <descriptor> was marked as 
depreciated. )

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