Home » Eclipse Projects » Plugin Development Environment (PDE) » Running the project builders when headless
| Running the project builders when headless [message #46585] |
Wed, 11 February 2009 08:10  |
Eclipse User |
|
|
|
Hi!
Could someone please explain why it isn't possible to run the normal
builders for a project when doing it headless? I have plugins that use
other languages than Java and in order to be able to build them from Ant I
have to write a different builder.
Given that it's not all that straightforward to get headless build anyway
(messing with all the pre- and post- targets to get the other languages
compiled), I am even considering to have a full Eclipse instance
remote-controlled (through a socket, for example) so that it can work as a
build server. Is it a crazy idea?
best regards,
Vlad
|
|
| |
| Re: Running the project builders when headless [message #47011 is a reply to message #46768] |
Sat, 14 February 2009 09:16  |
| Eclipse User |
|
|
|
Hi,
Prakash G.R. wrote:
> Eclipse framework doesn't mandate UI for builders. If a third party builder
> depends on UI, I would suggest to raise a bug against them.
The builder in question is the one provided by my plugin. My plugins are
also self-hosting, containing not only Java code.
The PDE build process uses ant targets to compile code, the only (if I
didn't get it all wrong) connection with eclipse is the ability to read
and handle workspace and project settings so that the Java compiler gets
configured properly.
This ability may or may not be available to other ant targets (I didn't
get that far), but even so, one has to maintain two different builders.
> Its not that tough to create a app in Eclipse that does all the compilation.
> I've created one some time back, which would invoke both Java compiler and
> GWT compiler in headless mode.
I will look at that, it seems to be similar with what I have in mind.
Thanks!
regards,
Vlad
|
|
|
| Re: Running the project builders when headless [message #47042 is a reply to message #47011] |
Mon, 16 February 2009 02:53 |
| Eclipse User |
|
|
|
> The builder in question is the one provided by my plugin. My plugins are
> also self-hosting, containing not only Java code.
Does that plugin depends on org.eclipse.ui?
- Prakash
--
http://blog.eclipse-tips.com
"Vlad Dumitrescu" <vladdu55@gmail.com> wrote in message
news:33df28564a19fde96cdb0a36ea7203e3$1@www.eclipse.org...
> Hi,
>
> Prakash G.R. wrote:
>> Eclipse framework doesn't mandate UI for builders. If a third party
>> builder depends on UI, I would suggest to raise a bug against them.
>
> The builder in question is the one provided by my plugin. My plugins are
> also self-hosting, containing not only Java code.
> The PDE build process uses ant targets to compile code, the only (if I
> didn't get it all wrong) connection with eclipse is the ability to read
> and handle workspace and project settings so that the Java compiler gets
> configured properly.
>
> This ability may or may not be available to other ant targets (I didn't
> get that far), but even so, one has to maintain two different builders.
>
>> Its not that tough to create a app in Eclipse that does all the
>> compilation. I've created one some time back, which would invoke both
>> Java compiler and GWT compiler in headless mode.
>
> I will look at that, it seems to be similar with what I have in mind.
> Thanks!
>
> regards,
> Vlad
>
>
>
|
|
|
| Re: Running the project builders when headless [message #47071 is a reply to message #47042] |
Mon, 16 February 2009 03:49 |
| Eclipse User |
|
|
|
Prakash G.R. wrote:
>> The builder in question is the one provided by my plugin. My plugins are
>> also self-hosting, containing not only Java code.
> Does that plugin depends on org.eclipse.ui?
No, the core plugin doesn't depend on the ui.
So yes, it is possible to write an application that will open a workspace,
fetch the sources and start a build. Not all the necessary APIs are
public, but I guess it would help to check the Buckminster code.
The part that I am still unsure about is if I can do all the PDE packaging
stuff from inside Eclipse.
Thank you for the suggestion, I was probably going to go with a much more
complicated solution.
regards,
Vlad
|
|
| |
| Re: Running the project builders when headless [message #591997 is a reply to message #46768] |
Sat, 14 February 2009 09:16 |
| Eclipse User |
|
|
|
Hi,
Prakash G.R. wrote:
> Eclipse framework doesn't mandate UI for builders. If a third party builder
> depends on UI, I would suggest to raise a bug against them.
The builder in question is the one provided by my plugin. My plugins are
also self-hosting, containing not only Java code.
The PDE build process uses ant targets to compile code, the only (if I
didn't get it all wrong) connection with eclipse is the ability to read
and handle workspace and project settings so that the Java compiler gets
configured properly.
This ability may or may not be available to other ant targets (I didn't
get that far), but even so, one has to maintain two different builders.
> Its not that tough to create a app in Eclipse that does all the compilation.
> I've created one some time back, which would invoke both Java compiler and
> GWT compiler in headless mode.
I will look at that, it seems to be similar with what I have in mind.
Thanks!
regards,
Vlad
|
|
|
| Re: Running the project builders when headless [message #592003 is a reply to message #47011] |
Mon, 16 February 2009 02:53 |
| Eclipse User |
|
|
|
> The builder in question is the one provided by my plugin. My plugins are
> also self-hosting, containing not only Java code.
Does that plugin depends on org.eclipse.ui?
- Prakash
--
http://blog.eclipse-tips.com
"Vlad Dumitrescu" <vladdu55@gmail.com> wrote in message
news:33df28564a19fde96cdb0a36ea7203e3$1@www.eclipse.org...
> Hi,
>
> Prakash G.R. wrote:
>> Eclipse framework doesn't mandate UI for builders. If a third party
>> builder depends on UI, I would suggest to raise a bug against them.
>
> The builder in question is the one provided by my plugin. My plugins are
> also self-hosting, containing not only Java code.
> The PDE build process uses ant targets to compile code, the only (if I
> didn't get it all wrong) connection with eclipse is the ability to read
> and handle workspace and project settings so that the Java compiler gets
> configured properly.
>
> This ability may or may not be available to other ant targets (I didn't
> get that far), but even so, one has to maintain two different builders.
>
>> Its not that tough to create a app in Eclipse that does all the
>> compilation. I've created one some time back, which would invoke both
>> Java compiler and GWT compiler in headless mode.
>
> I will look at that, it seems to be similar with what I have in mind.
> Thanks!
>
> regards,
> Vlad
>
>
>
|
|
|
| Re: Running the project builders when headless [message #592011 is a reply to message #47042] |
Mon, 16 February 2009 03:49 |
| Eclipse User |
|
|
|
Prakash G.R. wrote:
>> The builder in question is the one provided by my plugin. My plugins are
>> also self-hosting, containing not only Java code.
> Does that plugin depends on org.eclipse.ui?
No, the core plugin doesn't depend on the ui.
So yes, it is possible to write an application that will open a workspace,
fetch the sources and start a build. Not all the necessary APIs are
public, but I guess it would help to check the Buckminster code.
The part that I am still unsure about is if I can do all the PDE packaging
stuff from inside Eclipse.
Thank you for the suggestion, I was probably going to go with a much more
complicated solution.
regards,
Vlad
|
|
|
Goto Forum:
Current Time: Sun Jun 08 13:34:34 EDT 2025
Powered by FUDForum. Page generated in 0.04238 seconds |
Home