[
http://jira.codehaus.org/browse/MASSEMBLY-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Casey updated MASSEMBLY-209:
---------------------------------
Fix Version/s: (was: 2.2)
2.2-beta-5
> Service provider configuration files should be concatenated instead of
> overwritten
> ----------------------------------------------------------------------------------
>
> Key: MASSEMBLY-209
> URL: http://jira.codehaus.org/browse/MASSEMBLY-209
> Project: Maven 2.x Assembly Plugin
> Issue Type: Improvement
> Affects Versions: 2.1, 2.2-beta-1
> Reporter: Arjohn Kampman
> Fix For: 2.2-beta-5
>
>
> Service provider configuration files are text files that define what "service
> providers" are available for a specific interface. These files are normally
> stored in /META-INF/services/ and are named after the interface that is
> implemented (e.g. "java.io.spi.CharCodec"). See for more info:
> http://java.sun.com/j2se/1.5.0/docs/guide/jar/jar.html#Service%20Provider
> and
> http://java.sun.com/javase/6/docs/api/java/util/ServiceLoader.html
> Building a onejar from a multi-module project where multiple modules have
> similarly named services files results in a jar-file that includes just one
> of the service files. As a result, just the providers that are mentioned in
> that file are seen by applications running from the onejar, providers that
> were mentioned in the other service files are not. To fix this, service files
> with identical names should simply be concatenated (making sure that there's
> a newline between the contents of each service file).
--
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
