|
| Re: Building non-RCP osgi application [message #66690 is a reply to message #66669] |
Fri, 03 July 2009 17:45  |
 Chris Aniszczyk
Messages: 674
Registered: July 2009 |
Senior Member |
|
|
Kyle Neumeier wrote:
> Hi,
> I am a developer on a server-side (non-RCP) osgi project in which we
> have developed about 10-12 osgi bundles that consist of our
> application. In addition we have about 50 dependencies or so that
> reside in our target platform. It is easy to run the application from
> within eclipse using run configuration. My problem is that I cannot
> figure out a good way to export our application (10-12 bundles that we
> have developed) along with the dependencies in our target platform to a
> a folder with the eclipse structure (plugins folder and an executable to
> get things going).
>
> I have developed RCP applications in the past, and it was relatively
> easy to do an export: just create a new product file, configure the
> product file and hit export. The problem is that the product file
> requires me to point to an "eclipse application", which I do not have
> (since I am not developing an RCP app). I just want it to export all
> the plugins to a folder and give me an executable that I can use to
> start the osgi bundles. Any suggestions?
You can still use product definitions to build vanilla OSGi
applications! What's the problem with the product definitions? In 3.5,
we did a lot of work to make sure you didn't have to explicitly be tied
to RCP to use products in OSGi application. For example, there's options
now to not even include native artifacts when you export. Also, the
"application" and "product" fields are optional now. In your case, I
think you need the application field filled out and include the delta
pack... that should give you the launchers.
Also, be aware of this bug:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=281224
Cheers,
Chris Aniszczyk | EclipseSource Austin | +1 860 839 2465
http://twitter.com/eclipsesource | http://twitter.com/caniszczyk
|
|
|
| Re: Building non-RCP osgi application [message #598982 is a reply to message #66669] |
Fri, 03 July 2009 17:45 |
Chris Aniszczyk
Messages: 674
Registered: July 2009 |
Senior Member |
|
|
Kyle Neumeier wrote:
> Hi,
> I am a developer on a server-side (non-RCP) osgi project in which we
> have developed about 10-12 osgi bundles that consist of our
> application. In addition we have about 50 dependencies or so that
> reside in our target platform. It is easy to run the application from
> within eclipse using run configuration. My problem is that I cannot
> figure out a good way to export our application (10-12 bundles that we
> have developed) along with the dependencies in our target platform to a
> a folder with the eclipse structure (plugins folder and an executable to
> get things going).
>
> I have developed RCP applications in the past, and it was relatively
> easy to do an export: just create a new product file, configure the
> product file and hit export. The problem is that the product file
> requires me to point to an "eclipse application", which I do not have
> (since I am not developing an RCP app). I just want it to export all
> the plugins to a folder and give me an executable that I can use to
> start the osgi bundles. Any suggestions?
You can still use product definitions to build vanilla OSGi
applications! What's the problem with the product definitions? In 3.5,
we did a lot of work to make sure you didn't have to explicitly be tied
to RCP to use products in OSGi application. For example, there's options
now to not even include native artifacts when you export. Also, the
"application" and "product" fields are optional now. In your case, I
think you need the application field filled out and include the delta
pack... that should give you the launchers.
Also, be aware of this bug:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=281224
Cheers,
Chris Aniszczyk | EclipseSource Austin | +1 860 839 2465
http://twitter.com/eclipsesource | http://twitter.com/caniszczyk
|
|
|
Powered by
FUDForum. Page generated in 0.04190 seconds
] 
Search
Help
Register
Login
Home
