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 104315 - build JNLP and Harness
Summary: build JNLP and Harness
Status: RESOLVED INVALID
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:
Blocks:
 
Reported: 2007-05-18 20:15 UTC by kiyut
Modified: 2007-05-23 18:32 UTC (History)
0 users

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 kiyut 2007-05-18 20:15:02 UTC 
During build JNLP for application build on top NB Platform, the harness
component need to be unselected or the build will fail. So everytime I need to
build JNLP I need to unselect the harness, after the build finish, I go back to
select the harness again
Comment 1 Jesse Glick 2007-05-22 19:23:09 UTC 
Leave it unselected. You very likely do not want the harness cluster to be
included in your application.
Comment 2 kiyut 2007-05-23 05:33:20 UTC 
Unfortunately, we need the harness cluster in our application because since our
application is built on top NB Platform, we would like to provide the one of the
platform benefits which is plugin mechanism.

By including platform harness we will allow third party developer to develop
plugins for our applications easily. They only need to attach our platform
(which is built on top NB Platform) regarding which version of NB IDE they use.
Without including harness in our app, it will become problem when they are using
Netbeans IDE version different with our. Since the harness will follow the
current Netbeans IDE harness. However, including our harness which is the
harness come from Netbeans IDE version we use, third party developer just need
to use the harness supplied by our app.

Or is there a ways to allow third party developer to develop plugins for our app
with different NB IDE version / harness, without supplying the harness ?

So I would like to propose, if the build stuff detect JNLP target, it
automatically disregard the harness component (either selected or not selected),
if build normal it will check whether the harness is selected (will be included)
 or not selected (not included) ?
Comment 3 Jesse Glick 2007-05-23 18:32:47 UTC 
You can develop against a platform with no harness. In fact, as of NB 5.5, the
default is to use the harness bundled with the IDE, rather than the target
platform's harness (if it even exists). Using a newer harness with an older
platform should not be a problem.