[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipselink-users] toplink-essentials-agent.jar for Eclipselink

The problem is not as simple as I had first thought ;)

toplink-essentials-agent.jar is fine except for the fact that its manifest
file contains "Class-Path: toplink-essentials.jar". Obviously I would need
to modify this manifest file to refer to the obfuscated JAR file instead, so
maybe having a separate file isn't of much help to me after all...

This makes me wonder why Toplink had a separate file to begin with...? I was
under the impression it was a self-contained JAR file.

Gili


cowwoc wrote:
> 
> Hi,
> 
> I'm wondering why EclipseLink doesn't distribute the instrumentation agent
> in a (minimalistic) separate JAR file like TopLink does with
> toplink-essentials-agent.jar
> 
> I am processing my application using Proguard and EclipseLink's monolithic
> JAR makes it difficult to process. I'd like Proguard to produce one JAR
> file for my application and one JAR file per agent (since you can't deploy
> more than one agent per JAR file). Obviously I'd prefer it if
> EclipseLink's distribution included this separate JAR file already. I look
> forward to your response.
> 
> Thank you,
> Gili 
> 

-- 
View this message in context: http://www.nabble.com/toplink-essentials-agent.jar-for-Eclipselink-tp19283298p19283372.html
Sent from the EclipseLink - Users mailing list archive at Nabble.com.