Mailing list for developers of the Equinox OSGi implementation

Re: 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-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Sent by: equinox-dev-bounces-j9T/66MeVpFAfugRpC6u6w@public.gmane.org

2007-03-30 오후 11:02

Please respond to
Equinox development mailing list <equinox-dev-j9T/66MeVpFAfugRpC6u6w@public.gmane.org>

To	Equinox development mailing list <equinox-dev-j9T/66MeVpFAfugRpC6u6w@public.gmane.org>
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-IbmIGqUBH0XQT0dZR+AlfA@public.gmane.org>
Sent by: equinox-dev-bounces-j9T/66MeVpFAfugRpC6u6w@public.gmane.org

03/30/2007 03:04 AM

Please respond to
Equinox development mailing list <equinox-dev-j9T/66MeVpFAfugRpC6u6w@public.gmane.org>

To	Equinox development mailing list <equinox-dev-j9T/66MeVpFAfugRpC6u6w@public.gmane.org>
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 <at> IBMKR
Sent by: equinox-dev-bounces-j9T/66MeVpFAfugRpC6u6w@public.gmane.org

2007-03-30 오후 04:47

Please respond to
Equinox development mailing list <equinox-dev-j9T/66MeVpFAfugRpC6u6w@public.gmane.org>

To	equinox-dev-j9T/66MeVpFAfugRpC6u6w@public.gmane.org
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-IbmIGqUBH0XQT0dZR+AlfA@public.gmane.org
Tel: +82-2-3781-8422 (t/l: 825-8422), +82-10-3155-8422

_______________________________________________
equinox-dev mailing list
equinox-dev-j9T/66MeVpFAfugRpC6u6w@public.gmane.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________
equinox-dev mailing list
equinox-dev-j9T/66MeVpFAfugRpC6u6w@public.gmane.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________
equinox-dev mailing list
equinox-dev-j9T/66MeVpFAfugRpC6u6w@public.gmane.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev

headers

Thomas Watson | 3 Apr 00:29

Equinox projects tagged for 3.3 I-Build

The map file has been updated for the following Bug changes:
+ Bug 96832. ManifestLocalization.getResourceBundle could be improved (FIXED)
+ Bug 139531. debug/monitorbundles and monitor/activation trace options conflict (FIXED)
+ Bug 139935. NullPointerException in Launcher at line 262 (FIXED)
+ Bug 139983. Impossible to connect to framework console after connection reset (FIXED)
+ Bug 161449. ListenerQueue.dispatchEventAsynchronous should copy the listener list (FIXED)
+ Bug 173668. PermissionChecker can cause IllegalStateException (FIXED)
+ Bug 179321. TextProcessor should treat "he" as a rtl language (FIXED)
+ Bug 179787. [server] HttpServletRequest.getPathInfo should return null when path is not present (FIXED)
+ Bug 180145. Fragment gets resolved and attached even some of its imports are missing (FIXED)

The following projects have changed:
org.eclipse.equinox.servletbridge
org.eclipse.equinox.http.servlet
org.eclipse.osgi

Tom

headers

Thomas Watson | 3 Apr 15:12

Re: install workspace plug-ins on Equinox

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-IbmIGqUBH0XQT0dZR+AlfA@public.gmane.org>
Sent by: equinox-dev-bounces-j9T/66MeVpFAfugRpC6u6w@public.gmane.org

04/01/2007 07:30 PM

Please respond to
Equinox development mailing list <equinox-dev-j9T/66MeVpFAfugRpC6u6w@public.gmane.org>

To	Equinox development mailing list <equinox-dev-j9T/66MeVpFAfugRpC6u6w@public.gmane.org>
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-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Sent by: equinox-dev-bounces-j9T/66MeVpFAfugRpC6u6w@public.gmane.org

2007-03-30 오후 11:02

Please respond to
Equinox development mailing list <equinox-dev-j9T/66MeVpFAfugRpC6u6w@public.gmane.org>

To	Equinox development mailing list <equinox-dev-j9T/66MeVpFAfugRpC6u6w@public.gmane.org>
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-IbmIGqUBH0XQT0dZR+AlfA@public.gmane.org>
Sent by: equinox-dev-bounces-j9T/66MeVpFAfugRpC6u6w@public.gmane.org

03/30/2007 03:04 AM

Please respond to
Equinox development mailing list <equinox-dev-j9T/66MeVpFAfugRpC6u6w@public.gmane.org>

To	Equinox development mailing list <equinox-dev-j9T/66MeVpFAfugRpC6u6w@public.gmane.org>
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 <at> IBMKR
Sent by: equinox-dev-bounces-j9T/66MeVpFAfugRpC6u6w@public.gmane.org

2007-03-30 오후 04:47

