news.eclipse.rt

[news.eclipse.rt] Re: Basic questions about the Job class

eclipseng@xxxxxxx (John Arthorne) — Wed, 02 Sep 2009 19:28:04 GMT

Sunny wrote:

1. Can I think of org.eclipse.core.runtime.jobs.Job as Java Runnable?

Jobs are similar to Runnable but are connected to a scheduling system that allocates them to threads automatically. In your

2. If I have:
  MyJob1 a = new MyJob1();
  MyJob2 b = new MyJob2();
  MyJob3 c = new MyJob3();
  a.schedule();
  b.schedule();
  c.schedule();
Will a, b, and c be running in the same worker thread sequentially?

They may run either sequentially or concurrently, since you haven't expressed any dependency between these three jobs. For a more detailed answer see the documentation:

http://help.eclipse.org/galileo/topic/org.eclipse.platform.doc.isv/guide/runtime_jobs.htm

John

[news.eclipse.rt] Basic questions about the Job class

kun.wang@xxxxxxx (Sunny ) — Wed, 26 Aug 2009 02:40:14 GMT

Hi,

I am new to the Eclipse Job API and have a few basic questions.

1. Can I think of org.eclipse.core.runtime.jobs.Job as Java Runnable?

2. If I have:

  MyJob1 a = new MyJob1();
  MyJob2 b = new MyJob2();
  MyJob3 c = new MyJob3();
  a.schedule();
  b.schedule();
  c.schedule();

Will a, b, and c be running in the same worker thread sequentially? Or will they be running in 3 threads in parallel? If the former is true, what is the general mechanism to run different jobs in different threads parallelly? Can you please give an example?

Thanks in advance!

Sunny

[news.eclipse.rt] equinox experience reports

ian.skerrett@xxxxxxx (Ian Skerrett) — Tue, 18 Aug 2009 15:03:49 GMT

We are beginning to organize two EclipseRT Days in Austin and Toronto.  The 
goal of the EclipseRT Day is to share best practices of using Equinox and 
the associated EclipseRT technology, like RAP, EclipseLink, RCP, etc.   As 
part of the agenda we would like to have a number of end-user experience 
reports.

If you work at an end-user organization, building Equinox based applications 
and would like to share your experiences, please get in touch with me at ian 
DOT skerrett AT eclipse DOT org.

Thanks
Ian

[news.eclipse.rt] PDE API Tools

warren_paul@xxxxxxx (Paul Warren) — Thu, 25 Jun 2009 16:21:52 GMT

Hi Folks,

Apologies for the cross post.  I tried posting to eclipse.pde but I was not
authorized to do so.

I'm trialling the pde api tools for use within our organization and I'm
seeing some behavior that I dont understand.  Hopefully someone will be able
to explain the rational.

I have a reference plugin v1.0.0 (my baseline)

I have a separate identical copy of that plugin imported into my workspace
(the working copy).

I create a baseline using the reference copy.

I enable the working copy for api analysis.

And I immediately get an error stating:-

"The minor version should be incremented in version 1.0.0.qualifier, since
new APIs have been added since version 1.0.0.qualifier."

But I havent yet changed the plugin at all.

I would not expect this sort of error to appear until I make the first
change.  Is this an incorrect expectation?  If so, why?

Mnay thanks
_Paul

[news.eclipse.rt] Re: org.eclipse.core.runtime.compatibility.registry

obesedin@xxxxxxx (Oleg Besedin) — Mon, 22 Jun 2009 17:36:51 GMT

This fragment uses a classpath trick to replace some of the class files in 
its host. That only work with unzipped bundles.

I'd say if the application needs the 
org.eclipse.core.runtime.compatibility.registry fragment, then that fragment 
has to be supplied as a folder. However, not all bundles need it, so if you 
are dealing with a "closed" set of plugins, then you can test/update those 
plugins to the point where they don't need compatibility fragment.

