Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Language IDEs » AJDT » Buildconfig package
Buildconfig package [message #67083] Thu, 05 October 2006 10:24 Go to next message
Michael Pisula is currently offline Michael Pisula
Messages: 16
Registered: July 2009
Junior Member
Hello,

I am trying to migrate an application from Eclipse 3.0 to 3.2. However I
ran into some problems with AJDT there. The program uses some classes
from the buildconfig package, which was moved into a new plugin as I
found out. However, this plugin was nowhere to be found. Has anyone got
a clue where to find it, or what to use instead of these classes?

Sincerly,
Michael
Re: Buildconfig package [message #67093 is a reply to message #67083] Thu, 05 October 2006 11:13 Go to previous messageGo to next message
Matt Chapman is currently offline Matt Chapman
Messages: 429
Registered: July 2009
Senior Member
Michael,

Yes, a lot changed in the area of build configurations between AJDT 1.2
and AJDT 1.4. There is no longer any buildconfig package or plugin.
Essentially AJDT now uses the JDT build path mechanism to
include/exclude files from the build. There is however still some
support for applying and saving build configurations in .ajproperties
files. This can be found in the org.eclipse.ajdt.ui.buildpath package.

If you still have problems, please explain what the program was using
the old classes to do exactly, and I can then try to suggest a migration
approach.

Regards,

Matt.

Michael Pisula wrote:
> Hello,
>
> I am trying to migrate an application from Eclipse 3.0 to 3.2. However I
> ran into some problems with AJDT there. The program uses some classes
> from the buildconfig package, which was moved into a new plugin as I
> found out. However, this plugin was nowhere to be found. Has anyone got
> a clue where to find it, or what to use instead of these classes?
>
> Sincerly,
> Michael
Re: Buildconfig package [message #67379 is a reply to message #67093] Wed, 25 October 2006 13:02 Go to previous messageGo to next message
Michael Pisula is currently offline Michael Pisula
Messages: 16
Registered: July 2009
Junior Member
Hello again,

I ran into some heavy problems with the migration. I managed to rewrite
the old code to use the package you mentioned instead of the one we used
to use, but the program does not work anymore. What the program does is
to build a project using the ajde build manager, and then to get the
hierarchy and relationship map from the AsmManager.
We used to do it using the ProjectBuildConfigurator to set the desired
build config. Now I set the active build conofig file using the
configurationmanager... well, it works as far as building of the project
is concerned, but the AsmManager does not return anything useful. I
would appreciate any ideas about what could be wrong, as I'm fresh out
of ideas.

Regards,
Michael

Matt Chapman wrote:
> Michael,
>
> Yes, a lot changed in the area of build configurations between AJDT 1.2
> and AJDT 1.4. There is no longer any buildconfig package or plugin.
> Essentially AJDT now uses the JDT build path mechanism to
> include/exclude files from the build. There is however still some
> support for applying and saving build configurations in .ajproperties
> files. This can be found in the org.eclipse.ajdt.ui.buildpath package.
>
> If you still have problems, please explain what the program was using
> the old classes to do exactly, and I can then try to suggest a migration
> approach.
>
> Regards,
>
> Matt.
>
> Michael Pisula wrote:
>
>> Hello,
>>
>> I am trying to migrate an application from Eclipse 3.0 to 3.2. However
>> I ran into some problems with AJDT there. The program uses some
>> classes from the buildconfig package, which was moved into a new
>> plugin as I found out. However, this plugin was nowhere to be found.
>> Has anyone got a clue where to find it, or what to use instead of
>> these classes?
>>
>> Sincerly,
>> Michael
Re: Buildconfig package [message #67441 is a reply to message #67379] Thu, 26 October 2006 11:55 Go to previous messageGo to next message
Matt Chapman is currently offline Matt Chapman
Messages: 429
Registered: July 2009
Senior Member
Hi Michael,

It's hard to say what might be going wrong without seeing the code. But
I wonder if it might be worth doing some more migration, and switching
to use the higher level classes in org.eclipse.ajdt.core instead. See my
response in the recent "How to retrieve AspectJ model during build in
eclipse?" thread, which shows how to obtain relationship information
from AJDT. Does that look useful?

What does your plug-in need from AJDT? AJDT is now integrated more
closely to the rest of Eclipse, so it's best to work in Eclipse terms.
For example if you want to control which files are built, you would
manipulate the classpath like with a Java project. And to build a
project, you can call project.build() and let Eclipse do the rest.

Regards,

Matt.

Michael Pisula wrote:
> Hello again,
>
> I ran into some heavy problems with the migration. I managed to rewrite
> the old code to use the package you mentioned instead of the one we used
> to use, but the program does not work anymore. What the program does is
> to build a project using the ajde build manager, and then to get the
> hierarchy and relationship map from the AsmManager.
> We used to do it using the ProjectBuildConfigurator to set the desired
> build config. Now I set the active build conofig file using the
> configurationmanager... well, it works as far as building of the project
> is concerned, but the AsmManager does not return anything useful. I
> would appreciate any ideas about what could be wrong, as I'm fresh out
> of ideas.
>
> Regards,
> Michael
>
> Matt Chapman wrote:
>> Michael,
>>
>> Yes, a lot changed in the area of build configurations between AJDT
>> 1.2 and AJDT 1.4. There is no longer any buildconfig package or
>> plugin. Essentially AJDT now uses the JDT build path mechanism to
>> include/exclude files from the build. There is however still some
>> support for applying and saving build configurations in .ajproperties
>> files. This can be found in the org.eclipse.ajdt.ui.buildpath package.
>>
>> If you still have problems, please explain what the program was using
>> the old classes to do exactly, and I can then try to suggest a
>> migration approach.
>>
>> Regards,
>>
>> Matt.
>>
>> Michael Pisula wrote:
>>
>>> Hello,
>>>
>>> I am trying to migrate an application from Eclipse 3.0 to 3.2.
>>> However I ran into some problems with AJDT there. The program uses
>>> some classes from the buildconfig package, which was moved into a new
>>> plugin as I found out. However, this plugin was nowhere to be found.
>>> Has anyone got a clue where to find it, or what to use instead of
>>> these classes?
>>>
>>> Sincerly,
>>> Michael
Re: Buildconfig package [message #67460 is a reply to message #67441] Thu, 26 October 2006 12:17 Go to previous messageGo to next message
Michael Pisula is currently offline Michael Pisula
Messages: 16
Registered: July 2009
Junior Member
Hi Matt,

My Plug-In builds two versions of a AspectJ program to perform a change
analysis on them. The user can choose which versions he would like to
compare by providing two build configs to the plug-in. Therefore it
would be preferable to stick with the build configurations.
I'm afraid that doing a bigger migration might be problematic, as i have
quite a dense schedule, and the migration itself is not a part of my
task, just something I do to make working easier (and to make sure that
people will actually be able to use the plug-in afterwards, without
having to work with prehistoric eclipse versions ;)).

However, I think I found the reason why I am not getting any results. I
did some debugging and turned the AJDE log on, and found something
interesting.
When the program I use to test my plug-in is build by eclipse, the log
reads like this:
"<AJDE> build started:
runtime-workbench-workspace/.metadata/.plugins/org.eclipse.a jdt.core/NullCheck.generated.lst "
However, when my plug-in builds the program, i get the following:
"<AJDE> build started:
runtime-workbench-workspace/NullCheck/build.ajproperties"

Seems like I'm setting the build config the wrong way...

Would be glad for hints how to get this right, and I'm really grateful
for your help with this :)

Regards,
Michael
Matt Chapman wrote:
> Hi Michael,
>
> It's hard to say what might be going wrong without seeing the code. But
> I wonder if it might be worth doing some more migration, and switching
> to use the higher level classes in org.eclipse.ajdt.core instead. See my
> response in the recent "How to retrieve AspectJ model during build in
> eclipse?" thread, which shows how to obtain relationship information
> from AJDT. Does that look useful?
>
> What does your plug-in need from AJDT? AJDT is now integrated more
> closely to the rest of Eclipse, so it's best to work in Eclipse terms.
> For example if you want to control which files are built, you would
> manipulate the classpath like with a Java project. And to build a
> project, you can call project.build() and let Eclipse do the rest.
>
> Regards,
>
> Matt.
>
> Michael Pisula wrote:
>
>> Hello again,
>>
>> I ran into some heavy problems with the migration. I managed to
>> rewrite the old code to use the package you mentioned instead of the
>> one we used to use, but the program does not work anymore. What the
>> program does is to build a project using the ajde build manager, and
>> then to get the hierarchy and relationship map from the AsmManager.
>> We used to do it using the ProjectBuildConfigurator to set the desired
>> build config. Now I set the active build conofig file using the
>> configurationmanager... well, it works as far as building of the
>> project is concerned, but the AsmManager does not return anything
>> useful. I would appreciate any ideas about what could be wrong, as I'm
>> fresh out of ideas.
>>
>> Regards,
>> Michael
>>
>> Matt Chapman wrote:
>>
>>> Michael,
>>>
>>> Yes, a lot changed in the area of build configurations between AJDT
>>> 1.2 and AJDT 1.4. There is no longer any buildconfig package or
>>> plugin. Essentially AJDT now uses the JDT build path mechanism to
>>> include/exclude files from the build. There is however still some
>>> support for applying and saving build configurations in .ajproperties
>>> files. This can be found in the org.eclipse.ajdt.ui.buildpath package.
>>>
>>> If you still have problems, please explain what the program was using
>>> the old classes to do exactly, and I can then try to suggest a
>>> migration approach.
>>>
>>> Regards,
>>>
>>> Matt.
>>>
>>> Michael Pisula wrote:
>>>
>>>> Hello,
>>>>
>>>> I am trying to migrate an application from Eclipse 3.0 to 3.2.
>>>> However I ran into some problems with AJDT there. The program uses
>>>> some classes from the buildconfig package, which was moved into a
>>>> new plugin as I found out. However, this plugin was nowhere to be
>>>> found. Has anyone got a clue where to find it, or what to use
>>>> instead of these classes?
>>>>
>>>> Sincerly,
>>>> Michael
Re: Buildconfig package [message #67481 is a reply to message #67460] Thu, 26 October 2006 12:24 Go to previous message
Michael Pisula is currently offline Michael Pisula
Messages: 16
Registered: July 2009
Junior Member
Hello,

I found a solution, somehow writing about what went wrong gave me some
new ideas how to get it right ;) Next time I'll try to get the ideas
before sending the mail ;)

Thank you again for your help,
Michael

Michael Pisula wrote:
> Hi Matt,
>
> My Plug-In builds two versions of a AspectJ program to perform a change
> analysis on them. The user can choose which versions he would like to
> compare by providing two build configs to the plug-in. Therefore it
> would be preferable to stick with the build configurations.
> I'm afraid that doing a bigger migration might be problematic, as i have
> quite a dense schedule, and the migration itself is not a part of my
> task, just something I do to make working easier (and to make sure that
> people will actually be able to use the plug-in afterwards, without
> having to work with prehistoric eclipse versions ;)).
>
> However, I think I found the reason why I am not getting any results. I
> did some debugging and turned the AJDE log on, and found something
> interesting.
> When the program I use to test my plug-in is build by eclipse, the log
> reads like this:
> "<AJDE> build started:
> runtime-workbench-workspace/.metadata/.plugins/org.eclipse.a jdt.core/NullCheck.generated.lst "
>
> However, when my plug-in builds the program, i get the following:
> "<AJDE> build started:
> runtime-workbench-workspace/NullCheck/build.ajproperties"
>
> Seems like I'm setting the build config the wrong way...
>
> Would be glad for hints how to get this right, and I'm really grateful
> for your help with this :)
>
> Regards,
> Michael
> Matt Chapman wrote:
>
>> Hi Michael,
>>
>> It's hard to say what might be going wrong without seeing the code.
>> But I wonder if it might be worth doing some more migration, and
>> switching to use the higher level classes in org.eclipse.ajdt.core
>> instead. See my response in the recent "How to retrieve AspectJ model
>> during build in eclipse?" thread, which shows how to obtain
>> relationship information from AJDT. Does that look useful?
>>
>> What does your plug-in need from AJDT? AJDT is now integrated more
>> closely to the rest of Eclipse, so it's best to work in Eclipse terms.
>> For example if you want to control which files are built, you would
>> manipulate the classpath like with a Java project. And to build a
>> project, you can call project.build() and let Eclipse do the rest.
>>
>> Regards,
>>
>> Matt.
>>
>> Michael Pisula wrote:
>>
>>> Hello again,
>>>
>>> I ran into some heavy problems with the migration. I managed to
>>> rewrite the old code to use the package you mentioned instead of the
>>> one we used to use, but the program does not work anymore. What the
>>> program does is to build a project using the ajde build manager, and
>>> then to get the hierarchy and relationship map from the AsmManager.
>>> We used to do it using the ProjectBuildConfigurator to set the
>>> desired build config. Now I set the active build conofig file using
>>> the configurationmanager... well, it works as far as building of the
>>> project is concerned, but the AsmManager does not return anything
>>> useful. I would appreciate any ideas about what could be wrong, as
>>> I'm fresh out of ideas.
>>>
>>> Regards,
>>> Michael
>>>
>>> Matt Chapman wrote:
>>>
>>>> Michael,
>>>>
>>>> Yes, a lot changed in the area of build configurations between AJDT
>>>> 1.2 and AJDT 1.4. There is no longer any buildconfig package or
>>>> plugin. Essentially AJDT now uses the JDT build path mechanism to
>>>> include/exclude files from the build. There is however still some
>>>> support for applying and saving build configurations in
>>>> .ajproperties files. This can be found in the
>>>> org.eclipse.ajdt.ui.buildpath package.
>>>>
>>>> If you still have problems, please explain what the program was
>>>> using the old classes to do exactly, and I can then try to suggest a
>>>> migration approach.
>>>>
>>>> Regards,
>>>>
>>>> Matt.
>>>>
>>>> Michael Pisula wrote:
>>>>
>>>>> Hello,
>>>>>
>>>>> I am trying to migrate an application from Eclipse 3.0 to 3.2.
>>>>> However I ran into some problems with AJDT there. The program uses
>>>>> some classes from the buildconfig package, which was moved into a
>>>>> new plugin as I found out. However, this plugin was nowhere to be
>>>>> found. Has anyone got a clue where to find it, or what to use
>>>>> instead of these classes?
>>>>>
>>>>> Sincerly,
>>>>> Michael
Re: Buildconfig package [message #594851 is a reply to message #67083] Thu, 05 October 2006 11:13 Go to previous message
Matt Chapman is currently offline Matt Chapman
Messages: 429
Registered: July 2009
Senior Member
Michael,

Yes, a lot changed in the area of build configurations between AJDT 1.2
and AJDT 1.4. There is no longer any buildconfig package or plugin.
Essentially AJDT now uses the JDT build path mechanism to
include/exclude files from the build. There is however still some
support for applying and saving build configurations in .ajproperties
files. This can be found in the org.eclipse.ajdt.ui.buildpath package.

If you still have problems, please explain what the program was using
the old classes to do exactly, and I can then try to suggest a migration
approach.

Regards,

Matt.

Michael Pisula wrote:
> Hello,
>
> I am trying to migrate an application from Eclipse 3.0 to 3.2. However I
> ran into some problems with AJDT there. The program uses some classes
> from the buildconfig package, which was moved into a new plugin as I
> found out. However, this plugin was nowhere to be found. Has anyone got
> a clue where to find it, or what to use instead of these classes?
>
> Sincerly,
> Michael
Re: Buildconfig package [message #595126 is a reply to message #67093] Wed, 25 October 2006 13:02 Go to previous message
Michael Pisula is currently offline Michael Pisula
Messages: 16
Registered: July 2009
Junior Member
Hello again,

I ran into some heavy problems with the migration. I managed to rewrite
the old code to use the package you mentioned instead of the one we used
to use, but the program does not work anymore. What the program does is
to build a project using the ajde build manager, and then to get the
hierarchy and relationship map from the AsmManager.
We used to do it using the ProjectBuildConfigurator to set the desired
build config. Now I set the active build conofig file using the
configurationmanager... well, it works as far as building of the project
is concerned, but the AsmManager does not return anything useful. I
would appreciate any ideas about what could be wrong, as I'm fresh out
of ideas.

Regards,
Michael

Matt Chapman wrote:
> Michael,
>
> Yes, a lot changed in the area of build configurations between AJDT 1.2
> and AJDT 1.4. There is no longer any buildconfig package or plugin.
> Essentially AJDT now uses the JDT build path mechanism to
> include/exclude files from the build. There is however still some
> support for applying and saving build configurations in .ajproperties
> files. This can be found in the org.eclipse.ajdt.ui.buildpath package.
>
> If you still have problems, please explain what the program was using
> the old classes to do exactly, and I can then try to suggest a migration
> approach.
>
> Regards,
>
> Matt.
>
> Michael Pisula wrote:
>
>> Hello,
>>
>> I am trying to migrate an application from Eclipse 3.0 to 3.2. However
>> I ran into some problems with AJDT there. The program uses some
>> classes from the buildconfig package, which was moved into a new
>> plugin as I found out. However, this plugin was nowhere to be found.
>> Has anyone got a clue where to find it, or what to use instead of
>> these classes?
>>
>> Sincerly,
>> Michael
Re: Buildconfig package [message #595150 is a reply to message #67379] Thu, 26 October 2006 11:55 Go to previous message
Matt Chapman is currently offline Matt Chapman
Messages: 429
Registered: July 2009
Senior Member
Hi Michael,

It's hard to say what might be going wrong without seeing the code. But
I wonder if it might be worth doing some more migration, and switching
to use the higher level classes in org.eclipse.ajdt.core instead. See my
response in the recent "How to retrieve AspectJ model during build in
eclipse?" thread, which shows how to obtain relationship information
from AJDT. Does that look useful?

What does your plug-in need from AJDT? AJDT is now integrated more
closely to the rest of Eclipse, so it's best to work in Eclipse terms.
For example if you want to control which files are built, you would
manipulate the classpath like with a Java project. And to build a
project, you can call project.build() and let Eclipse do the rest.

Regards,

Matt.

Michael Pisula wrote:
> Hello again,
>
> I ran into some heavy problems with the migration. I managed to rewrite
> the old code to use the package you mentioned instead of the one we used
> to use, but the program does not work anymore. What the program does is
> to build a project using the ajde build manager, and then to get the
> hierarchy and relationship map from the AsmManager.
> We used to do it using the ProjectBuildConfigurator to set the desired
> build config. Now I set the active build conofig file using the
> configurationmanager... well, it works as far as building of the project
> is concerned, but the AsmManager does not return anything useful. I
> would appreciate any ideas about what could be wrong, as I'm fresh out
> of ideas.
>
> Regards,
> Michael
>
> Matt Chapman wrote:
>> Michael,
>>
>> Yes, a lot changed in the area of build configurations between AJDT
>> 1.2 and AJDT 1.4. There is no longer any buildconfig package or
>> plugin. Essentially AJDT now uses the JDT build path mechanism to
>> include/exclude files from the build. There is however still some
>> support for applying and saving build configurations in .ajproperties
>> files. This can be found in the org.eclipse.ajdt.ui.buildpath package.
>>
>> If you still have problems, please explain what the program was using
>> the old classes to do exactly, and I can then try to suggest a
>> migration approach.
>>
>> Regards,
>>
>> Matt.
>>
>> Michael Pisula wrote:
>>
>>> Hello,
>>>
>>> I am trying to migrate an application from Eclipse 3.0 to 3.2.
>>> However I ran into some problems with AJDT there. The program uses
>>> some classes from the buildconfig package, which was moved into a new
>>> plugin as I found out. However, this plugin was nowhere to be found.
>>> Has anyone got a clue where to find it, or what to use instead of
>>> these classes?
>>>
>>> Sincerly,
>>> Michael
Re: Buildconfig package [message #595160 is a reply to message #67441] Thu, 26 October 2006 12:17 Go to previous message
Michael Pisula is currently offline Michael Pisula
Messages: 16
Registered: July 2009
Junior Member
Hi Matt,

My Plug-In builds two versions of a AspectJ program to perform a change
analysis on them. The user can choose which versions he would like to
compare by providing two build configs to the plug-in. Therefore it
would be preferable to stick with the build configurations.
I'm afraid that doing a bigger migration might be problematic, as i have
quite a dense schedule, and the migration itself is not a part of my
task, just something I do to make working easier (and to make sure that
people will actually be able to use the plug-in afterwards, without
having to work with prehistoric eclipse versions ;)).

However, I think I found the reason why I am not getting any results. I
did some debugging and turned the AJDE log on, and found something
interesting.
When the program I use to test my plug-in is build by eclipse, the log
reads like this:
"<AJDE> build started:
runtime-workbench-workspace/.metadata/.plugins/org.eclipse.a jdt.core/NullCheck.generated.lst "
However, when my plug-in builds the program, i get the following:
"<AJDE> build started:
runtime-workbench-workspace/NullCheck/build.ajproperties"

Seems like I'm setting the build config the wrong way...

Would be glad for hints how to get this right, and I'm really grateful
for your help with this :)

Regards,
Michael
Matt Chapman wrote:
> Hi Michael,
>
> It's hard to say what might be going wrong without seeing the code. But
> I wonder if it might be worth doing some more migration, and switching
> to use the higher level classes in org.eclipse.ajdt.core instead. See my
> response in the recent "How to retrieve AspectJ model during build in
> eclipse?" thread, which shows how to obtain relationship information
> from AJDT. Does that look useful?
>
> What does your plug-in need from AJDT? AJDT is now integrated more
> closely to the rest of Eclipse, so it's best to work in Eclipse terms.
> For example if you want to control which files are built, you would
> manipulate the classpath like with a Java project. And to build a
> project, you can call project.build() and let Eclipse do the rest.
>
> Regards,
>
> Matt.
>
> Michael Pisula wrote:
>
>> Hello again,
>>
>> I ran into some heavy problems with the migration. I managed to
>> rewrite the old code to use the package you mentioned instead of the
>> one we used to use, but the program does not work anymore. What the
>> program does is to build a project using the ajde build manager, and
>> then to get the hierarchy and relationship map from the AsmManager.
>> We used to do it using the ProjectBuildConfigurator to set the desired
>> build config. Now I set the active build conofig file using the
>> configurationmanager... well, it works as far as building of the
>> project is concerned, but the AsmManager does not return anything
>> useful. I would appreciate any ideas about what could be wrong, as I'm
>> fresh out of ideas.
>>
>> Regards,
>> Michael
>>
>> Matt Chapman wrote:
>>
>>> Michael,
>>>
>>> Yes, a lot changed in the area of build configurations between AJDT
>>> 1.2 and AJDT 1.4. There is no longer any buildconfig package or
>>> plugin. Essentially AJDT now uses the JDT build path mechanism to
>>> include/exclude files from the build. There is however still some
>>> support for applying and saving build configurations in .ajproperties
>>> files. This can be found in the org.eclipse.ajdt.ui.buildpath package.
>>>
>>> If you still have problems, please explain what the program was using
>>> the old classes to do exactly, and I can then try to suggest a
>>> migration approach.
>>>
>>> Regards,
>>>
>>> Matt.
>>>
>>> Michael Pisula wrote:
>>>
>>>> Hello,
>>>>
>>>> I am trying to migrate an application from Eclipse 3.0 to 3.2.
>>>> However I ran into some problems with AJDT there. The program uses
>>>> some classes from the buildconfig package, which was moved into a
>>>> new plugin as I found out. However, this plugin was nowhere to be
>>>> found. Has anyone got a clue where to find it, or what to use
>>>> instead of these classes?
>>>>
>>>> Sincerly,
>>>> Michael
Re: Buildconfig package [message #595165 is a reply to message #67460] Thu, 26 October 2006 12:24 Go to previous message
Michael Pisula is currently offline Michael Pisula
Messages: 16
Registered: July 2009
Junior Member
Hello,

I found a solution, somehow writing about what went wrong gave me some
new ideas how to get it right ;) Next time I'll try to get the ideas
before sending the mail ;)

Thank you again for your help,
Michael

Michael Pisula wrote:
> Hi Matt,
>
> My Plug-In builds two versions of a AspectJ program to perform a change
> analysis on them. The user can choose which versions he would like to
> compare by providing two build configs to the plug-in. Therefore it
> would be preferable to stick with the build configurations.
> I'm afraid that doing a bigger migration might be problematic, as i have
> quite a dense schedule, and the migration itself is not a part of my
> task, just something I do to make working easier (and to make sure that
> people will actually be able to use the plug-in afterwards, without
> having to work with prehistoric eclipse versions ;)).
>
> However, I think I found the reason why I am not getting any results. I
> did some debugging and turned the AJDE log on, and found something
> interesting.
> When the program I use to test my plug-in is build by eclipse, the log
> reads like this:
> "<AJDE> build started:
> runtime-workbench-workspace/.metadata/.plugins/org.eclipse.a jdt.core/NullCheck.generated.lst "
>
> However, when my plug-in builds the program, i get the following:
> "<AJDE> build started:
> runtime-workbench-workspace/NullCheck/build.ajproperties"
>
> Seems like I'm setting the build config the wrong way...
>
> Would be glad for hints how to get this right, and I'm really grateful
> for your help with this :)
>
> Regards,
> Michael
> Matt Chapman wrote:
>
>> Hi Michael,
>>
>> It's hard to say what might be going wrong without seeing the code.
>> But I wonder if it might be worth doing some more migration, and
>> switching to use the higher level classes in org.eclipse.ajdt.core
>> instead. See my response in the recent "How to retrieve AspectJ model
>> during build in eclipse?" thread, which shows how to obtain
>> relationship information from AJDT. Does that look useful?
>>
>> What does your plug-in need from AJDT? AJDT is now integrated more
>> closely to the rest of Eclipse, so it's best to work in Eclipse terms.
>> For example if you want to control which files are built, you would
>> manipulate the classpath like with a Java project. And to build a
>> project, you can call project.build() and let Eclipse do the rest.
>>
>> Regards,
>>
>> Matt.
>>
>> Michael Pisula wrote:
>>
>>> Hello again,
>>>
>>> I ran into some heavy problems with the migration. I managed to
>>> rewrite the old code to use the package you mentioned instead of the
>>> one we used to use, but the program does not work anymore. What the
>>> program does is to build a project using the ajde build manager, and
>>> then to get the hierarchy and relationship map from the AsmManager.
>>> We used to do it using the ProjectBuildConfigurator to set the
>>> desired build config. Now I set the active build conofig file using
>>> the configurationmanager... well, it works as far as building of the
>>> project is concerned, but the AsmManager does not return anything
>>> useful. I would appreciate any ideas about what could be wrong, as
>>> I'm fresh out of ideas.
>>>
>>> Regards,
>>> Michael
>>>
>>> Matt Chapman wrote:
>>>
>>>> Michael,
>>>>
>>>> Yes, a lot changed in the area of build configurations between AJDT
>>>> 1.2 and AJDT 1.4. There is no longer any buildconfig package or
>>>> plugin. Essentially AJDT now uses the JDT build path mechanism to
>>>> include/exclude files from the build. There is however still some
>>>> support for applying and saving build configurations in
>>>> .ajproperties files. This can be found in the
>>>> org.eclipse.ajdt.ui.buildpath package.
>>>>
>>>> If you still have problems, please explain what the program was
>>>> using the old classes to do exactly, and I can then try to suggest a
>>>> migration approach.
>>>>
>>>> Regards,
>>>>
>>>> Matt.
>>>>
>>>> Michael Pisula wrote:
>>>>
>>>>> Hello,
>>>>>
>>>>> I am trying to migrate an application from Eclipse 3.0 to 3.2.
>>>>> However I ran into some problems with AJDT there. The program uses
>>>>> some classes from the buildconfig package, which was moved into a
>>>>> new plugin as I found out. However, this plugin was nowhere to be
>>>>> found. Has anyone got a clue where to find it, or what to use
>>>>> instead of these classes?
>>>>>
>>>>> Sincerly,
>>>>> Michael
Previous Topic:How to retrieve AspectJ model during build in eclipse?
Next Topic:How to find fully qualified type name from simple type name?
Goto Forum:
  


Current Time: Fri Sep 19 16:06:16 GMT 2014

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

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