Sahoo wrote:
> Tim,
>
> Why have you added weld-integration as a dependency? Does ACC use it?
My understanding was that both dependencies could be needed, depending
on the app client, at runtime.
Ken, maybe I missed something? Is only the weld-osgi-module dependency
needed for the client side? Or are both?
- Tim
> If so, can you explain how you use the functionality provided by that
> module?
>
> Thanks,
> Sahoo
>
> Tim Quinn wrote:
>> Hi.
>>
>> The weld JARs need to be accessible to app clients at runtime. These
>> changes add the api and the implementation JARs to the runtime
>> dependencies.
>>
>> Thanks.
>>
>> - Tim
>>
>>
>> Diffs:
>>
>> Index: appclient/client/acc/pom.xml
>> ===================================================================
>> --- appclient/client/acc/pom.xml (revision 33410)
>> +++ appclient/client/acc/pom.xml (working copy)
>> @@ -485,7 +485,20 @@
>> <groupId>org.glassfish.persistence.cmp</groupId>
>> <artifactId>cmp-internal-api</artifactId>
>> <version>${project.version}</version>
>> -</dependency>
>> + </dependency>
>>
>> + <dependency>
>> + <scope>runtime</scope>
>> + <groupId>org.jboss.weld</groupId>
>> + <artifactId>weld-osgi-bundle</artifactId>
>> + </dependency>
>> +
>> + <dependency>
>> + <scope>runtime</scope>
>> + <groupId>org.glassfish.web</groupId>
>> + <artifactId>weld-integration</artifactId>
>> + <version>${project.version}</version>
>> + </dependency>
>> +
>> </dependencies>
>> </project>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>