Bug 245782 - [product] creating products from OSGi launch configs
Summary: [product] creating products from OSGi launch configs
Status: RESOLVED FIXED
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.5   Edit
Hardware: PC Windows Vista
: P3 enhancement (vote)
Target Milestone: 3.5 M7   Edit
Assignee: Chris Aniszczyk CLA
QA Contact:
URL:
Whiteboard:
Keywords: noteworthy
: 219343 (view as bug list)
Depends on: 240737
Blocks:
  Show dependency tree
 
Reported: 2008-08-31 04:48 EDT by Jeff McAffer CLA
Modified: 2009-03-26 16:45 EDT (History)
2 users (show)

See Also:

Attachments
org.eclipse.pde.ui.patch (2.38 KB, patch)
2009-03-18 23:51 EDT, Chris Aniszczyk CLA 		no flags Details | Diff
org.eclipse.pde.ui.patch (11.01 KB, patch)
2009-03-19 12:12 EDT, Chris Aniszczyk CLA 		no flags Details | Diff
org.eclipse.pde.ui.patch (11.15 KB, patch)
2009-03-19 12:26 EDT, Chris Aniszczyk CLA 		no flags Details | Diff
org.eclipse.pde.ui.patch (11.15 KB, patch)
2009-03-19 12:27 EDT, Chris Aniszczyk CLA 		no flags Details | Diff
View All 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 Jeff McAffer CLA 2008-08-31 04:48:05 EDT 
There are several workflows that would benefit from the possibility of creating Product files from OSGi launch configs.  In addtion to simply getting the list of bundles, it would be interesting to look at how the start levels etc could be managed here.

This is likely part of the overall push to have PDE more consistent across Eclipse and OSGi usecases.
Comment 1 Benjamin Cabé CLA 2008-08-31 05:09:40 EDT 
(In reply to comment #0)
> There are several workflows that would benefit from the possibility of creating
> Product files from OSGi launch configs.  In addtion to simply getting the list
> of bundles, it would be interesting to look at how the start levels etc could
> be managed here.

Yes it would, indeed

> This is likely part of the overall push to have PDE more consistent across
> Eclipse and OSGi usecases.

Jeff, what is your opinion wrt bug 167438 ?
Comment 2 Jeff McAffer CLA 2008-08-31 11:35:55 EDT 
I am 100% for making PDE in to MDE (Module Development Environment).  It would be an extensible base into which various module mechanism could input tooling. There is much to be gained from using PDE in standard Java scenarios.  I believe we have a real opportunity here.  Now if you were suggesting more modest moves towards "bundle" tooling or BDE, that would be ok.  It would be great to see the barriers and differences between programming "Eclipse" and "Equinox" torn down or removed.
Comment 3 Chris Aniszczyk CLA 2008-09-02 11:25:21 EDT 
This will be possible when bug 240737 is completed. Currently, product files have no notions of start levels so this isn't going to help anyone really.
Comment 4 Chris Aniszczyk CLA 2009-03-10 13:56:16 EDT 
consider for M7
Comment 5 Chris Aniszczyk CLA 2009-03-18 23:51:36 EDT 
Created attachment 129318 [details]
org.eclipse.pde.ui.patch

Here's a patch that at least populates the list correctly.

We still have a problem in how we populate the plug-in list for product definitions. We have to know be aware of how to parse plug-ins depending if they come from an OSGi or Eclipse application launch config.
Comment 6 Chris Aniszczyk CLA 2009-03-19 12:12:24 EDT 
Created attachment 129367 [details]
org.eclipse.pde.ui.patch

An updated patch that works for osgi launch configurations.
Comment 7 Chris Aniszczyk CLA 2009-03-19 12:26:57 EDT 
Created attachment 129369 [details]
org.eclipse.pde.ui.patch

An updated and completed patch.
Comment 8 Chris Aniszczyk CLA 2009-03-19 12:27:26 EDT 
Created attachment 129370 [details]
org.eclipse.pde.ui.patch

An updated and completed patch.
Comment 9 Chris Aniszczyk CLA 2009-03-19 12:28:30 EDT 
done.

> 20090319
Comment 10 Chris Aniszczyk CLA 2009-03-19 12:28:51 EDT 
reopening due to assignment
Comment 11 Chris Aniszczyk CLA 2009-03-19 12:29:54 EDT 
done now ;)
Comment 12 Chris Aniszczyk CLA 2009-03-26 16:45:11 EDT 
*** Bug 219343 has been marked as a duplicate of this bug. ***