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 72356 - Remote packs
Summary: Remote packs
Status: VERIFIED FIXED
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: issues@profiler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-07 16:56 UTC by ehucka
Modified: 2013-04-29 12:50 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
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 ehucka 2006-02-07 16:56:01 UTC 
I think remote packs could be more user friendly.
Installer of remote pack lets user to choose target JVM path and installation
path for remote pack.
It prepares some script which could be 'transparently' used instead of java
executable. 
The script would contain all settings about agentpath, port etc. configured by
some '.conf' file and it would pass all its arguments to java process:

$JAVA_HOME/bin/java $AGENTPATH $ARGUMENTS

A user would be only using e.g. $PROFILER/bin/profiler instead of
$JAVA_HOME/bin/java in command line starting his/her application.
Comment 1 ehucka 2006-06-29 17:31:18 UTC 
fixed, there is profile.bat/.sh
Comment 2 Alexander Kouznetsov 2007-03-16 14:45:51 UTC 
Verified. Manual steps should be adjusted also. See issue 98088.