Bug 270412 - Webstart Export for multi-platforms should create one single archive with all fragments
Summary: Webstart Export for multi-platforms should create one single archive with all...
Status: NEW
Alias: None
Product: PDE
Classification: Eclipse Project
Component: Build (show other bugs)
Version: 3.5   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: pde-build-inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-30 03:36 EDT by Nicolas Richeton CLA
Modified: 2022-11-16 03:16 EST (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nicolas Richeton CLA 2009-03-30 03:36:02 EDT
When generating a webstart RCP application for multi-platform, Eclipse creates one folder or archive per platform, all using the same codebase url which makes the jnlp unusable without additional manual modification.  

2 possible fixes here : 
- Generate only one archive with fragments for all platforms. (best, in my opinion)
- Change the codebase url to include the platform name. eg : /linux.gtk.x86/  (easier to do, but will use up to 14x the size of the application on the host server). This would require some filtering mechanism like the one described in bug 270411
Comment 1 Nicolas Richeton CLA 2009-03-30 04:38:14 EDT
After further testing, the jnlp file for the RCP feature contains all necessary fragments. So the best would be to export every platform fragments to one single location.

Renaming bug to 'Webstart Export for multi-platforms should create one single archive with all fragments'.

 
Comment 2 Andrew Niefer CLA 2009-03-30 09:12:43 EDT
What happens if you set the property "groupConfigurations=true"
Comment 3 Nicolas Richeton CLA 2009-03-30 10:50:59 EDT
Hi Andrew,

I'm exporting from Feature Editor->Exporting->Export Wizard.
Where can I add this property ? 
Comment 4 Nicolas Richeton CLA 2009-03-30 12:29:20 EDT
Tried to add groupConfigurations=true to build.properties but the result is the same.
Comment 5 Andrew Niefer CLA 2009-03-30 13:04:59 EDT
groupConfigurations is set in the builder configuration, not in the feature or plug-in.  For export, this is internal to pde.ui and not something you have access to.

However, you can probably get it set by adding the property to the Ant Runtime Preferences.
Comment 6 Daniel Zuberbühler CLA 2009-08-21 10:14:06 EDT
I experience the same problem.
I tried adding the property groupConfigurations=true to the ant runtime preferences, but it didn't help, the result is the same.
Comment 7 Lars Vogel CLA 2018-12-03 09:10:31 EST
Currently we are not actively enhancing PDE build anymore. Therefore, I close this bug as WONTFIX. 

Please reopen, if you plan to provide a fix.
Comment 8 Lars Vogel CLA 2018-12-03 09:11:17 EST
Currently we are not actively enhancing PDE build anymore. Therefore, I close this bug as WONTFIX. 

Please reopen, if you plan to provide a fix.
Comment 9 Eclipse Genie CLA 2020-11-25 11:49:53 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 10 Eclipse Genie CLA 2022-11-16 03:16:58 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.