[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [p2-dev] instances/examples for server-side install?

Hi Jeff,

Jeff McAffer wrote:
Scott, I suggest that you just use the publisher to publish whatever you need into one of your repos. There is a launch config in the publisher project that should help a little. I should write some doc soon. Perhaps with your collaboration we can identify the key cases to doc first. Lets look at this next week.

I took a very quick look at the publisher...at first blush it looks to primarily want to publish given a full eclipse install location (as source). Can this source be (e.g.) a feature zip/dir and/or update site? Obviously for server-side install it will need to be something other than an eclipse install location.

I tried passing in -source <my update site location>, but got the exception below...so must be not possible or I don't have right/enough params, etc. If you have any info about params (in source, etc). Please just LMK.



at org.eclipse.equinox.internal.p2.publisher.eclipse.DataLoader.<init>(DataLoader.java:127)
at org.eclipse.equinox.p2.publisher.eclipse.AccumulateConfigDataAction.<init>(AccumulateConfigDataAction.java:27)
at org.eclipse.equinox.p2.publisher.eclipse.EclipseInstallAction.createAccumulateConfigDataActions(EclipseInstallAction.java:117)
at org.eclipse.equinox.p2.publisher.eclipse.EclipseInstallAction.createActions(EclipseInstallAction.java:67)
at org.eclipse.equinox.p2.publisher.eclipse.EclipseInstallAction.perform(EclipseInstallAction.java:53)
at org.eclipse.equinox.p2.publisher.Publisher.publish(Publisher.java:140)
at org.eclipse.equinox.p2.publisher.AbstractPublisherApplication.run(AbstractPublisherApplication.java:189)
at org.eclipse.equinox.p2.publisher.AbstractPublisherApplication.run(AbstractPublisherApplication.java:167)
at org.eclipse.equinox.p2.publisher.AbstractPublisherApplication.start(AbstractPublisherApplication.java:214)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
at org.eclipse.equinox.launcher.Main.main(Main.java:1212)

The .properties file really just identifies the repos and the top level ius to install.

Nick pointed out some issues he has had. I could believe that they were/are problems but we should address them with the reorg of the director/installer/ProvisioningHelper so that this function is available to install anything into anything (new, old, product, add-on, ...)


Scott Lewis wrote:
Hi John,

John Arthorne wrote:

Hi Scott, I don't know of anyone who has tried using the installer bundle in a server-side context. This doesn't really surprise me since the installer code as it is today is closely tied to a standalone client GUI installer. Perhaps on the server side people are using the director application instead?

Perhaps so. Actually, if someone has a meta-data and artifact repos available (for something other than the sdk) that they've been using with the director, I'll just construct the installer properties info from that. Please let me know. It doesn't strictly have to be IUs intended for server side usage, but that would be cooler.




*Scott Lewis <slewis@xxxxxxxxxxxxx>*
Sent by: p2-dev-bounces@xxxxxxxxxxx

09/05/2008 12:39 PM
Please respond to
P2 developer discussions <p2-dev@xxxxxxxxxxx>

To P2 developer discussions <p2-dev@xxxxxxxxxxx> cc Subject Re: [p2-dev] instances/examples for server-side install?

Hi Folks,

Surprisingly, I haven't received any replies to this request.  Isn't
anyone creating on-the-net meta-data/artifact repos that could be used
to create an install properties file for their IUs?

Perhaps the publisher is able to do this now for existing features? (I
haven't looked yet...my apologies in advance if this is silly).

If there isn't someone already doing this, I will look to do it myself
(probably for ECF bundles initially), and make available for some
testing that I'm going to do with p2-enabled/Equinox servlets I've been


Scott Lewis wrote:
> I'm working with the installer bundle org.eclipse.equinox.p2.installer
> to setup a server-side installer...are there install descriptions
> around that I could use for testing? There's an
> sdk-installer.properties in the installer bundle but I don't see any
> others.
> Are there others that already exist that people wouldn't mind sharing
> for testing in a server install scenario? As another way to put
> it...are there folks that would be willing to put together a
> meta-data/artifact repo with their server side bundles so I can test
> with the servletbridge + installer + my recent work (described on bug
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=245267)?
> Thanks,
> Scott
> _______________________________________________
> p2-dev mailing list
> p2-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/p2-dev

p2-dev mailing list


p2-dev mailing list

_______________________________________________ p2-dev mailing list p2-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/p2-dev
p2-dev mailing list