| Assosiating a Builder to a Nature [message #187693] |
Thu, 11 January 2007 13:29  |
Eclipse User |
|
|
|
Originally posted by: martin.tauber.t-online.de
Hello everybody!
I am developing an application using projects which contain files which
need to be compiled. The compilers should be provided by plugins. I took
a closer look at natures and builders and at a first glance they are
providing what I'm looking for. But ...
I can create a project and assosiate a nature to it. Now I would like to
create a plugin including a builder and assosiate it to the nature. I
don't see a way of doing this.
I saw the way that I can assosiate a builder to a nature using the
nature builder attribute when declaring the plugin extension, but this
is not what I want. During nature declaration the nature has no idea
what builders will be assosiated to it, since the builders are defined
in the plugins (extensions).
Does anyone have any ideas?
Thanks
|
|
|
| Re: Assosiating a Builder to a Nature [message #187710 is a reply to message #187693] |
Thu, 11 January 2007 15:33  |
| Eclipse User |
|
|
|
Originally posted by: wegener.cboenospam.com
Martin Tauber wrote:
> Hello everybody!
> I am developing an application using projects which contain files which
> need to be compiled. The compilers should be provided by plugins. I took
> a closer look at natures and builders and at a first glance they are
> providing what I'm looking for. But ...
> I can create a project and assosiate a nature to it. Now I would like to
> create a plugin including a builder and assosiate it to the nature. I
> don't see a way of doing this.
> I saw the way that I can assosiate a builder to a nature using the
> nature builder attribute when declaring the plugin extension, but this
> is not what I want. During nature declaration the nature has no idea
> what builders will be assosiated to it, since the builders are defined
> in the plugins (extensions).
> Does anyone have any ideas?
> Thanks
Have you read this article yet, it might be of some help.
http://www.eclipse.org/articles/Article-Builders/builders.ht ml
One possible solution would be to define a proxy builder in your plugin.
When your proxy builder is invoked, it could use the plugin repository to
create the defined builders and call them.
|
|
|
| Re: Assosiating a Builder to a Nature [message #187717 is a reply to message #187710] |
Thu, 11 January 2007 16:04 |
| Eclipse User |
|
|
|
Originally posted by: martin.tauber.t-online.de
If you are talking about a proxy builder, you mean that I have one
builder that invokes plugins that I define (with an interface that I
define) ok that is a solution, but I thought this was the whole idea of
natures...
Dave Wegener schrieb:
> Martin Tauber wrote:
>
>> Hello everybody!
>
>> I am developing an application using projects which contain files
>> which need to be compiled. The compilers should be provided by
>> plugins. I took a closer look at natures and builders and at a first
>> glance they are providing what I'm looking for. But ...
>
>> I can create a project and assosiate a nature to it. Now I would like
>> to create a plugin including a builder and assosiate it to the nature.
>> I don't see a way of doing this.
>
>> I saw the way that I can assosiate a builder to a nature using the
>> nature builder attribute when declaring the plugin extension, but this
>> is not what I want. During nature declaration the nature has no idea
>> what builders will be assosiated to it, since the builders are defined
>> in the plugins (extensions).
>
>> Does anyone have any ideas?
>> Thanks
>
> Have you read this article yet, it might be of some help.
> http://www.eclipse.org/articles/Article-Builders/builders.ht ml
>
> One possible solution would be to define a proxy builder in your
> plugin. When your proxy builder is invoked, it could use the plugin
> repository to create the defined builders and call them.
>
|
|
|
| Re: Assosiating a Builder to a Nature [message #187734 is a reply to message #187717] |
Thu, 11 January 2007 21:19 |
| Eclipse User |
|
|
|
Originally posted by: wegener.cboenospam.com
Martin Tauber wrote:
> If you are talking about a proxy builder, you mean that I have one
> builder that invokes plugins that I define (with an interface that I
> define) ok that is a solution, but I thought this was the whole idea of
> natures...
The relationship is from nature to builder not from builder to nature.
The most straight forward way to achieve the relationship is to define the
nature and the builder in the same plugin. However, I don't believe that
this is a requirement. You can define a nature in one plugin and a
builder in another. The builder id reference in the nature definition is
a fully qualified reference to a builder id.
I'm not sure I fully understand what you are trying to do. If you are
writing the application, you have control over the plugins where the
nature and builders are defined. Are there multiple builders for a single
nature? Are you expecting third parties to contribute additional builders
to your nature? If not, why do you need to have the nature defined in a
plugin separate from the builder?
> Dave Wegener schrieb:
>> Martin Tauber wrote:
>>
>>> Hello everybody!
>>
>>> I am developing an application using projects which contain files
>>> which need to be compiled. The compilers should be provided by
>>> plugins. I took a closer look at natures and builders and at a first
>>> glance they are providing what I'm looking for. But ...
>>
>>> I can create a project and assosiate a nature to it. Now I would like
>>> to create a plugin including a builder and assosiate it to the nature.
>>> I don't see a way of doing this.
>>
>>> I saw the way that I can assosiate a builder to a nature using the
>>> nature builder attribute when declaring the plugin extension, but this
>>> is not what I want. During nature declaration the nature has no idea
>>> what builders will be assosiated to it, since the builders are defined
>>> in the plugins (extensions).
>>
>>> Does anyone have any ideas?
>>> Thanks
>>
>> Have you read this article yet, it might be of some help.
>> http://www.eclipse.org/articles/Article-Builders/builders.ht ml
>>
>> One possible solution would be to define a proxy builder in your
>> plugin. When your proxy builder is invoked, it could use the plugin
>> repository to create the defined builders and call them.
>>
|
|
|
| Re: Assosiating a Builder to a Nature [message #187758 is a reply to message #187734] |
Fri, 12 January 2007 11:49 |
| Eclipse User |
|
|
|
Originally posted by: martin.tauber.t-online.de
Hi Dave,
somehow I don't see the point of having a relation from the nature to
the builder. I still think it should be the otherway around. Here is
what I'm trying to achieve:
I want to create an application which stores data in an xml file. This
xml file than should be converted into different formats (like html,
pdf, whatever). The application should provide the framework for
invoking the required builders each one of them copnverting the xml
file. Since I don't know what "whatever" is, I wanted to make the
application so flexible that it could be extended by plugins. So the
nature would be connected to the project and the plugins would connect
the builders to the nature. Then the application would automatically
know what to build. (Maybe some thinks it's cool to have a rtf output).
what is the use of having the relationship from the nature to the
builder? Then I would need to know all the builders beforehead. Why
shouldn't I then connect the builders directly to the project?
Regards
Martin
Dave Wegener schrieb:
> Martin Tauber wrote:
>
>> If you are talking about a proxy builder, you mean that I have one
>> builder that invokes plugins that I define (with an interface that I
>> define) ok that is a solution, but I thought this was the whole idea
>> of natures...
>
> The relationship is from nature to builder not from builder to nature.
> The most straight forward way to achieve the relationship is to define
> the nature and the builder in the same plugin. However, I don't believe
> that this is a requirement. You can define a nature in one plugin and a
> builder in another. The builder id reference in the nature definition
> is a fully qualified reference to a builder id.
>
> I'm not sure I fully understand what you are trying to do. If you are
> writing the application, you have control over the plugins where the
> nature and builders are defined. Are there multiple builders for a
> single nature? Are you expecting third parties to contribute additional
> builders to your nature? If not, why do you need to have the nature
> defined in a plugin separate from the builder?
>
>
>> Dave Wegener schrieb:
>>> Martin Tauber wrote:
>>>
>>>> Hello everybody!
>>>
>>>> I am developing an application using projects which contain files
>>>> which need to be compiled. The compilers should be provided by
>>>> plugins. I took a closer look at natures and builders and at a first
>>>> glance they are providing what I'm looking for. But ...
>>>
>>>> I can create a project and assosiate a nature to it. Now I would
>>>> like to create a plugin including a builder and assosiate it to the
>>>> nature. I don't see a way of doing this.
>>>
>>>> I saw the way that I can assosiate a builder to a nature using the
>>>> nature builder attribute when declaring the plugin extension, but
>>>> this is not what I want. During nature declaration the nature has no
>>>> idea what builders will be assosiated to it, since the builders are
>>>> defined in the plugins (extensions).
>>>
>>>> Does anyone have any ideas?
>>>> Thanks
>>>
>>> Have you read this article yet, it might be of some help.
>>> http://www.eclipse.org/articles/Article-Builders/builders.ht ml
>>>
>>> One possible solution would be to define a proxy builder in your
>>> plugin. When your proxy builder is invoked, it could use the plugin
>>> repository to create the defined builders and call them.
>>>
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.08543 seconds
] 
Search
Help
Register
Login
Home
