This is probably not a well-documented feature yet, as it's fairly new
and we've been working out the kinks. Container-descriptor handlers
aggregate content from things like components.xml, etc. in an
intelligent way, rather than allowing one jar's descriptor to overwrite
another's. The descriptor handlers are Plexus components, whose
role-hint is entered in the section you mention below. The assembly
plugin then looks up the specific handlers for use when it encounters
references to them in the assembly descriptor.
What is the specific error you're seeing?
Barrie Treloar wrote:
This IT is failing in my environment:
container-descriptors\custom-containerDescriptorHandler
I can't find any documentation to help work out what the following in
the assembly configuration means:
<containerDescriptorHandlers>
<containerDescriptorHandler>
<handlerName>file.txt</handlerName>
</containerDescriptorHandler>
</containerDescriptorHandlers>
Anyone else got this problem?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
