Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Equinox » Importing existing Bundles
Importing existing Bundles [message #33348] Thu, 15 January 2004 00:27 Go to next message
Stephen Goldbaum is currently offline Stephen GoldbaumFriend
Messages: 75
Registered: July 2009
Member
What's the best way to import the code for an existing OSGi bundle into
Eclipse so that it can be dynamically included in other plugin/bundles'
dependencies? The bundle already has a BundleActivator. I've tried
creating a new Plugin, importing the source code, then converting the
whole thing to an OSGi bundle. It seems to work, but I'm sure that's the
best approach.

Thanks,
Stephen
Re: Importing existing Bundles [message #33383 is a reply to message #33348] Thu, 15 January 2004 01:35 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: jeff_mcaffer_REMOVE.ca.ibm.com

You should just be able to run it as per normal. The "detail" is how to get
the darn thing installed. Two real choices

1) install using the console
2) insert a
"Stephen Goldbaum" <stephen.goldbaum@lehman.com> wrote in message
news:bu4mqc$3ek$1@eclipse.org...
> What's the best way to import the code for an existing OSGi bundle into
> Eclipse so that it can be dynamically included in other plugin/bundles'
> dependencies? The bundle already has a BundleActivator. I've tried
> creating a new Plugin, importing the source code, then converting the
> whole thing to an OSGi bundle. It seems to work, but I'm sure that's the
> best approach.
>
> Thanks,
> Stephen
>
Re: Importing existing Bundles [message #33421 is a reply to message #33383] Thu, 15 January 2004 01:36 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: jeff_mcaffer_REMOVE.ca.ibm.com

"Jeff McAffer" <jeff_mcaffer_REMOVE@ca.ibm.com> wrote in message
news:bu4qoi$78c$1@eclipse.org...
> You should just be able to run it as per normal. The "detail" is how to
get
> the darn thing installed. Two real choices
>
> 1) install using the console
> 2) insert a
> "Stephen Goldbaum" <stephen.goldbaum@lehman.com> wrote in message
> news:bu4mqc$3ek$1@eclipse.org...
> > What's the best way to import the code for an existing OSGi bundle into
> > Eclipse so that it can be dynamically included in other plugin/bundles'
> > dependencies? The bundle already has a BundleActivator. I've tried
> > creating a new Plugin, importing the source code, then converting the
> > whole thing to an OSGi bundle. It seems to work, but I'm sure that's
the
> > best approach.
> >
> > Thanks,
> > Stephen
> >
>
>
Re: Importing existing Bundles [message #33474 is a reply to message #33421] Thu, 15 January 2004 01:47 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: jeff_mcaffer_REMOVE.ca.ibm.com

Unbelievable!! I accidentally posted twice within 10 seconds. Sorry about
that. Now to continue...

You should just be able to run it as per normal. The "detail" is how to get
the darn thing installed. Two real choices
1) install using the console. In the current code there are some bugs which
likely prevent you from installing the bundle as a jar (this is being worked
on and should be available very soon). You can just extract the bundle into
a dir and install that dir. So something like
osgi> install reference:file:<path to the exploded bundle>
should do it.

2) insert a plugin.xml in there and use the Eclipse update mechanisms (e.g.,
just drop it in the plugins dir) Note taht I am not sure the the
plugin.xml is really even needed. The update guys were in the process of
making update understand manifest.mfs but I'm not sure that that code has
been released.

The expectation is that existing OSGi bundles will just work. This scenario
is currently not heavily tested but we believe it is important for 3.0.
Your help in fleshing this out would be greatly appreciated. Ask questions
and push for the function/scenarios you need. Detailed bug reports are
highly prized. We want to make this the best we can in the time left so
every bit helps.

Jeff


