Re: [equinox-dev] install workspace plug-ins on Equinox

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

Re: [equinox-dev] install workspace plug-ins on Equinox

From: Thomas Watson <tjwatson@xxxxxxxxxx>
Date: Tue, 3 Apr 2007 08:12:27 -0500
Delivered-to: equinox-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/listinfo/equinox-dev>
List-help: <mailto:equinox-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/equinox-dev>, <mailto:equinox-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/listinfo/equinox-dev>, <mailto:equinox-dev-request@eclipse.org?subject=unsubscribe>

You could open a bug against PDE-UI to request the enhancement. PDE-UI could create dev entries in the dev.properties for every plug-in project in your workspace which is not already selected from your target platform.

There are a few other bugs open against PDE that are related to development classpaths. You should search the PDE-UI bugs to see if there is already a similar one opened.

Tom

ChangWoo Jung <jungcw@xxxxxxxxxx>
Sent by: equinox-dev-bounces@xxxxxxxxxxx

04/01/2007 07:30 PM

Please respond to
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>

To	Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
cc
Subject	Re: [equinox-dev] install workspace plug-ins on Equinox

Tom,

I guess it could be sort of feature request.
Would that be helpful if PDE gives a global dev mode enable option which does the mapping of bundles in his workspace and their development time classpath entries, without user's selection for each bundle?
Currently, if user check the bundle then it implies that that bundle will be pre-installed.

The idea is that I can test some dynamic notion of install/uninstall thru the console without making pre-install decision but uses the self-hosting bundle project support?

Sincerely,
ChangWoo "Jason" Jung

Thomas Watson <tjwatson@xxxxxxxxxx>
Sent by: equinox-dev-bounces@xxxxxxxxxxx

2007-03-30 오후 11:02

Please respond to
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>

To	Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
cc
Subject	Re: [equinox-dev] install workspace plug-ins on Equinox

Passing "-dev bin" will only work if every bundle/plug-in project in your workspace uses "bin" as its output folder. I think you already answered most of your questions yourself ;-)

PDE generates a dev.properties which is passed to Equinox with the -dev option. This file contains a mapping of bundles and their development time classpath entries. PDE will only include a bundle in the dev.properties if it is selected to be included in the launch. By passing "-dev bin" you are telling the framework to use "bin" as the development time classpath for every bundle installed in the framework.

Tom

ChangWoo Jung <jungcw@xxxxxxxxxx>
Sent by: equinox-dev-bounces@xxxxxxxxxxx

03/30/2007 03:04 AM

Please respond to
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>

To	Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
cc
Subject	Re: [equinox-dev] install workspace plug-ins on Equinox

I guess I found the answer myself.
After passing "-dev bin", it works.

Sincerely,
ChangWoo "Jason" Jung

ChangWoo Jung/Korea/IBM@IBMKR
Sent by: equinox-dev-bounces@xxxxxxxxxxx

2007-03-30 오후 04:47

Please respond to
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>

To	equinox-dev@xxxxxxxxxxx
cc
Subject	[equinox-dev] install workspace plug-ins on Equinox

Hello folks,

I just want to install the workspace plug-in into equinox using self-hosting bundle project not using the jar packaging.
I guess it was supported by enabling the dev mode in the past (-dev)

But it gives me below error. (I used simple HelloWorld plug-in.)
It seems that if dev.properteis (which usually auto-generated when clicking the workspace plugin before launching) is missing then can't find the classes. (like "Hello=bin")

I guess this problem also can be occurred inside IDE.
If I don't check the workspace plug-in and start the equinox and later if I attempt to install workspace plug-in which was not chosen before and try the command like "install reference:file:[project_name]" then it gives me same error.

Do I miss something?

C:\Tools\eclipse-SDK-3.2.2-win32\eclipse>java -jar plugins/org.eclipse.osgi_3.2.
2.R32x_v20070118.jar -console

osgi> ss

Framework is launched.

id State Bundle
0 ACTIVE system.bundle_3.2.2.R32x_v20070118

osgi> install reference:file:C:\Eclipse_Workspace\3.2.2\TestWorkspace\Hello
Bundle id is 1

osgi> refresh

osgi> ss

Framework is launched.

id State Bundle
0 ACTIVE system.bundle_3.2.2.R32x_v20070118
1 RESOLVED Hello_1.0.0

