Skip to main content



      Home
Home » Eclipse Projects » Eclipse Platform » General understanding
General understanding [message #16681] Sat, 26 April 2003 10:12 Go to next message
Eclipse UserFriend
Originally posted by: frankc.colconsulting.com

Are plug-in scoped specifically to projects or are they "available and
active" across all types of projects?

--
---
Frank V. Castellucci
Re: General understanding [message #17566 is a reply to message #16681] Sat, 26 April 2003 18:12 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: pascal_rapicault.yahoo.fr

At development time, there is no special scope for plugins. Plugins are
considered as java projects, so you need to be careful to not reference code
that is in a project that will not be in your runtime environment.

hth,

PaScaL

"Frank V. Castellucci" <frankc@colconsulting.com> a
Re: General understanding [message #20613 is a reply to message #16681] Mon, 28 April 2003 19:09 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: John_Arthorne.oti.com_

At runtime, plugins are usually associated with a project via a project
nature. Generally, plugins only work with projects which have their
nature. For example, java tooling only operates on java projects. See
the eclipse.org article on builders and natures for more information.
--

Frank V. Castellucci wrote:
> Are plug-in scoped specifically to projects or are they "available and
> active" across all types of projects?
>
> --
> ---
> Frank V. Castellucci
>
>
Re: General understanding [message #22767 is a reply to message #20613] Tue, 29 April 2003 14:01 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: bob.objfac.com

Generally? Currently, natures are only useful for participating in the build
process. Plugins that don't usually don't pay any attention to natures.

Bob

"John Arthorne" <John_Arthorne@oti.com_> wrote in message
news:3EADB4AE.3050604@oti.com_...
> At runtime, plugins are usually associated with a project via a project
> nature. Generally, plugins only work with projects which have their
> nature. For example, java tooling only operates on java projects. See
> the eclipse.org article on builders and natures for more information.
> --
>
> Frank V. Castellucci wrote:
> > Are plug-in scoped specifically to projects or are they "available and
> > active" across all types of projects?
> >
> > --
> > ---
> > Frank V. Castellucci
> >
> >
>
Re: General understanding [message #23764 is a reply to message #22767] Wed, 30 April 2003 10:14 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: John_Arthorne.oti.com_

Well, it depends on the plugin. The plugins in the Eclipse SDK
generally only operate on plugins of their own nature. The java model
is built on all projects with the java nature, as an example. Java
search will only find types in java projects, etc. However, the java
editor will do syntax coloring on *.java files that are not in java
projects. A better answer to the original question would be: natures
can be used as a way of scoping the working set for a given plugin or
feature, although this is not enforced in any way.
--


Bob Foster wrote:
> Generally? Currently, natures are only useful for participating in the build
> process. Plugins that don't usually don't pay any attention to natures.
>
> Bob
>
> "John Arthorne" <John_Arthorne@oti.com_> wrote in message
> news:3EADB4AE.3050604@oti.com_...
>
>>At runtime, plugins are usually associated with a project via a project
>>nature. Generally, plugins only work with projects which have their
>>nature. For example, java tooling only operates on java projects. See
>>the eclipse.org article on builders and natures for more information.
>>--
>>
>>Frank V. Castellucci wrote:
>>
>>>Are plug-in scoped specifically to projects or are they "available and
>>>active" across all types of projects?
>>>
>>>--
>>>---
>>>Frank V. Castellucci
>>>
>>>
>>
>
>
Re: General understanding [message #29707 is a reply to message #20613] Sat, 10 May 2003 10:08 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: frankc.colconsulting.com

So,

If I create a plug-in that accesses EMF models, I can realize the
information in ALL EMF models in eclipse and not limited to project by
project.
Is this correct?

Frank V. Castellucci

"John Arthorne" <John_Arthorne@oti.com_> wrote in message
news:3EADB4AE.3050604@oti.com_...
> At runtime, plugins are usually associated with a project via a
project
> nature. Generally, plugins only work with projects which have their
> nature. For example, java tooling only operates on java projects.
See
> the eclipse.org article on builders and natures for more information.
> --
>
> Frank V. Castellucci wrote:
> > Are plug-in scoped specifically to projects or are they "available
and
> > active" across all types of projects?
> >
> > --
> > ---
> > Frank V. Castellucci
> >
> >
>
Re: General understanding [message #31685 is a reply to message #29707] Wed, 14 May 2003 11:13 Go to previous message
Eclipse UserFriend
Originally posted by: John_Arthorne.oti.com_

I don't know anything about EMF. Perhaps you can ask about the behaviour
of EMF models on the eclipse.tools.emf newsgroup.
--


Frank V. Castellucci wrote:
> So,
>
> If I create a plug-in that accesses EMF models, I can realize the
> information in ALL EMF models in eclipse and not limited to project by
> project.
> Is this correct?
>
Previous Topic:Setting Global Selection
Next Topic:Path to IFolder
Goto Forum:
  


Current Time: Wed Jul 16 18:17:01 EDT 2025

Powered by FUDForum. Page generated in 0.02903 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top