> > "Stephen Goldbaum" <stephen.goldbaum@lehman.com> wrote in message
> > news:bu4mqc$3ek$1@eclipse.org...
> > > What's the best way to import the code for an existing OSGi bundle
into
> > > Eclipse so that it can be dynamically included in other
plugin/bundles'
> > > dependencies? The bundle already has a BundleActivator. I've tried
> > > creating a new Plugin, importing the source code, then converting the
> > > whole thing to an OSGi bundle. It seems to work, but I'm sure that's
> the
> > > best approach.
> > >
> > > Thanks,
> > > Stephen
> > >
> >
> >
>
>
Re: Importing existing Bundles [message #33508 is a reply to message #33421] Thu, 15 January 2004 01:53 Go to previous messageGo to next message
Stephen Goldbaum is currently offline Stephen GoldbaumFriend
Messages: 75
Registered: July 2009
Member
Hmm... keeping me guessing, eh? Actually, I haven't figured out how to
start the initial eclipse workspace with the console. I've tried running
"eclipse -console" from cmd (windows xp) but that seems to use javaw, so
there's no console. Either way, I'd really like to import the bundle into
its own project so I can continue to develop it.

Thanks,
Stephen

Jeff McAffer wrote:

> "Jeff McAffer" <jeff_mcaffer_REMOVE@ca.ibm.com> wrote in message
> news:bu4qoi$78c$1@eclipse.org...
> > You should just be able to run it as per normal. The "detail" is how to
> get
> > the darn thing installed. Two real choices
> >
> > 1) install using the console
> > 2) insert a
> > "Stephen Goldbaum" <stephen.goldbaum@lehman.com> wrote in message
> > news:bu4mqc$3ek$1@eclipse.org...
> > > What's the best way to import the code for an existing OSGi bundle into
> > > Eclipse so that it can be dynamically included in other plugin/bundles'
> > > dependencies? The bundle already has a BundleActivator. I've tried
> > > creating a new Plugin, importing the source code, then converting the
> > > whole thing to an OSGi bundle. It seems to work, but I'm sure that's
> the
> > > best approach.
> > >
> > > Thanks,
> > > Stephen
> > >
> >
> >
Re: Importing existing Bundles [message #33712 is a reply to message #33508] Fri, 16 January 2004 04:36 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: jeff_mcaffer_REMOVE.ca.ibm.com

The eclipse.exe has not been updated to know about -console (and to then use
java.exe). Two options:
eclipse.exe -console -consolelog
or
eclipse.exe -console -vm <path to java.exe>

Jeff

"Stephen Goldbaum" <stephen.goldbaum@lehman.com> wrote in message
news:bu4rr4$879$1@eclipse.org...
> Hmm... keeping me guessing, eh? Actually, I haven't figured out how to
> start the initial eclipse workspace with the console. I've tried running
> "eclipse -console" from cmd (windows xp) but that seems to use javaw, so
> there's no console. Either way, I'd really like to import the bundle into
> its own project so I can continue to develop it.
>
> Thanks,
> Stephen
>
> Jeff McAffer wrote:
>
> > "Jeff McAffer" <jeff_mcaffer_REMOVE@ca.ibm.com> wrote in message
> > news:bu4qoi$78c$1@eclipse.org...
> > > You should just be able to run it as per normal. The "detail" is how
to
> > get
> > > the darn thing installed. Two real choices
> > >
> > > 1) install using the console
> > > 2) insert a
> > > "Stephen Goldbaum" <stephen.goldbaum@lehman.com> wrote in message
> > > news:bu4mqc$3ek$1@eclipse.org...
> > > > What's the best way to import the code for an existing OSGi bundle
into
> > > > Eclipse so that it can be dynamically included in other
plugin/bundles'
> > > > dependencies? The bundle already has a BundleActivator. I've tried
> > > > creating a new Plugin, importing the source code, then converting
the
> > > > whole thing to an OSGi bundle. It seems to work, but I'm sure
that's
> > the
> > > > best approach.
> > > >
> > > > Thanks,
> > > > Stephen
> > > >
> > >
> > >
>
>
Re: Importing existing Bundles [message #33912 is a reply to message #33712] Fri, 16 January 2004 15:31 Go to previous message
Stephen Goldbaum is currently offline Stephen GoldbaumFriend
Messages: 75
Registered: July 2009
Member
Thanks. That did the trick.

Jeff McAffer wrote:

> The eclipse.exe has not been updated to know about -console (and to then use
> java.exe). Two options:
> eclipse.exe -console -consolelog
> or
> eclipse.exe -console -vm <path to java.exe>

> Jeff

> "Stephen Goldbaum" <stephen.goldbaum@lehman.com> wrote in message
> news:bu4rr4$879$1@eclipse.org...
> > Hmm... keeping me guessing, eh? Actually, I haven't figured out how to
> > start the initial eclipse workspace with the console. I've tried running
> > "eclipse -console" from cmd (windows xp) but that seems to use javaw, so
> > there's no console. Either way, I'd really like to import the bundle into
> > its own project so I can continue to develop it.
> >
> > Thanks,
> > Stephen
> >
> > Jeff McAffer wrote:
> >
> > > "Jeff McAffer" <jeff_mcaffer_REMOVE@ca.ibm.com> wrote in message
> > > news:bu4qoi$78c$1@eclipse.org...
> > > > You should just be able to run it as per normal. The "detail" is how
> to
> > > get
> > > > the darn thing installed. Two real choices
> > > >
> > > > 1) install using the console
> > > > 2) insert a
> > > > "Stephen Goldbaum" <stephen.goldbaum@lehman.com> wrote in message
> > > > news:bu4mqc$3ek$1@eclipse.org...
> > > > > What's the best way to import the code for an existing OSGi bundle
> into
> > > > > Eclipse so that it can be dynamically included in other
> plugin/bundles'
> > > > > dependencies? The bundle already has a BundleActivator. I've tried
> > > > > creating a new Plugin, importing the source code, then converting
> the
> > > > > whole thing to an OSGi bundle. It seems to work, but I'm sure
> that's
> > > the
> > > > > best approach.
> > > > >
> > > > > Thanks,
> > > > > Stephen
> > > > >
> > > >
> > > >
> >
> >
Previous Topic:When is a plugin a dependency of another...
Next Topic:ClassLoading/Security issue
Goto Forum:
  


Current Time: Thu Apr 25 05:06:38 GMT 2024

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

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

Back to the top