|
Re: equinox and p2 Aha! Moment Needed [message #128051 is a reply to message #127979] |
Sun, 29 March 2009 03:21 |
Ben Vitale Messages: 247 Registered: July 2009 |
Senior Member |
|
|
See responses below.
Geoffry Roberts wrote:
> All,
>
> First the questions:
>
> Will p2 do what I want? i.e. ...take the launch configurations I use to
> run the nodes [equinox containers] from within the IDE and do
> deployments based on them.
>
> Do I really need an update site?
As in, an HTTP container serving up your nodes? It doesn't sound like
it, unless the nodes need to update themselves to new versions periodically.
>
> Do I have to create repositories?
If you are going to use p2, you will probably need a metadata repository
from which to provision the artifacts.
>
> Will p2 somehow write that awful config.ini file for me?
Not sure. I know for RCP "products", you can specify it to generate a
config.ini for you. Most likely that is part of the PDE build process.
>
> I sat down this morning to address my deployment issues with regard to
> equinox and quickly began looking into p2. Having read some very well
> prepared material from Band XI along with everything else is I could
> Google. I find myself in need of a good aha moment.
Have you seen the wiki? http://wiki.eclipse.org/Category:Equinox_p2
> I have what amounts to a distributed app with headless equinox
> containers running in different VMs all communicating via JMS. Let's
> call these equinoxes nodes. I need a good way to build and deploy these
> nodes. I've had an ant based solution for the past few weeks but it's
> proving to be much to brittle and expensive to maintain. What I'd like,
> would be to take the launch configurations I use to run the nodes from
> within the IDE and do deployments based on them. So I don't have to
> maintain two or more separate things say, the launcher, two places in
> the ant script, and config.ini. Yeesh!
The launchers take care of running something that is already built in
your workspace. To automate this outside of the workbench, you'll
probably need two steps, building and provisioning (deploying). The
standard Eclipse builder (PDE Build) does not work with launch
configurations, and the provisioning tools (p2) do not work off launch
configurations either. They both, generally speaking, consume plugin.xml
and OSGi manifest files to do their work.
>
> I sounds like p2 can be cajoled into doing something like this but I'm
> at a loss. Most things I've read talk about update sites but I don't
> think I need that much complexity.
>
>
I wish I could offer more but your use case is not something I've done
before. Hope these tidbits were helpful at least.
Cheers
Ben
|
|
|
Powered by
FUDForum. Page generated in 0.03918 seconds