Please respond to
Equinox development mailing list <equinox-dev-j9T/66MeVpFAfugRpC6u6w@public.gmane.org>

To	equinox-dev-j9T/66MeVpFAfugRpC6u6w@public.gmane.org
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-IbmIGqUBH0XQT0dZR+AlfA@public.gmane.org
Tel: +82-2-3781-8422 (t/l: 825-8422), +82-10-3155-8422

_______________________________________________
equinox-dev mailing list
equinox-dev-j9T/66MeVpFAfugRpC6u6w@public.gmane.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________
equinox-dev mailing list
equinox-dev-j9T/66MeVpFAfugRpC6u6w@public.gmane.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________
equinox-dev mailing list
equinox-dev-j9T/66MeVpFAfugRpC6u6w@public.gmane.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________
equinox-dev mailing list
equinox-dev-j9T/66MeVpFAfugRpC6u6w@public.gmane.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev

headers

Dimitar Valtchev | 3 Apr 15:26

new Equinox services from ProSyst

We are now ready with the source code of our OSGi services which we
will contribute to Equinox. These are:

- Implementation of OSGi Declarative Services Specification
- Implementation of OSGi IO Connector Service Specification
- Implementation of OSGi Initial Provisioning
- Implementation of OSGi Wire Admin Service Specification

We have done the following:

-all class packages have now names in the Eclipse namespace;
-all common utility classes used in the implementation of the services
above are packed in a separated bundle (util.jar) which is also
available under EPL and uses the Eclipse namespace;
-there are no dependencies on any other ProSyst classes.

My understanding is that we are currently not able to put any code
directly into the incubator area. Our case should be covered by Fig.6
of the document at
http://www.eclipse.org/legal/EclipseLegalProcessPoster.pdf, which
means that we need to fill the Contribution Questionnaire on Committer
Tools, to which we do not have access because we do not have a
committer status yet.

Jeff could you help us on this issue (I have already asked for a
committer status for our developers Pavlin Dobrev and Teodor Todorov)?
I can also provide a public link for FTP download and you can then put
the source into the Equinox CVS but I assume that this does not comply
with the defined legal process. How should we proceed?

Dimitar

headers

Ikuo Yamasaki | 4 Apr 06:20

Conditional Permission Admin

Hi,

Is there any document or instruction showing how to use Conditional
Permission Admin of Equinox implementation ? Especially I'm interested
in using BundleSignerCondition.

Regards,

=======
Ikuo YAMASAKI

headers

Woody Huang | 4 Apr 10:04

Woody Huang is out of the office.


I will be out of the office starting  04/04/2007 and will not return until
04/10/2007.

I will respond to your message when I return.

headers

Jeff McAffer | 4 Apr 19:32

Re: new Equinox services from ProSyst

Ha! chicken and egg problem... So the best way to do this as follows.
1) call for a vote to accept these contributions (see separate message following shortly)
2) assuming a good vote outcome, open separate Bugzilla entries in Eclipse/Equinox/Bundles for each of the service implementations that you will contribute.
3) Someone on the Equinox team will then enter the contribution questionnaires and start the legal process.
4) In parallel with that we will start the committer process. To that end various forms need to be filled out. See
http://www.eclipse.org/projects/dev_process/new-committer.php
I am not sure of Prosyst's status and what forms you have completed. You and I should work offline to walk through the process. Can you review the document and see which case applies here? Then we can submit the appropriate docs.

Make sense? Hopefully it will all come together in a couple weeks.

Jeff

Dimitar Valtchev <d.valtchev-gIMOvL9Iw+9BDgjK7y7TUQ@public.gmane.org>
Sent by: equinox-dev-bounces-j9T/66MeVpFAfugRpC6u6w@public.gmane.org

04/03/2007 09:26 AM

Please respond to
Equinox development mailing list <equinox-dev-j9T/66MeVpFAfugRpC6u6w@public.gmane.org>

To	equinox-dev-j9T/66MeVpFAfugRpC6u6w@public.gmane.org
cc
Subject	[equinox-dev] new Equinox services from ProSyst

We are now ready with the source code of our OSGi services which we
will contribute to Equinox. These are:

- Implementation of OSGi Declarative Services Specification
- Implementation of OSGi IO Connector Service Specification
- Implementation of OSGi Initial Provisioning
- Implementation of OSGi Wire Admin Service Specification

We have done the following:

-all class packages have now names in the Eclipse namespace;
-all common utility classes used in the implementation of the services
above are packed in a separated bundle (util.jar) which is also
available under EPL and uses the Eclipse namespace;
-there are no dependencies on any other ProSyst classes.

