Home » Archived » Buckminster » Shipping a configured eclipse IDE to my colleagues
| |
| Re: Shipping a configured eclipse IDE to my colleagues [message #499723 is a reply to message #499655] |
Mon, 23 November 2009 20:34   |
 Henrik Lindberg
Messages: 2509
Registered: July 2009 |
Senior Member |
|
|
Hi,
this is a very good use case for Buckminster Aggregator. It is typically
used for this specific reason.
The first step is to create a repository that contains the things you
want your collegues to use. You can either create it as a mirror (so you
are independent of network issues), or create a site that simply refers
to other p2 sites. A common thing would be to mirror things from smaller
update sites, but refer to the eclipse release repository.
The Buckminster Aggregator is suitable for performing this repository
composition.
(You don't have to compose the repositories, but if bundles come from
multiple locations, all of them needs to be specified when installing,
and it is easier if you have everything available using one address).
Once you have this repository, things can be installed from it. You can
also create traditional zip files from it (for traditional
installation). Other alternatives are to run the p2 installer, the
headless director app, or setup the EPP Wizard on you web server and
configure it with the choices you want to be included.
To reduce the complexity, the first step is to make sure things are
installable using the headless director - then you know you have all the
information in the right place.
- henrik
On 11/23/09 4:43 PM, Alain Helfenstein wrote:
> Hi all
>
> Is this task too easy - or totally unrealistic to solve using buckminster?
>
> Thanks for any responses,
> Alain.
>
>> Hi all
>>
>> I try to write a concept of how to ship a fully configured eclipse IDE
>> to my colleagues.
>>
>> At the end, my colleagues should only follow a web-link (or starting a
>> batch-file), in order to set up their programming environment. I read
>> about “installing” in the BuckyBook but are not sure, if this is
>> possible using Buckminster/p2.
>>
>> The configured eclipse IDE looks as following:
>> - Eclipse PDE SDK
>> - AJDT Feature
>> - Subclipse Feature
>> - Other Features…
>> - Eclipse Preferences
>> - Eclipse launch configurations
>>
>> I have already tried to use the p2 installer, but could not handle the
>> additional Features and configurations.
>> Should I use the director application or even the EPP wizard?
>>
>> Thanks for responses,
>> Alain.
|
|
|
| Re: Shipping a configured eclipse IDE to my colleagues [message #500967 is a reply to message #499723] |
Mon, 30 November 2009 14:06 |
Alain 
Messages: 115
Registered: July 2009 |
Senior Member |
|
|
Thanks a lot for your help!
I managed to configure the update site using the aggregator application.
After that, I tried to install a eclipse 3.5.1 and some additional
features using the director application.
But there are some problems now:
1. to install the org.eclipse.sdk.ide installabelUnit (product) I used
the headless director with success.
2. then I tried to install some additional features using the headless
director but without success. (see stack trace at the end of the email)
"director -r
file:///C:/Dev/InterneProjekte/UpdateSiteForIvy42DevEnvironm ent/final -i
org.eclipse.ve.feature.group -d C:/Users/ah/temp/DevEnv42/eclipse -p
SDKProfile"
3. then I tried to install the features using the eclipsec.exe of my
just installed eclipse - with success.
"eclipsec.exe -application org.eclipse.equinox.p2.director -repository
file:///C:/Dev/InterneProjekte/UpdateSiteForIvy42DevEnvironm ent/final
-installIU org.eclipse.ve.feature.group"
Question:
1. What did I wrong in the step 2?
2. To install eclipse preferences do I use the buckminster
"importpreferences" command?
3. what can I use, in order to import eclipse (jdt) launch configurations?
Thanks for your answers, Alain.
Error stack trace of step 2:
!SESSION 2009-11-30 12:21:20.972
-----------------------------------------------
eclipse.buildId=unknown
java.version=1.6.0_17
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_CH
Framework arguments: -application org.eclipse.equinox.p2.director
-metadataRepository
file:///C:/Dev/InterneProjekte/UpdateSiteForIvy42DevEnvironm ent/final
-artifactRepository
file:///C:/Dev/InterneProjekte/UpdateSiteForIvy42DevEnvironm ent/final
-installIU org.eclipse.ajdt.feature.group -destination
C:/Users/ah/temp/DevEnv42/eclipse -profile SDKProfile
Command-line arguments: -application org.eclipse.equinox.p2.director
-metadataRepository
file:///C:/Dev/InterneProjekte/UpdateSiteForIvy42DevEnvironm ent/final
-artifactRepository
file:///C:/Dev/InterneProjekte/UpdateSiteForIvy42DevEnvironm ent/final
-installIU org.eclipse.ajdt.feature.group -destination
C:/Users/ah/temp/DevEnv42/eclipse -profile SDKProfile
!ENTRY org.eclipse.equinox.p2.repository 2 0 2009-11-30 12:21:33.296
!MESSAGE Server returned lastModified <= 0 for
http://subclipse.tigris.org/update_1.6.x/content.xml
!ENTRY org.eclipse.equinox.p2.repository 4 0 2009-11-30 12:25:46.968
!MESSAGE ProvisioningEventBus could not be obtained. Metadata caches may
not be cleaned up properly.
!ENTRY org.eclipse.equinox.p2.garbagecollector 4 0 2009-11-30 12:25:46.984
!MESSAGE ProvisioningEventBus service could not be obtained,
CoreGarbageCollector will not function properly.
!ENTRY org.eclipse.equinox.p2.engine 4 4 2009-11-30 12:25:47.608
!MESSAGE An error occurred while committing the engine session for
profile: SDKProfile.
!SUBENTRY 1 org.eclipse.equinox.p2.engine 4 0 2009-11-30 12:25:47.608
!MESSAGE An error occurred while undoing the
org.eclipse.equinox.internal.provisional.p2.engine.phases.Ch eckTrust phase.
!STACK 0
java.lang.NullPointerException
at org.osgi.util.tracker.ServiceTracker.<init>(ServiceTracker.java:200)
at
org.eclipse.equinox.internal.provisional.p2.engine.Certifica teChecker. <init>(CertificateChecker.java:36)
at
org.eclipse.equinox.internal.provisional.p2.engine.phases.Ch eckTrust.completePhase(CheckTrust.java:41)
at
org.eclipse.equinox.internal.provisional.p2.engine.Phase.pos tPerform(Phase.java:195)
at
org.eclipse.equinox.internal.provisional.p2.engine.EngineSes sion.rollBackPhase(EngineSession.java:203)
at
org.eclipse.equinox.internal.provisional.p2.engine.EngineSes sion.rollback(EngineSession.java:145)
at
org.eclipse.equinox.internal.provisional.p2.engine.Engine.pe rform(Engine.java:63)
at
org.eclipse.equinox.internal.provisional.p2.director.PlanExe cutionHelper.executePlan(PlanExecutionHelper.java:41)
at
org.eclipse.equinox.internal.provisional.p2.director.PlanExe cutionHelper.executePlan(PlanExecutionHelper.java:23)
at
org.eclipse.equinox.internal.p2.director.app.DirectorApplica tion.planAndExecute(DirectorApplication.java:506)
at
org.eclipse.equinox.internal.p2.director.app.DirectorApplica tion.performProvisioningActions(DirectorApplication.java:492 )
at
org.eclipse.equinox.internal.p2.director.app.DirectorApplica tion.run(DirectorApplication.java:708)
at
org.eclipse.equinox.internal.p2.director.app.DirectorApplica tion.start(DirectorApplication.java:808)
at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:194)
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(EclipseS tarter.java:368)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.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: 559)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
at org.eclipse.equinox.launcher.Main.main(Main.java:1287)
!ENTRY org.eclipse.equinox.p2.engine 4 4 2009-11-30 12:25:47.873
!MESSAGE An error occurred while installing the items
!SUBENTRY 1 org.eclipse.equinox.p2.engine 4 0 2009-11-30 12:25:47.873
!MESSAGE session context was:(profile=SDKProfile,
phase=org.eclipse.equinox.internal.provisional.p2.engine.pha ses.Install,
operand=null --> [R]org.apache.commons.lang 2.4.0.v20081016-1030,
action=org.eclipse.equinox.internal.p2.touchpoint.eclipse.ac tions.InstallBundleAction).
!SUBENTRY 1 org.eclipse.equinox.p2.engine 4 0 2009-11-30 12:25:47.873
!MESSAGE
!STACK 0
java.lang.NullPointerException
at
org.eclipse.equinox.internal.p2.touchpoint.eclipse.LazyManip ulator.loadDelegate(LazyManipulator.java:64)
at
org.eclipse.equinox.internal.p2.touchpoint.eclipse.LazyManip ulator.getConfigData(LazyManipulator.java:108)
at
org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.I nstallBundleAction.installBundle(InstallBundleAction.java:76 )
at
org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.I nstallBundleAction.execute(InstallBundleAction.java:29)
at
org.eclipse.equinox.internal.p2.engine.ParameterizedProvisio ningAction.execute(ParameterizedProvisioningAction.java:35)
at
org.eclipse.equinox.internal.provisional.p2.engine.Phase.mai nPerform(Phase.java:129)
at
org.eclipse.equinox.internal.provisional.p2.engine.Phase.per form(Phase.java:72)
at
org.eclipse.equinox.internal.provisional.p2.engine.PhaseSet. perform(PhaseSet.java:44)
at
org.eclipse.equinox.internal.provisional.p2.engine.Engine.pe rform(Engine.java:54)
at
org.eclipse.equinox.internal.provisional.p2.director.PlanExe cutionHelper.executePlan(PlanExecutionHelper.java:41)
at
org.eclipse.equinox.internal.provisional.p2.director.PlanExe cutionHelper.executePlan(PlanExecutionHelper.java:23)
at
org.eclipse.equinox.internal.p2.director.app.DirectorApplica tion.planAndExecute(DirectorApplication.java:506)
at
org.eclipse.equinox.internal.p2.director.app.DirectorApplica tion.performProvisioningActions(DirectorApplication.java:492 )
at
org.eclipse.equinox.internal.p2.director.app.DirectorApplica tion.run(DirectorApplication.java:708)
at
org.eclipse.equinox.internal.p2.director.app.DirectorApplica tion.start(DirectorApplication.java:808)
at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:194)
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(EclipseS tarter.java:368)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.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: 559)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
at org.eclipse.equinox.launcher.Main.main(Main.java:1287)
Henrik Lindberg schrieb:
> Hi,
> this is a very good use case for Buckminster Aggregator. It is typically
> used for this specific reason.
>
> The first step is to create a repository that contains the things you
> want your collegues to use. You can either create it as a mirror (so you
> are independent of network issues), or create a site that simply refers
> to other p2 sites. A common thing would be to mirror things from smaller
> update sites, but refer to the eclipse release repository.
>
> The Buckminster Aggregator is suitable for performing this repository
> composition.
>
> (You don't have to compose the repositories, but if bundles come from
> multiple locations, all of them needs to be specified when installing,
> and it is easier if you have everything available using one address).
>
> Once you have this repository, things can be installed from it. You can
> also create traditional zip files from it (for traditional
> installation). Other alternatives are to run the p2 installer, the
> headless director app, or setup the EPP Wizard on you web server and
> configure it with the choices you want to be included.
>
> To reduce the complexity, the first step is to make sure things are
> installable using the headless director - then you know you have all the
> information in the right place.
>
> - henrik
>
> On 11/23/09 4:43 PM, Alain Helfenstein wrote:
>> Hi all
>>
>> Is this task too easy - or totally unrealistic to solve using
>> buckminster?
>>
>> Thanks for any responses,
>> Alain.
>>
>>> Hi all
>>>
>>> I try to write a concept of how to ship a fully configured eclipse IDE
>>> to my colleagues.
>>>
>>> At the end, my colleagues should only follow a web-link (or starting a
>>> batch-file), in order to set up their programming environment. I read
>>> about “installing” in the BuckyBook but are not sure, if this is
>>> possible using Buckminster/p2.
>>>
>>> The configured eclipse IDE looks as following:
>>> - Eclipse PDE SDK
>>> - AJDT Feature
>>> - Subclipse Feature
>>> - Other Features…
>>> - Eclipse Preferences
>>> - Eclipse launch configurations
>>>
>>> I have already tried to use the p2 installer, but could not handle the
>>> additional Features and configurations.
>>> Should I use the director application or even the EPP wizard?
>>>
>>> Thanks for responses,
>>> Alain.
>
|
|
|
Goto Forum:
Current Time: Thu Apr 25 07:39:48 GMT 2024
Powered by FUDForum. Page generated in 0.02535 seconds |
] 
Search
Help
Register
Login
Home
