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 64249 - [JNLP] don't add testing user to user home dir
Summary: [JNLP] don't add testing user to user home dir
Status: VERIFIED FIXED
Alias: None
Product: apisupport
Classification: Unclassified
Component: Harness (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: Jaroslav Tulach
URL:
Keywords:
Depends on: 64711
Blocks:
  Show dependency tree
 
Reported: 2005-09-13 14:23 UTC by pzajac
Modified: 2005-11-01 13:50 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 pzajac 2005-09-13 14:23:09 UTC 
The jnlp run creates userdit in user home dir. It is better to create it in 
build/jnlpuser folder of project.
Comment 1 Jesse Glick 2005-09-13 23:29:43 UTC 
No. The "Run" action on a suite tests the app in development mode, which uses a
testuserdir in the project. "Run JNLP" tries it out in actual deployment mode,
so it will work like it will work for a real user.
Comment 2 pzajac 2005-09-14 14:25:04 UTC 
IMHO it is not good idea. It is the same like you tests your code in 
$HOME/.netbeans/dev 
userdir before you commit into cvs.

Are you sure that it is correct? For Example you can work on new version of
application. So why to you the same workdir like it will work for real user.
Comment 3 Jesse Glick 2005-09-14 22:31:17 UTC 
"Run JNLP" is not for routine testing of the app as you develop it. Use "Run"
for that. "Run JNLP" is for final checking of JNLP packaging to make sure that
this step does not introduce any odd problems. "ant tryme" for NB developers is
akin to "Run"; "Run JNLP" would be something more like

ant build-nozip
ant -f installer/build.xml
sh installer/build/netbeans-dev

or something like that, which of course would use your default userdir location.

In the future we would like to actually have Run JNLP publish a WAR to a bundled
app server and launch javaws on the URL, which of course ought to behave
precisely as if you opened that URL in your web browser without the IDE - which
would use whatever userdir is considered default for the app.

Not sure how best to make this clear in the UI.
Comment 4 pzajac 2005-09-16 12:55:40 UTC 
Ok
Comment 5 Jesse Glick 2005-09-16 20:39:20 UTC 
Thought of a different idea.
Comment 6 Jesse Glick 2005-09-16 20:41:47 UTC 
Rather than changing the default JNLP userdir, build scripts now *remove* the
default JNLP userdir (with a one-level backup for safety) when cleaning the
suite. This should be enough to avoid clogging up your JNLP userdir with
obsolete settings - you just need to do a clean build.

committed   * Up-To-Date  1.15        harness/release/jnlp.xml
committed   * Up-To-Date  1.17        harness/release/suite.xml
Comment 7 pzajac 2005-11-01 13:50:01 UTC 
ok I agree, it is now much better