Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 160052 - Update site build should be able to generate JNLP-enabled site
Summary: Update site build should be able to generate JNLP-enabled site
Status: RESOLVED DUPLICATE of bug 160059
Alias: None
Product: PDE
Classification: Eclipse Project
Component: Build (show other bugs)
Version: 3.2.1   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: pde-build-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-10-06 12:55 EDT by Denis Jouvin CLA
Modified: 2006-10-06 13:22 EDT (History)
0 users

See Also:

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 Denis Jouvin CLA 2006-10-06 12:55:49 EDT 
Currently the only method I know of to bulid a JNLP site is to use a custom 
JNLP feature including the target main feature of a feature-based product,
with the signed startup.jar and main JNLP file as feature root files.

The problem with this method are many, in addition to the fact that the main JNLP file has to be made by hand:
- when building the feature for multiple platforms, they are build in different 
separate folders that have to be "merged" in the actual site: although files
with the same names are normally identical, it is not very reassuring to have 
these file conflicts when merging..
- versionning of the main JNLP file has to be managed by hand..
- .. as well as the link to the main feature's own JNLP file, when a version changes
- it is very slow and redundant to build the same files n times
Comment 1 Denis Jouvin CLA 2006-10-06 13:22:36 EDT 

*** This bug has been marked as a duplicate of 160059 ***