I did trace it down to a quirk in dependency graph resolution and
filtering and it was triggered when the original mail.jar started
showing up twice in the dependency tree of glassfish-common package,
since in the addition of being the optional dependency of
javax.mail.jar it was introduced also as test dependency somewhere in
grizzly (if memory serves me...). Both instances should have been
filtered out but it seems that two exclusion criteria applied to single
artifact managed to cancel each other...
In any case, I'll file P3 issue to track this and it will get fixed soon.
Thanks,
Snjezana
Sahoo wrote:
> I still two jars in fairly recent builds. Snjezana was investigating
> this, as it was a packaging issue.
>
> Sahoo
>
> Bill Shannon wrote:
>> Did you ever resolve this issue?
>>
>> Sahoo wrote on 9/7/09 4:05 AM:
>>
>>> I see both mail.jar and javax.mail.jar in modules/.
>>>
>>> Thanks,
>>> Sahoo
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>