My understanding is that we are currently not able to put any code
directly into the incubator area. Our case should be covered by Fig.6
of the document at
http://www.eclipse.org/legal/EclipseLegalProcessPoster.pdf, which
means that we need to fill the Contribution Questionnaire on Committer
Tools, to which we do not have access because we do not have a
committer status yet.

Jeff could you help us on this issue (I have already asked for a
committer status for our developers Pavlin Dobrev and Teodor Todorov)?
I can also provide a public link for FTP download and you can then put
the source into the Equinox CVS but I assume that this does not comply
with the defined legal process. How should we proceed?

Dimitar

_______________________________________________
equinox-dev mailing list
equinox-dev-j9T/66MeVpFAfugRpC6u6w@public.gmane.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev

headers

Jeff McAffer | 4 Apr 19:37

VOTE new Equinox services from ProSyst

This is great. As per the process message I just sent, we should poll the community for interest in accepting these contributions. To be clear to the community, the expectation is that Prosyst will be following through here with ongoing service and support for these implementations. The contributions will first go into the Incubator while they are reviewed and massaged. They will then graduate as appropriate into the Bundles component.

Please cast your votes on this list.

Jeff

Dimitar Valtchev <d.valtchev-gIMOvL9Iw+9BDgjK7y7TUQ@public.gmane.org>
Sent by: equinox-dev-bounces-j9T/66MeVpFAfugRpC6u6w@public.gmane.org

04/03/2007 09:26 AM

Please respond to
Equinox development mailing list <equinox-dev-j9T/66MeVpFAfugRpC6u6w@public.gmane.org>

To	equinox-dev-j9T/66MeVpFAfugRpC6u6w@public.gmane.org
cc
Subject	[equinox-dev] new Equinox services from ProSyst

We are now ready with the source code of our OSGi services which we
will contribute to Equinox. These are:

- Implementation of OSGi Declarative Services Specification
- Implementation of OSGi IO Connector Service Specification
- Implementation of OSGi Initial Provisioning
- Implementation of OSGi Wire Admin Service Specification

We have done the following:

-all class packages have now names in the Eclipse namespace;
-all common utility classes used in the implementation of the services
above are packed in a separated bundle (util.jar) which is also
available under EPL and uses the Eclipse namespace;
-there are no dependencies on any other ProSyst classes.

My understanding is that we are currently not able to put any code
directly into the incubator area. Our case should be covered by Fig.6
of the document at
http://www.eclipse.org/legal/EclipseLegalProcessPoster.pdf, which
means that we need to fill the Contribution Questionnaire on Committer
Tools, to which we do not have access because we do not have a
committer status yet.

Jeff could you help us on this issue (I have already asked for a
committer status for our developers Pavlin Dobrev and Teodor Todorov)?
I can also provide a public link for FTP download and you can then put
the source into the Equinox CVS but I assume that this does not comply
with the defined legal process. How should we proceed?

Dimitar

_______________________________________________
equinox-dev mailing list
equinox-dev-j9T/66MeVpFAfugRpC6u6w@public.gmane.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev

headers

Pascal Rapicault | 4 Apr 19:48

Re: VOTE new Equinox services from ProSyst

+1

                                                                           
             Jeff                                                          
             McAffer/Ottawa/IB                                             
             M <at> IBMCA                                                    To 
             Sent by:                  Equinox development mailing list    
             equinox-dev-bounc         <equinox-dev@...>           
             es@...                                             cc 

                                                                   Subject 
             04/04/2007 01:37          [equinox-dev] VOTE new Equinox      
             PM                        services from ProSyst               

                                                                           
             Please respond to                                             
                  Equinox                                                  
                development                                                
               mailing list                                                
             <equinox-dev <at> ecli                                             
                 pse.org>                                                  

This is great.  As per the process message I just sent, we should poll the
community for interest in accepting these contributions.  To be clear to
the community, the expectation is that Prosyst will be following through
here with ongoing service and support for these implementations.  The
contributions will first go into the Incubator while they are reviewed and
massaged.  They will then graduate as appropriate into the Bundles
component.

Please cast your votes on this list.

Jeff

                                                                           
 Dimitar Valtchev                                                          
 <d.valtchev@...>                                                  
 Sent by:                                                               To 
 equinox-dev-bounces@...                 
equinox-dev@...  
                                                                        cc 

 04/03/2007 09:26 AM                                               Subject 
                                                  [equinox-dev] new        
                                                  Equinox services from    
           Please respond to                      ProSyst                  
    Equinox development mailing list                                       
       <equinox-dev@...>                                           

We are now ready with the source code of our OSGi services which we
will contribute to Equinox. These are:

- Implementation of OSGi Declarative Services Specification
- Implementation of OSGi IO Connector Service Specification
- Implementation of OSGi Initial Provisioning
- Implementation of OSGi Wire Admin Service Specification

We have done the following:

