persistence@glassfish.java.net

Re: A change in persistence-api does not update toplink-essentials.jar

From: Sahoo <sahoo_at_sun.com>
Date: Fri, 22 Jun 2007 02:13:31 +0530

Hi Marina,

Why can't this be accomplished by a simple <jar update=yes> Ant task? Is
it an issue to know the name of the toplink-essential.jar file in
persistence-api module?

Rebuilding entity-persistence module is an extra step, but I think
cutting down that additional step can avoid an inconsistent environment
that can result if one forgets to run that extra build step.

Thanks,
Sahoo
Marina Vatkina wrote:
> Hi Sahoo,
>
> Solving this problem can be tricky, because the build should be only
> updating an existing toplink-essentials.jar, but do not depend on its
> existence.
>
> Right now you need to rebuild toplink-essentials.jar to incorporate
> any changes from the persistence-api sources.
>
> thanks,
> -marina
>
> Sahoo wrote:
>> A 'maven build' in glassfish/persistence-api only updates javaee.jar;
>> it does not update toplink-essentials.jar. Is this not a bug?
>>
>> Thanks,
>> Sahoo