[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [pde-dev] PDEState and state caching
|
Wassim Melhem wrote on Friday, September 01, 2006
> I don't know about the 'le grand' part. I'm just a guy who
> likes to make plug-in develpers happy :)
So for me, as an happy plugin dev, you are le grand!
> Such a task would certainly be useful. However, what would
> you envision the input for the task would be. ie. will we pass in
2500
> plug-in IDs? :)
I envision a path like fileset structure (that's what I have working
today):
<checkState verbose="true|false" failonerror="true|false">
<pluginset dir="/home/install/eclipse/plugins">
<include name="**" />
</pluginset>
<pluginset dir="/home/install/eclipseextension/eclipse/plugins">
<include name="**" />
</pluginset>
</checkState>
So it does not matter if you have one or a 1000 or 2500
(who the heck could be using so many bundles ? I wonder ;-) )
You pass it a a pluginset and it runs with it.
The pluginset is interpreted so build the URL[] that the *States classes
expect.
Output use the regular ant log mechanism.
Cordially
--
Cheers
Philippe
philippe ombredanne | 1 650 799 0949 | pombredanne at nexb.com
nexB - Open by Design (tm) - http://www.nexb.com
http://easyeclipse.org - irc://irc.freenode.net/easyeclipse
> -----Original Message-----
> From: pde-dev-bounces@xxxxxxxxxxx
> [mailto:pde-dev-bounces@xxxxxxxxxxx] On Behalf Of Wassim Melhem
> Sent: Friday, September 01, 2006 10:33 AM
> To: Eclipse PDE general developers list.
> Cc: fg@xxxxxxxx; 'Eclipse PDE general developers list.';
> pde-dev-bounces@xxxxxxxxxxx
> Subject: RE: [pde-dev] PDEState and state caching
>
>
> >Wassim le grand wrote:
>
> I don't know about the 'le grand' part. I'm just a guy who
> likes to make
> plug-in develpers happy :)
>
> Such a task would certainly be useful. However, what would
> you envision
> the input for the task would be. ie. will we pass in 2500
> plug-in IDs? :)
>
> Wassim.
>
>
>
>
>
>
> "Philippe
>
> Ombredanne"
>
> <pombredanne@gmai
> To
> l.com> "'Eclipse PDE general
> developers
> Sent by: list.'"
> <pde-dev@xxxxxxxxxxx>
> pde-dev-bounces@e
> cc
> clipse.org fg@xxxxxxxx
>
>
> Subject
> RE: [pde-dev] PDEState
> and state
> 09/01/2006 12:12 caching
>
> PM
>
>
>
>
>
> Please respond to
>
> "Eclipse PDE
>
> general
>
> developers list."
>
> <pde-dev@eclipse.
>
> org>
>
>
>
>
>
>
>
>
>
> Wassim le grand wrote:
> > What ant task you referring to?
> Philippe le sneaky wrote:
> > >I am building a set of ant tasks that re-use PDEState to
> > >validate the state of an arbitrary set of bundles and plugins, all
> external.
> > Care for a contribution?
> We use those as a post-build test task that can help discover issues
> when you assemble several projects's plugin together, to make sure all
> dependencies are properly resolved in a user configuration.
> It performs a static validation ensurnig that you will get OSGi
> resolution at the minimum.
> I could see it's use for Callisto, or any large or very large Eclipse
> deployment.
> For instance validating that a set of plugins/bundles you ship will
> resolve at runtime -- especially when you have 2500 plugins
> ;-) created
> by every known alien species in the galaxy-- can be daunting and error
> prone.
>
> Including a test/validation task after everything has been built and
> packed can uncover snafus.
> At least it does for me.
>
> Cordially
> --
> Cheers
> Philippe
>
> philippe ombredanne | 1 650 799 0949 | pombredanne at nexb.com
> nexB - Open by Design (tm) - http://www.nexb.com
> http://easyeclipse.org - irc://irc.freenode.net/easyeclipse
>
>
>
> > -----Original Message-----
> > From: pde-dev-bounces@xxxxxxxxxxx
> > [mailto:pde-dev-bounces@xxxxxxxxxxx] On Behalf Of Wassim Melhem
> > Sent: Thursday, August 31, 2006 1:57 PM
> > To: Eclipse PDE general developers list.
> > Cc: fg@xxxxxxxx; 'Eclipse PDE general developers list.';
> > pde-dev-bounces@xxxxxxxxxxx
> > Subject: RE: [pde-dev] PDEState and state caching
> > > By the way that ant task in no big deal
> > What ant task you referring to?
> > Wassim.
> > "Philippe
> > Ombredanne"
> > <pombredanne@gmai
> > To
> > l.com> "'Eclipse PDE general
> > developers
> > Sent by: list.'"
> > <pde-dev@xxxxxxxxxxx>
> > pde-dev-bounces@e
> > cc
> > clipse.org fg@xxxxxxxx
> >
> >
> > Subject
> > RE: [pde-dev] PDEState
> > and state
> > 08/31/2006 03:39 caching
> >
> > PM
> >
> >
> >
> >
> >
> > Please respond to
> >
> > "Eclipse PDE
> >
> > general
> >
> > developers list."
> >
> > <pde-dev@eclipse.
> >
> > org>
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Sweet... Thanks Wassim...
> > By the way that ant task in no big deal... but could be
> > helpful to many
> > projects IMHO.
> > Care for a contribution?
> >
> > --
> > Cheers
> > Philippe
> >
> > philippe ombredanne | 1 650 799 0949 | pombredanne at nexb.com
> > nexB - Open by Design (tm) - http://www.nexb.com
> > http://easyeclipse.org - irc://irc.freenode.net/easyeclipse
> >
> >
> >
> > > -----Original Message-----
> > > From: pde-dev-bounces@xxxxxxxxxxx
> > > [mailto:pde-dev-bounces@xxxxxxxxxxx] On Behalf Of Wassim Melhem
> > > Sent: Thursday, August 31, 2006 12:20 PM
> > > To: Eclipse PDE general developers list.
> > > Cc: fg@xxxxxxxx; 'Eclipse PDE general developers list.';
> > > pde-dev-bounces@xxxxxxxxxxx
> > > Subject: Re: [pde-dev] PDEState and state caching
> > >
> > >
> > > Hi Philippe,
> > >
> > > What you want then is a stateless state :), ie. one that
> > does not use
> > > caching.
> > >
> > > For that, you should use MinimalState.
> > >
> > > Take a look a the implementation of the 'Validate Plug-in
> > > Set' button on
> > > the Plug-ins tab of the Eclipse/Equinox launch configuration.
> > > Sounds like you need an identical or trimmed-down
> function for your
> > > purposes, since you only care about unsatisfied constraints.
> > >
> > > org.eclipse.pde.internal.ui.launcher.PluginValidationOperation
> > > should be a
> > > good starting point.
> > >
> > > Wassim.
> > >
> > >
> > >
> > >
> > >
> > >
> > > Philippe
> > >
> > > Ombredanne
> > >
> > > <pombredanne@gmai
> > > To
> > > l.com> "'Eclipse PDE general
> > > developers
> > > Sent by: list.'"
> > > <pde-dev@xxxxxxxxxxx>
> > > pde-dev-bounces@e
> > > cc
> > > clipse.org fg@xxxxxxxx
> > >
> > >
> > > Subject
> > > [pde-dev] PDEState and
> > > state
> > > 08/31/2006 03:04 caching
> > >
> > > PM
> > >
> > >
> > >
> > >
> > >
> > > Please respond to
> > >
> > > "Eclipse PDE
> > >
> > > general
> > >
> > > developers list."
> > >
> > > <pde-dev@eclipse.
> > >
> > > org>
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > Hi:
> > > I have a question on PDESate
> > > I am building a set of ant tasks that re-use PDEState to
> > validate the
> > > state of an arbitrary set of bundles and plugins, all external.
> > >
> > > I get a PDESate to obtain a State with :
> > > PDEState pdeState = new PDEState(new URL[0], urls, true, new
> > > NullProgressMonitor());
> > > State osgiState = pdeState.getState();
> > > IPluginModelBase[] targetModels = pdeState.getTargetModels();
> > >
> > > and then I iterate over that to get errors:
> > > BundleDescription bd = targetModels[i].getBundleDescription();
> > > ResolverError[] re = osgiState.getResolverErrors(bd);
> > > and do some simple analysis of that.
> > >
> > > It works great but the second time I run it on a set of
> bundles that
> > > cannot be resolved, its runs without detecting errors.
> > > It sounds that PDEState does some smart caching...based on
> > time stamps
> > > How to disable that?
> > > Is that with System.setProperty("pde.nocache","true") ? But
> > > it seems to
> > > apply only to 'workspace' plugins, while I am feeding only target
> > > stuffs.
> > > I tried to create the PDEstate with resolve true or false.
> > no changes.
> > > Or some other trick?
> > > Would just cleaning the directory be enough?
> > >
> > > I would like to avoid hacking the PDESate code, which is
> so cooool!
> > > Cordially
> > >
> > > --
> > > Cheers
> > > Philippe
> > >
> > > philippe ombredanne | 1 650 799 0949 | pombredanne at nexb.com
> > > nexB - Open by Design (tm) - http://www.nexb.com
> > > http://easyeclipse.org - irc://irc.freenode.net/easyeclipse
> > >
> > >
> > >
> > >
> > > _______________________________________________
> > > 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
> > >
> >
> > _______________________________________________
> > 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
> >
>
> _______________________________________________
> 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
>
