You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Arjohn Kampman (JIRA)" <ji...@codehaus.org> on 2007/05/03 14:39:26 UTC
[jira] Created: (MASSEMBLY-209) Service provider configuration
files should be concatenated instead of overwritten
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.2-beta-1, 2.1
Reporter: Arjohn Kampman
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
[jira] Commented: (MASSEMBLY-209) Service provider configuration
files should be concatenated instead of overwritten
Posted by "Paudi Moriarty (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_117045 ]
Paudi Moriarty commented on MASSEMBLY-209:
------------------------------------------
This is also an issue for Spring Framework META-INF files (spring.handlers, spring.schemas)
> 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
>
>
> 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
[jira] Updated: (MASSEMBLY-209) Service provider configuration
files should be concatenated instead of overwritten
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Casey updated MASSEMBLY-209:
---------------------------------
Fix Version/s: 2.2-beta-2
> 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-2
>
>
> 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
[jira] Updated: (MASSEMBLY-209) Service provider configuration
files should be concatenated instead of overwritten
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ 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-beta-2)
2.2
> 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
>
>
> 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
[jira] Closed: (MASSEMBLY-209) Service provider configuration files
should be concatenated instead of overwritten
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Casey closed MASSEMBLY-209.
--------------------------------
Resolution: Fixed
Assignee: John Casey
use container descriptor handler 'metaInf-services' to enable this.
> 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
> Assignee: John Casey
> Fix For: 2.2-beta-6
>
>
> 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
[jira] Updated: (MASSEMBLY-209) Service provider configuration
files should be concatenated instead of overwritten
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (MASSEMBLY-209) Service provider configuration
files should be concatenated instead of overwritten
Posted by "Johan Walles (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=169852#action_169852 ]
Johan Walles commented on MASSEMBLY-209:
----------------------------------------
Affects 2.2-beta-2 as well.
> 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
>
>
> 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