Sincerely,
Oleg Besedin

"Paul Warren"  wrote in message 
news:h1o2su$p3$1@xxxxxxxxxxxxxxxxxxxx
> Hi Folks,
>
> I've done a bit of googling but cant find any specific 
> reasons/justifications for this.
>
> I'm trying to work out why org.eclipse.core.runtime.compatibility.registry 
> is deployed as a folder as opposed to a jar.
>
> Some internal customers for a servletbridge-based product are asking me if 
> we can deploy this frgament as a jar.  Is this possible or is there a 
> reason why it is unpacked to a folder?
>
> Many thanks
> _Paul
>
>
>
>
>

[news.eclipse.rt] org.eclipse.core.runtime.compatibility.registry

warren_paul@xxxxxxx (Paul Warren) — Mon, 22 Jun 2009 14:02:05 GMT

Hi Folks,

I've done a bit of googling but cant find any specific 
reasons/justifications for this.

I'm trying to work out why org.eclipse.core.runtime.compatibility.registry 
is deployed as a folder as opposed to a jar.

Some internal customers for a servletbridge-based product are asking me if 
we can deploy this frgament as a jar.  Is this possible or is there a reason 
why it is unpacked to a folder?

Many thanks
_Paul

[news.eclipse.rt] Starting eclipse with Java in the same JVM

markus.oley@xxxxxxx (Markus Oley) — Fri, 29 May 2009 08:29:06 GMT

Hi you,

I have somewhere in my filesystem a path a eclipse-installation.

I want to start this new eclipse in a Javaprogram. I also want eclipse to use the same VM as the Javaprogram in which I start.

How can I do this?

[news.eclipse.rt] Re: Missing class "org.eclipse.core.runtime.IStatus"

mikegr@xxxxxxx (Michael Greifeneder) — Sun, 19 Apr 2009 22:49:17 GMT

Hello,

I found the class in plugin org.eclipse.equinox.common. I looked for the class a long time before I wrote the question, but found it soon after I sent it.

Mike

[news.eclipse.rt] Missing class "org.eclipse.core.runtime.IStatus"

mikegr@xxxxxxx (Michael Greifeneder) — Sun, 19 Apr 2009 20:17:41 GMT

Hello,

The plugin org.eclipse.core.runtime_3.4.0.v20080512.jar from version Eclipse 3.4.2 doesn't contain a class

org.eclipse.core.runtime.IStatus

I don't know which Eclipse distro I downloaded. But it's definitely not in package RCP binary distriubtion 3.4.2 and 3.4.1 for linux/gtk/x86.

Has it moved or is this a bug? JavaDoc in release 3.4 does mention the class.

Regards,

Mike

[news.eclipse.rt] Any interest in helping standardize eRCP

rogalski@xxxxxxx (Mark Rogalski) — Tue, 10 Feb 2009 19:57:06 GMT

As you may be aware, the OSGi alliance has kicked off a project to 
standardize eRCP. Since eRCP is already an existing project, the effort is 
mostly around making an "official" spec of the eRCP components that are not 
already part of standards, and producing an official test suite that ensures 
compliance to the spec. The goal is to release the completed spec and TCK in 
alignment with release of eRCP 1.3 this coming July.

This should not be a huge effort as most of the spec can already be derived 
from existing JavaDoc and the bulk of the API tests are already in Eclipse. 
The work is to fill in some missing specification text and test cases. The 
standardization group may also influence what new function will be put into 
eRCP 1.3.

Having eRCP be an official standard may ease its adoption with mobile 
service providers who are looking to upgrade from the JME MIDP standard, but 
are leary of going with a non standardized open source project.  Providing 
the missing test cases will also directly help the Eclipse community by 
providing better test coverage for core components. As always, we are 
looking for a few good people to assist with this work so we can keep it on 
schedule. Please let me know if you would like to help or can recommend 
places to post this information where interested parties may see it.

            Thanks,
                  Mark