Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » Buckminster » Any experience using buckminster and AspectJ?
Any experience using buckminster and AspectJ? [message #502616] Wed, 09 December 2009 07:43 Go to next message
Alain  is currently offline Alain Friend
Messages: 115
Registered: July 2009
Senior Member
Hi

Does anyone have some experience using buckminster to build projects
that use AspectJ?

I read about this bug
https://bugs.eclipse.org/bugs/show_bug.cgi?id=252641 that explains a
possible workaround for headless pde builds.

But did this also works for buckminster?

Thanks for any response,
Alain.
Re: Any experience using buckminster and AspectJ? [message #502622 is a reply to message #502616] Wed, 09 December 2009 08:07 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas HallgrenFriend
Messages: 3240
Registered: July 2009
Senior Member
Hi Alain,
The general rule of thumb when using Buckminster is that if you can build it in your IDE, you should be able to build
the same thing headlessly. Your workspace is built the same way regardless. Are you encountering any specific problems?

Regards,
Thomas Hallgren


On 2009-12-09 08:43, Alain Helfenstein wrote:
> Hi
>
> Does anyone have some experience using buckminster to build projects
> that use AspectJ?
>
> I read about this bug
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=252641 that explains a
> possible workaround for headless pde builds.
>
> But did this also works for buckminster?
>
> Thanks for any response,
> Alain.
Re: Any experience using buckminster and AspectJ? [message #502635 is a reply to message #502622] Wed, 09 December 2009 08:54 Go to previous messageGo to next message
Alain  is currently offline Alain Friend
Messages: 115
Registered: July 2009
Senior Member
Hi Thomas,
thanks a lot for your answer.

In the IDE, I have installed the AJDT feature that exports a builder for
the projects that uses AspectJ.
In the .project file we have now the following lines that replaces the
"org.eclipse.jdt.core.javabuilder" buildCommand:

<buildCommand>
<name>org.eclipse.ajdt.core.ajbuilder</name>
<arguments>
</arguments>
</buildCommand>

But for the headless buckminster build, a headless ajbuilder is missing.
There is a workaround for headless pde build. But I'm not shure if I can
use the same workaround for the buckminster build.

The steps to follow in order to implement the workaround are as follows
(see https://bugs.eclipse.org/bugs/show_bug.cgi?id=252641):
1. unzip the plugin into your eclipse/dropins directory.
2. run eclipse once so that this plugin is recognized and installed by
the P2
installer
3. in your headless build script, make sure that the eclipse antrunner
points
to the org.eclipse.ajdt.pde.build/scripts/build.xml ant script
4. ensure that the following property is available to ant:
ajdt.pdebuild.home =
<path_to_ajdt.pde_plugin> (you can add this as a vm arg to
-Dajdt.pdebuild.home=<path_to_ajdt.pde_plugin>)
5. run your build script

How to implement the point 3 if I want to use buckminster?

So my question was, if anybody have already solved this issue.

Kind regards,
Alain.

Thomas Hallgren schrieb:
> Hi Alain,
> The general rule of thumb when using Buckminster is that if you can
> build it in your IDE, you should be able to build the same thing
> headlessly. Your workspace is built the same way regardless. Are you
> encountering any specific problems?
>
> Regards,
> Thomas Hallgren
>
>
> On 2009-12-09 08:43, Alain Helfenstein wrote:
>> Hi
>>
>> Does anyone have some experience using buckminster to build projects
>> that use AspectJ?
>>
>> I read about this bug
>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=252641 that explains a
>> possible workaround for headless pde builds.
>>
>> But did this also works for buckminster?
>>
>> Thanks for any response,
>> Alain.
>
Re: Any experience using buckminster and AspectJ? [message #502641 is a reply to message #502635] Wed, 09 December 2009 09:22 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas HallgrenFriend
Messages: 3240
Registered: July 2009
Senior Member
Hi Alain,
I'm trying to understand why you would need a workaround in the first place. When using Buckminster, you won't run into
any limitations that might exist when you run a PDE build headlessly.

So if you have your build running in your IDE, perhaps you should just try and run it headlessly with Buckminster and
see if it works. If it doesn't, then we can take it from there.

Regards,
Thomas Hallgren
Re: Any experience using buckminster and AspectJ? [message #502765 is a reply to message #502641] Wed, 09 December 2009 16:15 Go to previous messageGo to next message
Alain  is currently offline Alain Friend
Messages: 115
Registered: July 2009
Senior Member
Hi Thomas

Thanks for your answer.

As far as I see the problem is as follows:

1. I can't install the original AJDT plugin (that i use in my IDE) into
a hedless environment, because if I do so, a exception will be thrown,
that the SWTException class is missing.

2. Instead of that, I install the "org.eclipse.ajdt.pde.build" plugin
that, do to the description, supports the build of aspectj plugins
headlessly.

3. Because the projects (using aspectj) does not have a
org.eclipse.jdt.core.javabuilder build-command no classes will be built
using a default headless installation (whitout
org.eclipse.jdt.core.javabuilder).
As effect, simply the class can not be found e.g. "NameProvider cannot
be resolved"

4. That the plugin org.eclipse.jdt.core.javabuilder takes effect, the
documentation sais, that I should make shure, that the eclipse antrunner
points to the org.eclipse.ajdt.pde.build/scripts/build.xml ant script.

And now the question: How to do this for buckminster?

Thanks for your response,
Alain.
Re: Any experience using buckminster and AspectJ? [message #502796 is a reply to message #502765] Wed, 09 December 2009 17:39 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas HallgrenFriend
Messages: 3240
Registered: July 2009
Senior Member
Hi Alain,
Please install the org.eclipse.buckminster.pde.headless.feature into your headless buckminster. It contains the javabuilder.

I don't know what the build.xml in question does, or where it's supposed to get called from, so I cannot advice on #4.

Regards,
Thomas Hallgren



On 2009-12-09 17:15, Alain Helfenstein wrote:
> Hi Thomas
>
> Thanks for your answer.
>
> As far as I see the problem is as follows:
>
> 1. I can't install the original AJDT plugin (that i use in my IDE) into
> a hedless environment, because if I do so, a exception will be thrown,
> that the SWTException class is missing.
>
> 2. Instead of that, I install the "org.eclipse.ajdt.pde.build" plugin
> that, do to the description, supports the build of aspectj plugins
> headlessly.
>
> 3. Because the projects (using aspectj) does not have a
> org.eclipse.jdt.core.javabuilder build-command no classes will be built
> using a default headless installation (whitout
> org.eclipse.jdt.core.javabuilder).
> As effect, simply the class can not be found e.g. "NameProvider cannot
> be resolved"
>
> 4. That the plugin org.eclipse.jdt.core.javabuilder takes effect, the
> documentation sais, that I should make shure, that the eclipse antrunner
> points to the org.eclipse.ajdt.pde.build/scripts/build.xml ant script.
>
> And now the question: How to do this for buckminster?
>
> Thanks for your response,
> Alain.
Re: Any experience using buckminster and AspectJ? [message #502969 is a reply to message #502616] Thu, 10 December 2009 13:33 Go to previous messageGo to next message
Alain  is currently offline Alain Friend
Messages: 115
Registered: July 2009
Senior Member
Hi Thomas

I give it another try.

The documentation of the headless AJDT (AspectJ) sais, that you should
install the org.eclipse.ajdt.pde.build plugin into your headless pde
build environment.

Then you should change the main entry point of the eclipse ant runner to
the org.eclipse.ajdt.pde.build/scripts/build.xml script instead of the
org.eclipse.pde.build/scripts/build.xml

But is it right, that buckminster does not call the
org.eclipse.pde.build/scripts/build.xml?

Thanks for your answer,
Alain.
Re: Any experience using buckminster and AspectJ? [message #502981 is a reply to message #502969] Thu, 10 December 2009 14:08 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas HallgrenFriend
Messages: 3240
Registered: July 2009
Senior Member
On 2009-12-10 14:33, Alain Helfenstein wrote:
> Hi Thomas
>
> I give it another try.
>
> The documentation of the headless AJDT (AspectJ) sais, that you should
> install the org.eclipse.ajdt.pde.build plugin into your headless pde
> build environment.
>
> Then you should change the main entry point of the eclipse ant runner to
> the org.eclipse.ajdt.pde.build/scripts/build.xml script instead of the
> org.eclipse.pde.build/scripts/build.xml
>
> But is it right, that buckminster does not call the
> org.eclipse.pde.build/scripts/build.xml?
>
That's right. Buckminster will not call that. We just build as you normally would build when you have the workspace in
the IDE. No special tricks are used in a headless environment.

- thomas
Re: Any experience using buckminster and AspectJ? [message #503443 is a reply to message #502616] Mon, 14 December 2009 03:32 Go to previous message
Alain  is currently offline Alain Friend
Messages: 115
Registered: July 2009
Senior Member
Hi.

It seams, that the AspectJ developpment team must supply a feature, that
implements its AJDT builder headlessly. I opened a Issue on the
"bugs.eclipse.org" for that:

Bug 297713 - AJDT for Headless Buckminster build process

It would be very kind, if the Buckminster dev-team could support the
AJDT-dev team in resolving this issue.

Thenks for your help,
Alain.
Previous Topic:Wildcard in local provider
Next Topic:git connector for Buckminster
Goto Forum:
  


Current Time: Fri Apr 19 22:35:02 GMT 2024

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

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

Back to the top