-all class packages have now names in the Eclipse namespace;
-all common utility classes used in the implementation of the services
above are packed in a separated bundle (util.jar) which is also
available under EPL and uses the Eclipse namespace;
-there are no dependencies on any other ProSyst classes.

My understanding is that we are currently not able to put any code
directly into the incubator area. Our case should be covered by Fig.6
of the document at
http://www.eclipse.org/legal/EclipseLegalProcessPoster.pdf, which
means that we need to fill the Contribution Questionnaire on Committer
Tools, to which we do not have access because we do not have a
committer status yet.

Jeff could you help us on this issue (I have already asked for a
committer status for our developers Pavlin Dobrev and Teodor Todorov)?
I can also provide a public link for FTP download and you can then put
the source into the Equinox CVS but I assume that this does not comply
with the defined legal process. How should we proceed?

Dimitar

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

headers

Simon Kaegi | 4 Apr 19:48

Re: VOTE new Equinox services from ProSyst

+1

equinox-dev-bounces@... wrote on 04/04/2007 01:37:11 PM:

>
> This is great.  As per the process message I just sent, we should
> poll the community for interest in accepting these contributions.
> To be clear to the community, the expectation is that Prosyst will
> be following through here with ongoing service and support for these
> implementations.  The contributions will first go into the Incubator
> while they are reviewed and massaged.  They will then graduate as
> appropriate into the Bundles component.
>
> Please cast your votes on this list.
>
> Jeff
>
>

>
> Dimitar Valtchev <d.valtchev@...>
> Sent by: equinox-dev-bounces@...
> 04/03/2007 09:26 AM
>
> Please respond to
> Equinox development mailing list <equinox-dev@...>
>
> To
>
> equinox-dev@...
>
> cc
>
> Subject
>
> [equinox-dev] new Equinox services from ProSyst
>
>
>
>
> We are now ready with the source code of our OSGi services which we
> will contribute to Equinox. These are:
>
> - Implementation of OSGi Declarative Services Specification
> - Implementation of OSGi IO Connector Service Specification
> - Implementation of OSGi Initial Provisioning
> - Implementation of OSGi Wire Admin Service Specification
>
> We have done the following:
>
> -all class packages have now names in the Eclipse namespace;
> -all common utility classes used in the implementation of the services
> above are packed in a separated bundle (util.jar) which is also
> available under EPL and uses the Eclipse namespace;
> -there are no dependencies on any other ProSyst classes.
>
> My understanding is that we are currently not able to put any code
> directly into the incubator area. Our case should be covered by Fig.6
> of the document at
> http://www.eclipse.org/legal/EclipseLegalProcessPoster.pdf, which
> means that we need to fill the Contribution Questionnaire on Committer
> Tools, to which we do not have access because we do not have a
> committer status yet.
>
> Jeff could you help us on this issue (I have already asked for a
> committer status for our developers Pavlin Dobrev and Teodor Todorov)?
> I can also provide a public link for FTP download and you can then put
> the source into the Equinox CVS but I assume that this does not comply
> with the defined legal process. How should we proceed?
>
> Dimitar
>
> _______________________________________________
> equinox-dev mailing list
> equinox-dev@...
> https://dev.eclipse.org/mailman/listinfo/equinox-dev
> _______________________________________________
> equinox-dev mailing list
> equinox-dev@...
> https://dev.eclipse.org/mailman/listinfo/equinox-dev

9	February 2012
14	January 2012
19	December 2011
3	November 2011
27	October 2011
24	September 2011
49	August 2011
24	July 2011
49	June 2011
49	May 2011
59	April 2011
57	March 2011
46	February 2011
28	January 2011
47	December 2010
50	November 2010
30	October 2010
51	September 2010
21	August 2010
16	July 2010
70	June 2010
20	May 2010
80	April 2010
57	March 2010
37	February 2010
54	January 2010
62	December 2009
34	November 2009
50	October 2009
76	September 2009
71	August 2009
52	July 2009
107	June 2009
94	May 2009
121	April 2009
71	March 2009
77	February 2009
97	January 2009
35	December 2008
58	November 2008
116	October 2008
126	September 2008
57	August 2008
134	July 2008
193	June 2008
190	May 2008
207	April 2008
201	March 2008
215	February 2008
151	January 2008
96	December 2007
118	November 2007
203	October 2007
164	September 2007
173	August 2007
128	July 2007
156	June 2007
152	May 2007
93	April 2007
121	March 2007
180	February 2007
74	January 2007
48	December 2006
139	November 2006
110	October 2006
63	September 2006
37	August 2006
89	July 2006
143	June 2006
71	May 2006
51	April 2006
103	March 2006
114	February 2006
64	January 2006
42	December 2005
82	November 2005