Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » Buckminster » Product config.ini generation
Product config.ini generation [message #383525] Mon, 23 March 2009 16:15 Go to next message
Nick Veys is currently offline Nick VeysFriend
Messages: 52
Registered: July 2009
Member
Having an issue generating our products since the resultant config.ini is
vastly different than the one generated through an Eclipse export.

The basic structure is the same, but the 'osgi.bundles' list is very
different between the two.

From Eclipse export:
osgi.bundles=org.eclipse.equinox.common@2:start,org.eclipse.update.configurator@3:start,org.eclipse.core.runtime@start

From Buckminster:
osgi.bundles=org.eclipse.equinox.simpleconfigurator@1:start,com.ibm.icu,
...... _all_ of the plugins in our product ......
,org.junit4,org.junit,org.w3c.css.sac,org.w3c.dom.smil,org.w 3c.dom.svg

When I run the buckminster-generated one, we get classpath
(NoClassDefFound, etc) issues and all of _our_ fragments don't get
resolved, they stay at INSTALLED. If I swap in the one produced from an
Eclipse export run, it works fine.

I've tried adding the org.eclipse.equinox feature to my product feature,
since the simpleconfigurator is contained there and I wasn't depending on
it, but that didn't help.

Ideas? Could there be some plugin or feature I'm not depending on but
need to?
Re: Product config.ini generation [message #383526 is a reply to message #383525] Mon, 23 March 2009 17:00 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas HallgrenFriend
Messages: 3240
Registered: July 2009
Senior Member
Hi Nick,
What version of Buckminser/Eclipse IDE are you using for the build/export?

- thomas

Nick Veys wrote:
> Having an issue generating our products since the resultant config.ini
> is vastly different than the one generated through an Eclipse export.
>
> The basic structure is the same, but the 'osgi.bundles' list is very
> different between the two.
>
> From Eclipse export:
> osgi.bundles=org.eclipse.equinox.common@2:start,org.eclipse.update.configurator@3:start,org.eclipse.core.runtime@start
>
>
> From Buckminster:
> osgi.bundles=org.eclipse.equinox.simpleconfigurator@1:start,com.ibm.icu,
> ..... _all_ of the plugins in our product ......
> ,org.junit4,org.junit,org.w3c.css.sac,org.w3c.dom.smil,org.w 3c.dom.svg
>
> When I run the buckminster-generated one, we get classpath
> (NoClassDefFound, etc) issues and all of _our_ fragments don't get
> resolved, they stay at INSTALLED. If I swap in the one produced from an
> Eclipse export run, it works fine.
>
> I've tried adding the org.eclipse.equinox feature to my product feature,
> since the simpleconfigurator is contained there and I wasn't depending
> on it, but that didn't help.
>
> Ideas? Could there be some plugin or feature I'm not depending on but
> need to?
>
Re: Product config.ini generation [message #383549 is a reply to message #383526] Mon, 23 March 2009 17:39 Go to previous message
Nick Veys is currently offline Nick VeysFriend
Messages: 52
Registered: July 2009
Member
Eclipse is 3.4.2, buckminster is 1.1.340.r09952 headless.

Thomas Hallgren wrote:
> Hi Nick,
> What version of Buckminser/Eclipse IDE are you using for the build/export?
Previous Topic:Can I pass parameters to Buckminster?
Next Topic:Exception while creating product
Goto Forum:
  


Current Time: Fri Apr 19 23:34:08 GMT 2024

Powered by FUDForum. Page generated in 0.02935 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top