This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 76754 - Generated jar file for a Java SE project that uses JPA has agent lib in Class-Path manifest
Summary: Generated jar file for a Java SE project that uses JPA has agent lib in Class...
Status: RESOLVED WONTFIX
Alias: None
Product: javaee
Classification: Unclassified
Component: Persistence (show other bugs)
Version: 5.x
Hardware: All All
: P4 blocker (vote)
Assignee: Andrei Badea
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-05-23 19:23 UTC by Sanjeeb Sahoo
Modified: 2008-07-22 00:18 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Sanjeeb Sahoo 2006-05-23 19:23:06 UTC 
The build target in my Java SE project that uses JPA generated a jar file with
following manifest entries:

Class-Path: lib/toplink-essentials.jar lib/toplink-essentials-agent.jar
Main-Class: pkg.Main

and suggested me to run the project using
java -jar dist/foo.jar

Why is the toplink-essentials-agent jar in Class-Path? VM will only use it if it
is used in -javaagent option. Having it in Class-Path manifest does not make sense.
Comment 1 Pavel Buzek 2006-08-28 23:53:00 UTC 
There is nothing special for toplink agent here, all jar files from all
libraries added to project are added to manifest. Toplink agent is part of the
toplink library bcs it's part of toplink and I did not want to create 2 libraries.

Maybe it is not intuitive, but I do not see anything harmful.
Comment 2 Dongmei Cao 2008-07-22 00:18:52 UTC 
See comments in desc2