osgi> start 1
org.osgi.framework.BundleException: The activator hello.Activator for bundle Hel
lo is invalid
at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadBundleAct
ivator(AbstractBundle.java:141)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(Bund
leContextImpl.java:962)
at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(Bundl
eHost.java:317)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(Abstrac
tBundle.java:256)
at org.eclipse.osgi.framework.internal.core.FrameworkCommandProvider._st
art(FrameworkCommandProvider.java:239)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:64)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:615)
at org.eclipse.osgi.framework.internal.core.FrameworkCommandInterpreter.
execute(FrameworkCommandInterpreter.java:145)
at org.eclipse.osgi.framework.internal.core.FrameworkConsole.docommand(F
rameworkConsole.java:293)
at org.eclipse.osgi.framework.internal.core.FrameworkConsole.console(Fra
meworkConsole.java:278)
at org.eclipse.osgi.framework.internal.core.FrameworkConsole.run(Framewo
rkConsole.java:213)
at java.lang.Thread.run(Thread.java:799)
Caused by: java.lang.ClassNotFoundException: hello.Activator
at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(Bundl
eLoader.java:402)
at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(Bundl
eLoader.java:347)
at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(De
faultClassLoader.java:83)
at java.lang.ClassLoader.loadClass(ClassLoader.java:563)
at org.eclipse.osgi.framework.internal.core.BundleLoader.loadClass(Bundl
eLoader.java:278)
at org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleH
ost.java:227)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadBundleAct
ivator(AbstractBundle.java:134)
... 13 more
Nested Exception:
java.lang.ClassNotFoundException: hello.Activator
at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(Bundl
eLoader.java:402)
at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(Bundl
eLoader.java:347)
at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(De
faultClassLoader.java:83)
at java.lang.ClassLoader.loadClass(ClassLoader.java:563)
at org.eclipse.osgi.framework.internal.core.BundleLoader.loadClass(Bundl
eLoader.java:278)
at org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleH
ost.java:227)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadBundleAct
ivator(AbstractBundle.java:134)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(Bund
leContextImpl.java:962)
at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(Bundl
eHost.java:317)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(Abstrac
tBundle.java:256)
at org.eclipse.osgi.framework.internal.core.FrameworkCommandProvider._st
art(FrameworkCommandProvider.java:239)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:64)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:615)
at org.eclipse.osgi.framework.internal.core.FrameworkCommandInterpreter.
execute(FrameworkCommandInterpreter.java:145)
at org.eclipse.osgi.framework.internal.core.FrameworkConsole.docommand(F
rameworkConsole.java:293)
at org.eclipse.osgi.framework.internal.core.FrameworkConsole.console(Fra
meworkConsole.java:278)
at org.eclipse.osgi.framework.internal.core.FrameworkConsole.run(Framewo
rkConsole.java:213)
at java.lang.Thread.run(Thread.java:799)
Nested Exception:
java.lang.ClassNotFoundException: hello.Activator
at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(Bundl
eLoader.java:402)
at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(Bundl
eLoader.java:347)
at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(De
faultClassLoader.java:83)
at java.lang.ClassLoader.loadClass(ClassLoader.java:563)
at org.eclipse.osgi.framework.internal.core.BundleLoader.loadClass(Bundl
eLoader.java:278)
at org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleH
ost.java:227)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadBundleAct
ivator(AbstractBundle.java:134)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(Bund
leContextImpl.java:962)
at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(Bundl
eHost.java:317)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(Abstrac
tBundle.java:256)
at org.eclipse.osgi.framework.internal.core.FrameworkCommandProvider._st
art(FrameworkCommandProvider.java:239)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:64)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:615)
at org.eclipse.osgi.framework.internal.core.FrameworkCommandInterpreter.
execute(FrameworkCommandInterpreter.java:145)
at org.eclipse.osgi.framework.internal.core.FrameworkConsole.docommand(F
rameworkConsole.java:293)
at org.eclipse.osgi.framework.internal.core.FrameworkConsole.console(Fra
meworkConsole.java:278)
at org.eclipse.osgi.framework.internal.core.FrameworkConsole.run(Framewo
rkConsole.java:213)
at java.lang.Thread.run(Thread.java:799)

osgi>

Sincerely,
ChangWoo "Jason" Jung

Staff Research Engineer, Ubiquitous Computing Laboratory, IBM Corporation, Seoul
e-mail: jungcw@xxxxxxxxxx
Tel: +82-2-3781-8422 (t/l: 825-8422), +82-10-3155-8422

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

Follow-Ups:
- Re: [equinox-dev] install workspace plug-ins on Equinox
  - From: Jeff McAffer

References:
- Re: [equinox-dev] install workspace plug-ins on Equinox
  - From: ChangWoo Jung

Prev by Date: [equinox-dev] Equinox projects tagged for 3.3 I-Build
Next by Date: [equinox-dev] new Equinox services from ProSyst
Previous by thread: Re: [equinox-dev] install workspace plug-ins on Equinox
Next by thread: Re: [equinox-dev] install workspace plug-ins on Equinox
Index(es):
- Date
- Thread

Breadcrumbs