Re: [pde-dev] Product vs. Launch Inconsistencies

[Brian Bauman <baumanbr@xxxxxxxxxx>]

The way PDE treats the two is as separate
entities.  When you select a launch configuration in the wizard, we
use it only to initialize.  We do this as to keep the concept easy
to manage.  The reason being that synchronization is a tricky thing.
 

Do you synchronize both ways (changes
in product/launch config)?  Do you synchronize all changes (adding/removing
bundles)?  How do you synchronize a product config that is based on
features?  In a product configuration, do you synchronize a change
across all OS's or just the one you are working in (things like program/VM
arguments)?  If you sync just the one you work with, this could lead
to people having different program arguments in different OS's by accident.
 If you sync all of them you can't specify any OS specific VM/Program
arguments.  Is there ever a time a user would not want a change to
be propagated?  Would the synchronization over write a value the user
modified manually?  There is not really a compare mode, so we can't
really show diffs.

This is a very complex problem and so
instead of trying to make assumptions on what is best to do for our users,
we have stayed out of it letting users manager their own product configurations.

I wanted to say I though there was a
bug already open about this, but I can't seem to find it.  So feel
free to open a bug :)  I just want to make sure we have a well thought
out story before we start implementing synchronization like this.

Sorry I could not be more helpful Ian.

Brian Bauman
     IBM Software Group - Austin, TX
     Eclipse Committer
     baumanbr@xxxxxxxxxx
     (512) 838 -2938 (T/L 678-2938)

From:	Ian Bull <irbull@xxxxxxxxxx>
To:	"Eclipse PDE general developers list." <pde-dev@xxxxxxxxxxx>
Date:	10/31/2007 01:26 PM
Subject:	Re: [pde-dev] Product vs. Launch Inconsistencies

---

I have always been able to find the differences, I
am talking more about 
the user experience around maintaining two configurations.  So if
I add 
a new bundle, and test it from within eclipse (open the launch tab, add
the bundle, configure it, etc...), I also have to add it (by hand) to my
config.ini file when I go to export it from the product wizard.  I
would 
be nice if I could say (in the X.product file configuration tab), keep
my config.ini file in sync with my launch configuration.

Maybe this is what the generate config.ini option is supposed to do, and
I just stumbled upon a bug.

Cheers,
Ian

Brian Bauman wrote:
>
> What do the two config.ini look like?  Can you attach them in
an email 
> so we can see the differences.  Knowing what is different might
help 
> diagnose the problem.
>
> Brian Bauman
>     IBM Software Group - Austin, TX
>     Eclipse Committer
>     baumanbr@xxxxxxxxxx
>     (512) 838 -2938 (T/L 678-2938)
>
>
>
> From:                
 Ian Bull <irbull@xxxxxxxxxx>
> To:                
 "Eclipse PDE general developers list." <pde-dev@xxxxxxxxxxx>
> Date:                
 10/30/2007 11:54 PM
> Subject:              
   [pde-dev] Product vs. Launch Inconsistencies
>
>
> ------------------------------------------------------------------------
>
>
>
> There seems to be some inconsistencies between the product configuration
> and a launch configuration.  I have a small OSGi application
that I can
> launch fine from Eclipse, but when I go to create a product, export
it,
> and launch it, it doesn't run the same.  The reason is the actual
> configuration file (the one that defines which bundles should start,
and
> their run level, etc...) is not in sync with what I launched from
> Eclipse.  This may just be my lack of understanding, and if it
is tell
> me and I will post the question on the newsgroup.  However, I
think the
> problem exists because the launch and product configuration are two
> separate things.
>
> I know I can address this by grabbing (or pointing my config.ini file)
> to the one created in configuration directory when I launch my OSGi
> application, but this seems a little convoluted.  Since it is
still
> early in the development cycle, does anyone have other  thoughts
on how
> we could address this?  Does anyone else see this as a problem
or is
> there a better way to manage my development + export environment?
 It
> seems like we could provide a slightly better use experience here.
>
> Cheers,
> Ian
>
> -- 
> R. Ian Bull
> PhD Candidate, University of Victoria
> http://www.ianbull.com
<http://www.ianbull.com/>
> http://irbull.blogspot.com/
>
>
> _______________________________________________
> pde-dev mailing list
> pde-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/pde-dev
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> pde-dev mailing list
> pde-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/pde-dev
>   


-- 
R. Ian Bull
PhD Candidate, University of Victoria
http://www.ianbull.com
http://irbull.blogspot.com/


_______________________________________________
pde-dev mailing list
pde-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pde-dev