Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Language IDEs » AJDT » Binary cycles while exporting RCP product
Binary cycles while exporting RCP product [message #74370] Thu, 02 July 2009 16:02 Go to next message
Eclipse User
Originally posted by: gaston.tonietti.teracode.com

Hi guys,

I have a problem when I want to export my RCP product.

As I have some aspects in my project I tried to export it using "Eclipse product with AspectJ support" export wizard, but the export
fails with the following error:

Export feature error
A cycle was detected when generating the classpath ...

I know this problem is fixed in JDT. "Eclipse product" export wizard has a nice and useful checkbox called "Allow for binary cycles in
target platform", but if I use this wizard I don't have any aspect in the exported product, compiled aspects are not present in the
plug-in jar so I get this error at startup:

Cannot register non aspect: ....

So, I wonder if there is any way to tell AJDT export wizard to allow for binary cycles just as JDT one does.

Thank you very much for your time.
Gaston.
Re: Binary cycles while exporting RCP product [message #74388 is a reply to message #74370] Thu, 02 July 2009 18:42 Go to previous messageGo to next message
Eclipse User
Originally posted by: andrew.eisenberg.springsource.com

Binary cycles when exporting are not currently supported in AJDT, but there
is a bug open for this:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=268667

There is a patch, which I am planning on integrating soon. Please add your
name to the cc there and you will be notified of its progress.

The patch will only be applied to the 3.5 stream as Eclipse 3.4 does not
allow binary cycles.


On 02/07/09 9:02 AM, in article h2ilm2$u5h$1@build.eclipse.org, "Gaston M.
Tonietti" <gaston.tonietti@teracode.com> wrote:

> Hi guys,
>
> I have a problem when I want to export my RCP product.
>
> As I have some aspects in my project I tried to export it using "Eclipse
> product with AspectJ support" export wizard, but the export
> fails with the following error:
>
> Export feature error
> A cycle was detected when generating the classpath ...
>
> I know this problem is fixed in JDT. "Eclipse product" export wizard has a
> nice and useful checkbox called "Allow for binary cycles in
> target platform", but if I use this wizard I don't have any aspect in the
> exported product, compiled aspects are not present in the
> plug-in jar so I get this error at startup:
>
> Cannot register non aspect: ....
>
> So, I wonder if there is any way to tell AJDT export wizard to allow for
> binary cycles just as JDT one does.
>
> Thank you very much for your time.
> Gaston.
Re: Binary cycles while exporting RCP product [message #74406 is a reply to message #74388] Fri, 03 July 2009 15:17 Go to previous messageGo to next message
Eclipse User
Originally posted by: gaston.tonietti.teracode.com

Thanks for answering Andrew. I've added myself to the CC list of the bug.

But I still have the problem, I'm not able to export my product with aspects support. Do you know what I am doing in the meanwhile? I have to copy compiled aspects from my project output folder into the plugin jar
inside the product zip :O (thanks Midnight Commander for supporting that!!). So every time I have to export a new Milestone, it is a pain you know where :-)

I also have to make a headless build to work. I have it working after following instructions from Andrew Niefer' blog "Building p2 RCP products in Eclipse 3.5M6", but guess what... without aspects working :-)

I found a solution for that in https://bugs.eclipse.org/bugs/show_bug.cgi?id=252641#c12

I replaced this line:
<ant antfile="${eclipse.pdebuild.scripts}/productBuild/productBuild.xml " />
with this one:
<ant antfile="${ajdt.pdebuild.scripts}/productBuild/productBuild.xml " />

but I got this error:
BUILD FAILED
project-releng/buildProduct.xml:21: The following error occurred while executing this line:
project-releng/org.eclipse.ajdt.pde.build_1.6.3.200808060918 /scripts/productBuild/productBuild.xml:20: The following error occurred while executing this line:
project-releng/org.eclipse.ajdt.pde.build_1.6.3.200808060918 /scripts/build.xml:46: The following error occurred while executing this line:
project-releng/org.eclipse.ajdt.pde.build_1.6.3.200808060918 /templates/headless-build/customTargets.xml:73: The following error occurred while executing this line:
project-releng/org.eclipse.ajdt.pde.build_1.6.3.200808060918 /templates/headless-build/customTargets.xml:18: java.net.MalformedURLException: no protocol: ${eclipseBaseURL}

I also tried replacing with this line as the bug comment says:
<ant antfile="${ajdt.pdebuild.scripts}/build.xml" />

but I got this error:
BUILD FAILED
project-releng/buildProduct.xml:21: The following error occurred while executing this line:
project-releng/org.eclipse.ajdt.pde.build_1.6.3.200808060918 /scripts/build.xml:28: The following error occurred while executing this line:
project-releng/org.eclipse.ajdt.pde.build_1.6.3.200808060918 /scripts/build.xml:68: The following error occurred while executing this line:
project-releng/org.eclipse.ajdt.pde.build_1.6.3.200808060918 /templates/headless-build/customTargets.xml:12: The following error occurred while executing this line:
project-releng/org.eclipse.ajdt.pde.build_1.6.3.200808060918 /templates/headless-build/allElements.xml:16: The following error occurred while executing this line:
project-releng/org.eclipse.ajdt.pde.build_1.6.3.200808060918 /scripts/genericTargets.xml:88: java.lang.NoSuchMethodError: org.eclipse.pde.internal.build.BundleHelper.getRuntimeJavaPr ofiles()[Ljava/lang/String;

So, just for you to know, I'm using Galileo release with the proper AJDT version 2.0.0 and it seems that this build plugin is for AJDT 1.6.3. Am I right?
So I would like to know if there is any update of the AJDT PDE Build but for last AJDT version 2.0.0 and if it supports the same that PDE one does, such as p2 repository generation.

Thanks a lot.
Gaston.


Andrew Eisenberg wrote:

> Binary cycles when exporting are not currently supported in AJDT, but
> there is a bug open for this:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=268667
>
> There is a patch, which I am planning on integrating soon. Please add
> your name to the cc there and you will be notified of its progress.
>
> The patch will only be applied to the 3.5 stream as Eclipse 3.4 does not
> allow binary cycles.
>
>
> On 02/07/09 9:02 AM, in article h2ilm2$u5h$1@build.eclipse.org, "Gaston M.
> Tonietti" <gaston.tonietti@teracode.com> wrote:
>
>> Hi guys,
>>
>> I have a problem when I want to export my RCP product.
>>
>> As I have some aspects in my project I tried to export it using "Eclipse
>> product with AspectJ support" export wizard, but the export
>> fails with the following error:
>>
>> Export feature error
>> A cycle was detected when generating the classpath ...
>>
>> I know this problem is fixed in JDT. "Eclipse product" export wizard has
>> a nice and useful checkbox called "Allow for binary cycles in
>> target platform", but if I use this wizard I don't have any aspect in the
>> exported product, compiled aspects are not present in the
>> plug-in jar so I get this error at startup:
>>
>> Cannot register non aspect: ....
>>
>> So, I wonder if there is any way to tell AJDT export wizard to allow for
>> binary cycles just as JDT one does.
>>
>> Thank you very much for your time.
>> Gaston.
Re: Binary cycles while exporting RCP product [message #74424 is a reply to message #74406] Fri, 03 July 2009 17:55 Go to previous messageGo to next message
Eclipse User
Originally posted by: andrew.eisenberg.springsource.com

On 03/07/09 8:17 AM, in article h2l7f3$h1$1@build.eclipse.org, "Gaston M.
Tonietti" <gaston.tonietti@teracode.com> wrote:

> Thanks for answering Andrew. I've added myself to the CC list of the bug.
This bug has now been fixed. Let me know if this addresses your
non-headless build issues.


>
> So, just for you to know, I'm using Galileo release with the proper AJDT
> version 2.0.0 and it seems that this build plugin is for AJDT 1.6.3. Am I
> right?
Yes. This plugin is not officially supported by us. We put it out there
because some people were asking for it. We use it (and a 3.5 version) to
build AJDT itself.

> So I would like to know if there is any update of the AJDT PDE Build but for
> last AJDT version 2.0.0 and if it supports the same that PDE one does, such as
> p2 repository generation.
>
I can package one up for you and post it to that bug report. I don't think
I can get to it today, but early next week.

Eventually, I may have to release it as a feature on the update site.
Re: Binary cycles while exporting RCP product [message #74441 is a reply to message #74424] Fri, 03 July 2009 18:50 Go to previous messageGo to next message
Eclipse User
Originally posted by: gaston.tonietti.teracode.com

Comments inline.

Andrew Eisenberg wrote:

>
>
>
> On 03/07/09 8:17 AM, in article h2l7f3$h1$1@build.eclipse.org, "Gaston M.
> Tonietti" <gaston.tonietti@teracode.com> wrote:
>
>> Thanks for answering Andrew. I've added myself to the CC list of the bug.
> This bug has now been fixed. Let me know if this addresses your
> non-headless build issues.
I got the bugzilla mail. Good news. What should I do to try it out? download
a nightly build of AJDT for Galileo? or it is already published thru the
update site.
>
>
>>
>> So, just for you to know, I'm using Galileo release with the proper AJDT
>> version 2.0.0 and it seems that this build plugin is for AJDT 1.6.3. Am I
>> right?
> Yes. This plugin is not officially supported by us. We put it out there
> because some people were asking for it. We use it (and a 3.5 version) to
> build AJDT itself.
>
>> So I would like to know if there is any update of the AJDT PDE Build but
>> for last AJDT version 2.0.0 and if it supports the same that PDE one
>> does, such as p2 repository generation.
>>
> I can package one up for you and post it to that bug report. I don't
> think I can get to it today, but early next week.
Early next week would be pretty fine for me. I'm adding myself to this bug's
CC list right now so I get notified when you post it.
>
> Eventually, I may have to release it as a feature on the update site.
It would be really cool. There would be lot of people using aspectj in RCP
products who need to build "headlesslly"

Last question.
Is this build delegating on PDE one so it only replaces PDE for compiling?
I ask it to know if I must contact you for problems (not related to
AspectsJ) in the headless build process if I'm using this script or I should
contact PDE folks.

Tank you very much for all your help. You have been very kind.
Gaston.
Re: Binary cycles while exporting RCP product [message #74459 is a reply to message #74441] Fri, 03 July 2009 20:40 Go to previous messageGo to next message
Eclipse User
Originally posted by: andrew.eisenberg.springsource.com

> I got the bugzilla mail. Good news. What should I do to try it out? download
> a nightly build of AJDT for Galileo? or it is already published thru the
> update site.

It will be available from the dev update site:
http://download.eclipse.org/tools/ajdt/35/dev/update

It is not available yet, but should be within a few hours. Look at the time
stamp for the build available from the site to see if it is the one produced
today.

> Early next week would be pretty fine for me. I'm adding myself to this bug's
> CC list right now so I get notified when you post it.
Good.

> It would be really cool. There would be lot of people using aspectj in RCP
> products who need to build "headlesslly"

Well, when I asked on the bug report and on the mailing list who would be
interested in having this feature available from the update site, I got no
responses, so I assumed there was little interest.

>
> Last question.
> Is this build delegating on PDE one so it only replaces PDE for compiling?
> I ask it to know if I must contact you for problems (not related to
> AspectsJ) in the headless build process if I'm using this script or I should
> contact PDE folks.
What we do, and this is the reason why it is not "officially" supported, is
that we branch the PDE build plugin and make the appropriate changes so that
AJDT can be built. The only substantial change that we have made is to
delegate to ajc instead of javac, but this small change cascades into a few
other changes elsewhere in the plugin.

It will probably work on other projects, but we have not tested it in detail
(nor do we have the capacity to).

--a
Re: Binary cycles while exporting RCP product [message #74477 is a reply to message #74459] Tue, 07 July 2009 05:41 Go to previous messageGo to next message
Eclipse User
Originally posted by: gaston.tonietti.teracode.com

Hi Andrew,

I did the update, I got AspectJ Development Tools 2.0.1.e35x-20090704-2000, but I'm still having problems.

I have no checkbox for allowing cycles in "Export Eclipse Product with AspectJ support". It is not an issue as now it does not fail due cycles anymore.
I saw it in "Export deployable plug-ins and fragments with AspectJ support" but I need to export it as an eclipse product.

The problem is that I have no compiled aspects in the exported product, I have only .aj files and sometimes a compilation error in a temporary build.xml (line 210) which is created in the project root, it does not
happen with regular PDE product export.

I would like to clarify something, I don't know if it matters:
I don't have aspects in the product I'm exporting, but in another project
which the product depends on.

WS structure (simplified :-) )
- domain (with aspects)
- ui (the product, depending on domain)

Let me know if I'm doing something wrong. Anyway, I can wait until you post the scripts for headless building {IReminder reminder = (IReminder) gaston;} :-)
Thanks again

Gaston.


Andrew Eisenberg wrote:

>
>
>
>> I got the bugzilla mail. Good news. What should I do to try it out?
>> download a nightly build of AJDT for Galileo? or it is already published
>> thru the update site.
>
> It will be available from the dev update site:
> http://download.eclipse.org/tools/ajdt/35/dev/update
>
> It is not available yet, but should be within a few hours. Look at the
> time stamp for the build available from the site to see if it is the one
> produced today.
>
>> Early next week would be pretty fine for me. I'm adding myself to this
>> bug's CC list right now so I get notified when you post it.
> Good.
>
>> It would be really cool. There would be lot of people using aspectj in
>> RCP products who need to build "headlesslly"
>
> Well, when I asked on the bug report and on the mailing list who would be
> interested in having this feature available from the update site, I got no
> responses, so I assumed there was little interest.
>
>>
>> Last question.
>> Is this build delegating on PDE one so it only replaces PDE for
>> compiling? I ask it to know if I must contact you for problems (not
>> related to AspectsJ) in the headless build process if I'm using this
>> script or I should contact PDE folks.
> What we do, and this is the reason why it is not "officially" supported,
> is that we branch the PDE build plugin and make the appropriate changes so
> that
> AJDT can be built. The only substantial change that we have made is to
> delegate to ajc instead of javac, but this small change cascades into a
> few other changes elsewhere in the plugin.
>
> It will probably work on other projects, but we have not tested it in
> detail (nor do we have the capacity to).
>
> --a
Re: Binary cycles while exporting RCP product [message #74495 is a reply to message #74477] Wed, 08 July 2009 04:00 Go to previous messageGo to next message
Eclipse User
Originally posted by: andrew.eisenberg.springsource.com

Hi Gaston,

I added a new attachment to the bug report that has the updated ajdt pde
build plugin 3.5:
https://bugs.eclipse.org/252641

> I have no checkbox for allowing cycles in "Export Eclipse Product with AspectJ
> support". It is not an issue as now it does not fail due cycles anymore.
> I saw it in "Export deployable plug-ins and fragments with AspectJ support"
> but I need to export it as an eclipse product.
Yes. There is no check box for it. The change I made turned on the flag by
default (with no way of disabling it). Bug 282391 is about adding UI
support for this.

> I would like to clarify something, I don't know if it matters:
> I don't have aspects in the product I'm exporting, but in another project
> which the product depends on.

Yes, this may be an issue. How do you have this set up? Is the other
project on the aspect path? Is it another plugin project?

Right click on the manifest file for the plugin and select "Generate build
file with AspectJ support". Make sure that the project that you expect is
on the aspect path.

--a
Re: Binary cycles while exporting RCP product [message #74512 is a reply to message #74495] Wed, 08 July 2009 07:13 Go to previous messageGo to next message
Eclipse User
Originally posted by: gaston.tonietti.teracode.com

Ok. I tried to build the product using scripts from ajdt-pde-build plugin but it fails:
org.eclipse.ajdt.pde.build_2.0.1.200907072043/templates/head less-build/customTargets.xml:18: java.net.MalformedURLException: no protocol:
${eclipseBaseURL}

But I think I understood what you said, so I created the build file in the project having the aspects, it generates a @dot folder with compiled aspects
all right, and I built the product with the regular pdebuild script, thinking it will use the existing build.xml for the project with the aspects, but it
wasn't this way :-( , this file was overridden by one without AspectJ support.

So I don't know what else to do.

My setup is, at least the part which matters now (I have more plug-in projects not related to this problem), a plug-in project with AspectJ capability
called domain and an RCP product project called ui. Domain doesn't know anything about ui, while ui depends on domain (using Required-Bundles header) and
uses Equinox Aspects for weaving at runtime. All this is working great in development.

So my problem is, that I get the domain plug-in jar with the MyAspect.aj file instead of the compiled one MyAspect.class, due that, weaving hook fails
registering the aspect:
Cannot register non aspect: MyAspect , MyAspect

So what can I do in order to get an exported product with a domain plug-in jar containing proper aspect class?

Thanks a lot Andrew.
Gaston.

Andrew Eisenberg wrote:

> Hi Gaston,
>
> I added a new attachment to the bug report that has the updated ajdt pde
> build plugin 3.5:
> https://bugs.eclipse.org/252641
>
>> I have no checkbox for allowing cycles in "Export Eclipse Product with
>> AspectJ support". It is not an issue as now it does not fail due cycles
>> anymore. I saw it in "Export deployable plug-ins and fragments with
>> AspectJ support" but I need to export it as an eclipse product.
> Yes. There is no check box for it. The change I made turned on the flag
> by
> default (with no way of disabling it). Bug 282391 is about adding UI
> support for this.
>
>> I would like to clarify something, I don't know if it matters:
>> I don't have aspects in the product I'm exporting, but in another project
>> which the product depends on.
>
> Yes, this may be an issue. How do you have this set up? Is the other
> project on the aspect path? Is it another plugin project?
>
> Right click on the manifest file for the plugin and select "Generate build
> file with AspectJ support". Make sure that the project that you expect is
> on the aspect path.
>
> --a
Re: Binary cycles while exporting RCP product [message #74530 is a reply to message #74512] Wed, 08 July 2009 16:18 Go to previous messageGo to next message
Eclipse User
Originally posted by: andrew.eisenberg.springsource.com

> Ok. I tried to build the product using scripts from ajdt-pde-build plugin but
> it fails:
> org.eclipse.ajdt.pde.build_2.0.1.200907072043/templates/head less-build/customT
> argets.xml:18: java.net.MalformedURLException: no protocol:
> ${eclipseBaseURL}
The problem here is that you have not set the variable eclipseBaseURL. It
should point to the target eclipse zip file that you are building against.
Note that this should be in URL format. So, eg:
file:/home/build/Eclipses/myEclipse.zip

This doesn't need to be called. See the getBaseComponents target in
customTargets.xml.
Re: Binary cycles while exporting RCP product [message #74548 is a reply to message #74530] Wed, 08 July 2009 19:46 Go to previous messageGo to next message
Eclipse User
Originally posted by: gaston.tonietti.teracode.com

Thank to point me out this, I'm skipping it now so that problem is solved, but I have a new one now:

generateScript:

BUILD FAILED
releng/buildProduct.xml:22: The following error occurred while executing this line:
releng/org.eclipse.ajdt.pde.build_2.0.1.200907072043/scripts /productBuild/productBuild.xml:28: The following error occurred while executing this line:
releng/org.eclipse.ajdt.pde.build_2.0.1.200907072043/scripts /build.xml:68: The following error occurred while executing this line:
releng/org.eclipse.ajdt.pde.build_2.0.1.200907072043/templat es/headless-build/customTargets.xml:12: The following error occurred while executing this line:
releng/org.eclipse.ajdt.pde.build_2.0.1.200907072043/scripts /productBuild/allElements.xml:10: The following error occurred while executing this line:
releng/org.eclipse.ajdt.pde.build_2.0.1.200907072043/scripts /genericTargets.xml:88: java.lang.NoSuchMethodError: org.eclipse.pde.internal.build.BundleHelper.getRuntimeJavaPr ofiles()[Ljava/lang/String;

Any idea? is it using the wrong jar?

Thanks again.
Gaston.

Andrew Eisenberg wrote:

>> Ok. I tried to build the product using scripts from ajdt-pde-build plugin
>> but it fails:
>> org.eclipse.ajdt.pde.build_2.0.1.200907072043/templates/head less-build/customT
>> argets.xml:18: java.net.MalformedURLException: no protocol:
>> ${eclipseBaseURL}
> The problem here is that you have not set the variable eclipseBaseURL. It
> should point to the target eclipse zip file that you are building against.
> Note that this should be in URL format. So, eg:
> file:/home/build/Eclipses/myEclipse.zip
>
> This doesn't need to be called. See the getBaseComponents target in
> customTargets.xml.
Re: Binary cycles while exporting RCP product [message #74566 is a reply to message #74548] Wed, 08 July 2009 21:23 Go to previous messageGo to next message
Eclipse User
Originally posted by: andrew.eisenberg.springsource.com

Don't know what is going on here. The call to the method that is invalid,
existed in the 3.4 version, but does not exist in the 3.5 version. Perhaps
you are picking up the wrong jar (ie- the 3,.4 jar). Make sure that the old
pluign is completely wiped from your workspace. And try running once with
-clean to ensure that the jar wasn't cached anywhere.

If that still doesn't work, I will recreate the plugin for you from scratch
and make sure that the proper jar is in there.


On 08/07/09 12:46 PM, in article h32t2c$s5$1@build.eclipse.org, "Gaston M.
Tonietti" <gaston.tonietti@teracode.com> wrote:

> Thank to point me out this, I'm skipping it now so that problem is solved, but
> I have a new one now:
>
> generateScript:
>
> BUILD FAILED
> releng/buildProduct.xml:22: The following error occurred while executing this
> line:
> releng/org.eclipse.ajdt.pde.build_2.0.1.200907072043/scripts /productBuild/prod
> uctBuild.xml:28: The following error occurred while executing this line:
> releng/org.eclipse.ajdt.pde.build_2.0.1.200907072043/scripts /build.xml:68: The
> following error occurred while executing this line:
> releng/org.eclipse.ajdt.pde.build_2.0.1.200907072043/templat es/headless-build/
> customTargets.xml:12: The following error occurred while executing this line:
> releng/org.eclipse.ajdt.pde.build_2.0.1.200907072043/scripts /productBuild/allE
> lements.xml:10: The following error occurred while executing this line:
> releng/org.eclipse.ajdt.pde.build_2.0.1.200907072043/scripts /genericTargets.xm
> l:88: java.lang.NoSuchMethodError:
> org.eclipse.pde.internal.build.BundleHelper.getRuntimeJavaPr ofiles()[Ljava/lan
> g/String;
>
> Any idea? is it using the wrong jar?
>
> Thanks again.
> Gaston.
>
> Andrew Eisenberg wrote:
>
>>> Ok. I tried to build the product using scripts from ajdt-pde-build plugin
>>> but it fails:
>>> org.eclipse.ajdt.pde.build_2.0.1.200907072043/templates/head less-build/custo
>>> mT
>>> argets.xml:18: java.net.MalformedURLException: no protocol:
>>> ${eclipseBaseURL}
>> The problem here is that you have not set the variable eclipseBaseURL. It
>> should point to the target eclipse zip file that you are building against.
>> Note that this should be in URL format. So, eg:
>> file:/home/build/Eclipses/myEclipse.zip
>>
>> This doesn't need to be called. See the getBaseComponents target in
>> customTargets.xml.
>
Re: Binary cycles while exporting RCP product [message #74584 is a reply to message #74566] Thu, 09 July 2009 06:58 Go to previous messageGo to next message
Eclipse User
Originally posted by: gaston.tonietti.teracode.com

Hi Andrew, finally I was able to build the product.

It was just as you said, I had the old plugin in my dropins, so I removed it and installed the new one and it worked.
I had a little problem when assembling, it tried to find the launcher icon in a folder inside buldDirectory but it wasn't there, I could fix it creating a soft link pointing to the folder it looked for (not
that nice).

I got the product exported, with aspects working great, but I lost a very important thing, repository generation and p2 director invocation. It seems that ajdt-pde-build is ignoring the property
p2.gathering

Do you know how I can get it back?
Can I use AJDT Build just for the plug-in which needs it (domain project) and build the product and the other plug-ins with the regular PDE Build? I tried, but build.xml with aspectj support which I
generate in domain project is overridden when I run the product build. If I make it read only the build fails.

Thank you so much for all your help. I really appreciate it.
Gaston.


Andrew Eisenberg wrote:

> Don't know what is going on here. The call to the method that is invalid,
> existed in the 3.4 version, but does not exist in the 3.5 version.
> Perhaps
> you are picking up the wrong jar (ie- the 3,.4 jar). Make sure that the
> old
> pluign is completely wiped from your workspace. And try running once with
> -clean to ensure that the jar wasn't cached anywhere.
>
> If that still doesn't work, I will recreate the plugin for you from
> scratch and make sure that the proper jar is in there.
>
>
> On 08/07/09 12:46 PM, in article h32t2c$s5$1@build.eclipse.org, "Gaston M.
> Tonietti" <gaston.tonietti@teracode.com> wrote:
>
>> Thank to point me out this, I'm skipping it now so that problem is
>> solved, but I have a new one now:
>>
>> generateScript:
>>
>> BUILD FAILED
>> releng/buildProduct.xml:22: The following error occurred while executing
>> this line:
>> releng/org.eclipse.ajdt.pde.build_2.0.1.200907072043/scripts /productBuild/prod
>> uctBuild.xml:28: The following error occurred while executing this line:
>> releng/org.eclipse.ajdt.pde.build_2.0.1.200907072043/scripts /build.xml:68:
>> The following error occurred while executing this line:
>> releng/org.eclipse.ajdt.pde.build_2.0.1.200907072043/templat es/headless-build/
>> customTargets.xml:12: The following error occurred while executing this
>> line:
>> releng/org.eclipse.ajdt.pde.build_2.0.1.200907072043/scripts /productBuild/allE
>> lements.xml:10: The following error occurred while executing this line:
>> releng/org.eclipse.ajdt.pde.build_2.0.1.200907072043/scripts /genericTargets.xm
>> l:88: java.lang.NoSuchMethodError:
>> org.eclipse.pde.internal.build.BundleHelper.getRuntimeJavaPr ofiles()[Ljava/lan
>> g/String;
>>
>> Any idea? is it using the wrong jar?
>>
>> Thanks again.
>> Gaston.
>>
>> Andrew Eisenberg wrote:
>>
>>>> Ok. I tried to build the product using scripts from ajdt-pde-build
>>>> plugin but it fails:
>>>> org.eclipse.ajdt.pde.build_2.0.1.200907072043/templates/head less-build/custo
>>>> mT
>>>> argets.xml:18: java.net.MalformedURLException: no protocol:
>>>> ${eclipseBaseURL}
>>> The problem here is that you have not set the variable eclipseBaseURL.
>>> It should point to the target eclipse zip file that you are building
>>> against.
>>> Note that this should be in URL format. So, eg:
>>> file:/home/build/Eclipses/myEclipse.zip
>>>
>>> This doesn't need to be called. See the getBaseComponents target in
>>> customTargets.xml.
>>
Re: Binary cycles while exporting RCP product [message #74601 is a reply to message #74584] Thu, 09 July 2009 17:40 Go to previous messageGo to next message
Eclipse User
Originally posted by: andrew.eisenberg.springsource.com

Glad to hear that you got it working.

> I got the product exported, with aspects working great, but I lost a very
> important thing, repository generation and p2 director invocation. It seems
> that ajdt-pde-build is ignoring the property
> p2.gathering

That property is not supported by the build scripts currently. I raised a
bug to track this:
http://bugs.eclipse.org/283054

How important for you is having this property available in your AJDT
headless build scripts? This is not a trivial enhancement, and I need to
know how to rank it in importance.
Re: Binary cycles while exporting RCP product [message #74619 is a reply to message #74601] Thu, 09 July 2009 17:56 Go to previous messageGo to next message
Eclipse User
Originally posted by: gaston.tonietti.teracode.com

It depends on the answer to my other question.

If I can handle product export with the regular PDE Build while using AJDT
Build for just those plug-ins having aspects, it is not important.

I think it makes more sense to do it this way as it is using ajc for all
projects, even for those which I know that don't have any aspect.

Is there any way to address it this way?

Thanks.
Gaston.

Andrew Eisenberg wrote:

> Glad to hear that you got it working.
>
>> I got the product exported, with aspects working great, but I lost a very
>> important thing, repository generation and p2 director invocation. It
>> seems that ajdt-pde-build is ignoring the property
>> p2.gathering
>
> That property is not supported by the build scripts currently. I raised a
> bug to track this:
> http://bugs.eclipse.org/283054
>
> How important for you is having this property available in your AJDT
> headless build scripts? This is not a trivial enhancement, and I need to
> know how to rank it in importance.
Re: Binary cycles while exporting RCP product [message #74637 is a reply to message #74619] Thu, 09 July 2009 20:26 Go to previous messageGo to next message
Eclipse User
Originally posted by: andrew.eisenberg.springsource.com

> If I can handle product export with the regular PDE Build while using AJDT
> Build for just those plug-ins having aspects, it is not important.
>
> I think it makes more sense to do it this way as it is using ajc for all
> projects, even for those which I know that don't have any aspect.
>
> Is there any way to address it this way?

I don't know. Can you export your aspect plugins separately from your
non-aspect plugins?

This might be a question better asked on the pde mailing list.
Re: Binary cycles while exporting RCP product [message #74655 is a reply to message #74637] Fri, 10 July 2009 05:54 Go to previous messageGo to next message
Eclipse User
Originally posted by: gaston.tonietti.teracode.com

Ok Andrew, I'll try with the PDE folks. Thank you so much for all your help. It was very kind of you.

Gaston.

Andrew Eisenberg wrote:

>
>
>
>> If I can handle product export with the regular PDE Build while using
>> AJDT Build for just those plug-ins having aspects, it is not important.
>>
>> I think it makes more sense to do it this way as it is using ajc for all
>> projects, even for those which I know that don't have any aspect.
>>
>> Is there any way to address it this way?
>
> I don't know. Can you export your aspect plugins separately from your
> non-aspect plugins?
>
> This might be a question better asked on the pde mailing list.
Re: Binary cycles while exporting RCP product [message #74672 is a reply to message #74655] Fri, 10 July 2009 07:15 Go to previous message
Eclipse User
Originally posted by: andrew.eisenberg.springsource.com

No problem. Let me know how it goes with the pde team. If they can't help,
come back here, raise a bug, and I will try to find some time to look into
it.


On 09/07/09 10:54 PM, in article h36l2b$g68$1@build.eclipse.org, "Gaston M.
Tonietti" <gaston.tonietti@teracode.com> wrote:

> Ok Andrew, I'll try with the PDE folks. Thank you so much for all your help.
> It was very kind of you.
>
> Gaston.
>
> Andrew Eisenberg wrote:
>
>>
>>
>>
>>> If I can handle product export with the regular PDE Build while using
>>> AJDT Build for just those plug-ins having aspects, it is not important.
>>>
>>> I think it makes more sense to do it this way as it is using ajc for all
>>> projects, even for those which I know that don't have any aspect.
>>>
>>> Is there any way to address it this way?
>>
>> I don't know. Can you export your aspect plugins separately from your
>> non-aspect plugins?
>>
>> This might be a question better asked on the pde mailing list.
>
Re: Binary cycles while exporting RCP product [message #600171 is a reply to message #74370] Thu, 02 July 2009 18:42 Go to previous message
Andrew Eisenberg is currently offline Andrew Eisenberg
Messages: 77
Registered: July 2009
Member
Binary cycles when exporting are not currently supported in AJDT, but there
is a bug open for this:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=268667

There is a patch, which I am planning on integrating soon. Please add your
name to the cc there and you will be notified of its progress.

The patch will only be applied to the 3.5 stream as Eclipse 3.4 does not
allow binary cycles.


On 02/07/09 9:02 AM, in article h2ilm2$u5h$1@build.eclipse.org, "Gaston M.
Tonietti" <gaston.tonietti@teracode.com> wrote:

> Hi guys,
>
> I have a problem when I want to export my RCP product.
>
> As I have some aspects in my project I tried to export it using "Eclipse
> product with AspectJ support" export wizard, but the export
> fails with the following error:
>
> Export feature error
> A cycle was detected when generating the classpath ...
>
> I know this problem is fixed in JDT. "Eclipse product" export wizard has a
> nice and useful checkbox called "Allow for binary cycles in
> target platform", but if I use this wizard I don't have any aspect in the
> exported product, compiled aspects are not present in the
> plug-in jar so I get this error at startup:
>
> Cannot register non aspect: ....
>
> So, I wonder if there is any way to tell AJDT export wizard to allow for
> binary cycles just as JDT one does.
>
> Thank you very much for your time.
> Gaston.
Re: Binary cycles while exporting RCP product [message #600177 is a reply to message #74388] Fri, 03 July 2009 15:17 Go to previous message
Eclipse User
Originally posted by: gaston.tonietti.teracode.com

Thanks for answering Andrew. I've added myself to the CC list of the bug.

But I still have the problem, I'm not able to export my product with aspects support. Do you know what I am doing in the meanwhile? I have to copy compiled aspects from my project output folder into the plugin jar
inside the product zip :O (thanks Midnight Commander for supporting that!!). So every time I have to export a new Milestone, it is a pain you know where :-)

I also have to make a headless build to work. I have it working after following instructions from Andrew Niefer' blog "Building p2 RCP products in Eclipse 3.5M6", but guess what... without aspects working :-)

I found a solution for that in https://bugs.eclipse.org/bugs/show_bug.cgi?id=252641#c12

I replaced this line:
<ant antfile="${eclipse.pdebuild.scripts}/productBuild/productBuild.xml " />
with this one:
<ant antfile="${ajdt.pdebuild.scripts}/productBuild/productBuild.xml " />

but I got this error:
BUILD FAILED
project-releng/buildProduct.xml:21: The following error occurred while executing this line:
project-releng/org.eclipse.ajdt.pde.build_1.6.3.200808060918 /scripts/productBuild/productBuild.xml:20: The following error occurred while executing this line:
project-releng/org.eclipse.ajdt.pde.build_1.6.3.200808060918 /scripts/build.xml:46: The following error occurred while executing this line:
project-releng/org.eclipse.ajdt.pde.build_1.6.3.200808060918 /templates/headless-build/customTargets.xml:73: The following error occurred while executing this line:
project-releng/org.eclipse.ajdt.pde.build_1.6.3.200808060918 /templates/headless-build/customTargets.xml:18: java.net.MalformedURLException: no protocol: ${eclipseBaseURL}

I also tried replacing with this line as the bug comment says:
<ant antfile="${ajdt.pdebuild.scripts}/build.xml" />

but I got this error:
BUILD FAILED
project-releng/buildProduct.xml:21: The following error occurred while executing this line:
project-releng/org.eclipse.ajdt.pde.build_1.6.3.200808060918 /scripts/build.xml:28: The following error occurred while executing this line:
project-releng/org.eclipse.ajdt.pde.build_1.6.3.200808060918 /scripts/build.xml:68: The following error occurred while executing this line:
project-releng/org.eclipse.ajdt.pde.build_1.6.3.200808060918 /templates/headless-build/customTargets.xml:12: The following error occurred while executing this line:
project-releng/org.eclipse.ajdt.pde.build_1.6.3.200808060918 /templates/headless-build/allElements.xml:16: The following error occurred while executing this line:
project-releng/org.eclipse.ajdt.pde.build_1.6.3.200808060918 /scripts/genericTargets.xml:88: java.lang.NoSuchMethodError: org.eclipse.pde.internal.build.BundleHelper.getRuntimeJavaPr ofiles()[Ljava/lang/String;

So, just for you to know, I'm using Galileo release with the proper AJDT version 2.0.0 and it seems that this build plugin is for AJDT 1.6.3. Am I right?
So I would like to know if there is any update of the AJDT PDE Build but for last AJDT version 2.0.0 and if it supports the same that PDE one does, such as p2 repository generation.

Thanks a lot.
Gaston.


Andrew Eisenberg wrote:

> Binary cycles when exporting are not currently supported in AJDT, but
> there is a bug open for this:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=268667
>
> There is a patch, which I am planning on integrating soon. Please add
> your name to the cc there and you will be notified of its progress.
>
> The patch will only be applied to the 3.5 stream as Eclipse 3.4 does not
> allow binary cycles.
>
>
> On 02/07/09 9:02 AM, in article h2ilm2$u5h$1@build.eclipse.org, "Gaston M.
> Tonietti" <gaston.tonietti@teracode.com> wrote:
>
>> Hi guys,
>>
>> I have a problem when I want to export my RCP product.
>>
>> As I have some aspects in my project I tried to export it using "Eclipse
>> product with AspectJ support" export wizard, but the export
>> fails with the following error:
>>
>> Export feature error
>> A cycle was detected when generating the classpath ...
>>
>> I know this problem is fixed in JDT. "Eclipse product" export wizard has
>> a nice and useful checkbox called "Allow for binary cycles in
>> target platform", but if I use this wizard I don't have any aspect in the
>> exported product, compiled aspects are not present in the
>> plug-in jar so I get this error at startup:
>>
>> Cannot register non aspect: ....
>>
>> So, I wonder if there is any way to tell AJDT export wizard to allow for
>> binary cycles just as JDT one does.
>>
>> Thank you very much for your time.
>> Gaston.
Re: Binary cycles while exporting RCP product [message #600183 is a reply to message #74406] Fri, 03 July 2009 17:55 Go to previous message
Andrew Eisenberg is currently offline Andrew Eisenberg
Messages: 77
Registered: July 2009
Member
On 03/07/09 8:17 AM, in article h2l7f3$h1$1@build.eclipse.org, "Gaston M.
Tonietti" <gaston.tonietti@teracode.com> wrote:

> Thanks for answering Andrew. I've added myself to the CC list of the bug.
This bug has now been fixed. Let me know if this addresses your
non-headless build issues.


>
> So, just for you to know, I'm using Galileo release with the proper AJDT
> version 2.0.0 and it seems that this build plugin is for AJDT 1.6.3. Am I
> right?
Yes. This plugin is not officially supported by us. We put it out there
because some people were asking for it. We use it (and a 3.5 version) to
build AJDT itself.

> So I would like to know if there is any update of the AJDT PDE Build but for
> last AJDT version 2.0.0 and if it supports the same that PDE one does, such as
> p2 repository generation.
>
I can package one up for you and post it to that bug report. I don't think
I can get to it today, but early next week.

Eventually, I may have to release it as a feature on the update site.
Re: Binary cycles while exporting RCP product [message #600196 is a reply to message #74424] Fri, 03 July 2009 18:50 Go to previous message
Eclipse User
Originally posted by: gaston.tonietti.teracode.com

Comments inline.

Andrew Eisenberg wrote:

>
>
>
> On 03/07/09 8:17 AM, in article h2l7f3$h1$1@build.eclipse.org, "Gaston M.
> Tonietti" <gaston.tonietti@teracode.com> wrote:
>
>> Thanks for answering Andrew. I've added myself to the CC list of the bug.
> This bug has now been fixed. Let me know if this addresses your
> non-headless build issues.
I got the bugzilla mail. Good news. What should I do to try it out? download
a nightly build of AJDT for Galileo? or it is already published thru the
update site.
>
>
>>
>> So, just for you to know, I'm using Galileo release with the proper AJDT
>> version 2.0.0 and it seems that this build plugin is for AJDT 1.6.3. Am I
>> right?
> Yes. This plugin is not officially supported by us. We put it out there
> because some people were asking for it. We use it (and a 3.5 version) to
> build AJDT itself.
>
>> So I would like to know if there is any update of the AJDT PDE Build but
>> for last AJDT version 2.0.0 and if it supports the same that PDE one
>> does, such as p2 repository generation.
>>
> I can package one up for you and post it to that bug report. I don't
> think I can get to it today, but early next week.
Early next week would be pretty fine for me. I'm adding myself to this bug's
CC list right now so I get notified when you post it.
>
> Eventually, I may have to release it as a feature on the update site.
It would be really cool. There would be lot of people using aspectj in RCP
products who need to build "headlesslly"

Last question.
Is this build delegating on PDE one so it only replaces PDE for compiling?
I ask it to know if I must contact you for problems (not related to
AspectsJ) in the headless build process if I'm using this script or I should
contact PDE folks.

Tank you very much for all your help. You have been very kind.
Gaston.
Re: Binary cycles while exporting RCP product [message #600206 is a reply to message #74441] Fri, 03 July 2009 20:40 Go to previous message
Andrew Eisenberg is currently offline Andrew Eisenberg
Messages: 77
Registered: July 2009
Member
> I got the bugzilla mail. Good news. What should I do to try it out? download
> a nightly build of AJDT for Galileo? or it is already published thru the
> update site.

It will be available from the dev update site:
http://download.eclipse.org/tools/ajdt/35/dev/update

It is not available yet, but should be within a few hours. Look at the time
stamp for the build available from the site to see if it is the one produced
today.

> Early next week would be pretty fine for me. I'm adding myself to this bug's
> CC list right now so I get notified when you post it.
Good.

> It would be really cool. There would be lot of people using aspectj in RCP
> products who need to build "headlesslly"

Well, when I asked on the bug report and on the mailing list who would be
interested in having this feature available from the update site, I got no
responses, so I assumed there was little interest.

>
> Last question.
> Is this build delegating on PDE one so it only replaces PDE for compiling?
> I ask it to know if I must contact you for problems (not related to
> AspectsJ) in the headless build process if I'm using this script or I should
> contact PDE folks.
What we do, and this is the reason why it is not "officially" supported, is
that we branch the PDE build plugin and make the appropriate changes so that
AJDT can be built. The only substantial change that we have made is to
delegate to ajc instead of javac, but this small change cascades into a few
other changes elsewhere in the plugin.

It will probably work on other projects, but we have not tested it in detail
(nor do we have the capacity to).

--a
Re: Binary cycles while exporting RCP product [message #600215 is a reply to message #74459] Tue, 07 July 2009 05:41 Go to previous message
Eclipse User
Originally posted by: gaston.tonietti.teracode.com

Hi Andrew,

I did the update, I got AspectJ Development Tools 2.0.1.e35x-20090704-2000, but I'm still having problems.

I have no checkbox for allowing cycles in "Export Eclipse Product with AspectJ support". It is not an issue as now it does not fail due cycles anymore.
I saw it in "Export deployable plug-ins and fragments with AspectJ support" but I need to export it as an eclipse product.

The problem is that I have no compiled aspects in the exported product, I have only .aj files and sometimes a compilation error in a temporary build.xml (line 210) which is created in the project root, it does not
happen with regular PDE product export.

I would like to clarify something, I don't know if it matters:
I don't have aspects in the product I'm exporting, but in another project
which the product depends on.

WS structure (simplified :-) )
- domain (with aspects)
- ui (the product, depending on domain)

Let me know if I'm doing something wrong. Anyway, I can wait until you post the scripts for headless building {IReminder reminder = (IReminder) gaston;} :-)
Thanks again

Gaston.


Andrew Eisenberg wrote:

>
>
>
>> I got the bugzilla mail. Good news. What should I do to try it out?
>> download a nightly build of AJDT for Galileo? or it is already published
>> thru the update site.
>
> It will be available from the dev update site:
> http://download.eclipse.org/tools/ajdt/35/dev/update
>
> It is not available yet, but should be within a few hours. Look at the
> time stamp for the build available from the site to see if it is the one
> produced today.
>
>> Early next week would be pretty fine for me. I'm adding myself to this
>> bug's CC list right now so I get notified when you post it.
> Good.
>
>> It would be really cool. There would be lot of people using aspectj in
>> RCP products who need to build "headlesslly"
>
> Well, when I asked on the bug report and on the mailing list who would be
> interested in having this feature available from the update site, I got no
> responses, so I assumed there was little interest.
>
>>
>> Last question.
>> Is this build delegating on PDE one so it only replaces PDE for
>> compiling? I ask it to know if I must contact you for problems (not
>> related to AspectsJ) in the headless build process if I'm using this
>> script or I should contact PDE folks.
> What we do, and this is the reason why it is not "officially" supported,
> is that we branch the PDE build plugin and make the appropriate changes so
> that
> AJDT can be built. The only substantial change that we have made is to
> delegate to ajc instead of javac, but this small change cascades into a
> few other changes elsewhere in the plugin.
>
> It will probably work on other projects, but we have not tested it in
> detail (nor do we have the capacity to).
>
> --a
Re: Binary cycles while exporting RCP product [message #600225 is a reply to message #74477] Wed, 08 July 2009 04:00 Go to previous message
Andrew Eisenberg is currently offline Andrew Eisenberg
Messages: 77
Registered: July 2009
Member
Hi Gaston,

I added a new attachment to the bug report that has the updated ajdt pde
build plugin 3.5:
https://bugs.eclipse.org/252641

> I have no checkbox for allowing cycles in "Export Eclipse Product with AspectJ
> support". It is not an issue as now it does not fail due cycles anymore.
> I saw it in "Export deployable plug-ins and fragments with AspectJ support"
> but I need to export it as an eclipse product.
Yes. There is no check box for it. The change I made turned on the flag by
default (with no way of disabling it). Bug 282391 is about adding UI
support for this.

> I would like to clarify something, I don't know if it matters:
> I don't have aspects in the product I'm exporting, but in another project
> which the product depends on.

Yes, this may be an issue. How do you have this set up? Is the other
project on the aspect path? Is it another plugin project?

Right click on the manifest file for the plugin and select "Generate build
file with AspectJ support". Make sure that the project that you expect is
on the aspect path.

--a
Re: Binary cycles while exporting RCP product [message #600237 is a reply to message #74495] Wed, 08 July 2009 07:13 Go to previous message
Eclipse User
Originally posted by: gaston.tonietti.teracode.com

Ok. I tried to build the product using scripts from ajdt-pde-build plugin but it fails:
org.eclipse.ajdt.pde.build_2.0.1.200907072043/templates/head less-build/customTargets.xml:18: java.net.MalformedURLException: no protocol:
${eclipseBaseURL}

But I think I understood what you said, so I created the build file in the project having the aspects, it generates a @dot folder with compiled aspects
all right, and I built the product with the regular pdebuild script, thinking it will use the existing build.xml for the project with the aspects, but it
wasn't this way :-( , this file was overridden by one without AspectJ support.

So I don't know what else to do.

My setup is, at least the part which matters now (I have more plug-in projects not related to this problem), a plug-in project with AspectJ capability
called domain and an RCP product project called ui. Domain doesn't know anything about ui, while ui depends on domain (using Required-Bundles header) and
uses Equinox Aspects for weaving at runtime. All this is working great in development.

So my problem is, that I get the domain plug-in jar with the MyAspect.aj file instead of the compiled one MyAspect.class, due that, weaving hook fails
registering the aspect:
Cannot register non aspect: MyAspect , MyAspect

So what can I do in order to get an exported product with a domain plug-in jar containing proper aspect class?

Thanks a lot Andrew.
Gaston.

Andrew Eisenberg wrote:

> Hi Gaston,
>
> I added a new attachment to the bug report that has the updated ajdt pde
> build plugin 3.5:
> https://bugs.eclipse.org/252641
>
>> I have no checkbox for allowing cycles in "Export Eclipse Product with
>> AspectJ support". It is not an issue as now it does not fail due cycles
>> anymore. I saw it in "Export deployable plug-ins and fragments with
>> AspectJ support" but I need to export it as an eclipse product.
> Yes. There is no check box for it. The change I made turned on the flag
> by
> default (with no way of disabling it). Bug 282391 is about adding UI
> support for this.
>
>> I would like to clarify something, I don't know if it matters:
>> I don't have aspects in the product I'm exporting, but in another project
>> which the product depends on.
>
> Yes, this may be an issue. How do you have this set up? Is the other
> project on the aspect path? Is it another plugin project?
>
> Right click on the manifest file for the plugin and select "Generate build
> file with AspectJ support". Make sure that the project that you expect is
> on the aspect path.
>
> --a
Re: Binary cycles while exporting RCP product [message #600249 is a reply to message #74512] Wed, 08 July 2009 16:18 Go to previous message
Andrew Eisenberg is currently offline Andrew Eisenberg
Messages: 77
Registered: July 2009
Member
> Ok. I tried to build the product using scripts from ajdt-pde-build plugin but
> it fails:
> org.eclipse.ajdt.pde.build_2.0.1.200907072043/templates/head less-build/customT
> argets.xml:18: java.net.MalformedURLException: no protocol:
> ${eclipseBaseURL}
The problem here is that you have not set the variable eclipseBaseURL. It
should point to the target eclipse zip file that you are building against.
Note that this should be in URL format. So, eg:
file:/home/build/Eclipses/myEclipse.zip

This doesn't need to be called. See the getBaseComponents target in
customTargets.xml.
Re: Binary cycles while exporting RCP product [message #600268 is a reply to message #74530] Wed, 08 July 2009 19:46 Go to previous message
Eclipse User
Originally posted by: gaston.tonietti.teracode.com

Thank to point me out this, I'm skipping it now so that problem is solved, but I have a new one now:

generateScript:

BUILD FAILED
releng/buildProduct.xml:22: The following error occurred while executing this line:
releng/org.eclipse.ajdt.pde.build_2.0.1.200907072043/scripts /productBuild/productBuild.xml:28: The following error occurred while executing this line:
releng/org.eclipse.ajdt.pde.build_2.0.1.200907072043/scripts /build.xml:68: The following error occurred while executing this line:
releng/org.eclipse.ajdt.pde.build_2.0.1.200907072043/templat es/headless-build/customTargets.xml:12: The following error occurred while executing this line:
releng/org.eclipse.ajdt.pde.build_2.0.1.200907072043/scripts /productBuild/allElements.xml:10: The following error occurred while executing this line:
releng/org.eclipse.ajdt.pde.build_2.0.1.200907072043/scripts /genericTargets.xml:88: java.lang.NoSuchMethodError: org.eclipse.pde.internal.build.BundleHelper.getRuntimeJavaPr ofiles()[Ljava/lang/String;

Any idea? is it using the wrong jar?

Thanks again.
Gaston.

Andrew Eisenberg wrote:

>> Ok. I tried to build the product using scripts from ajdt-pde-build plugin
>> but it fails:
>> org.eclipse.ajdt.pde.build_2.0.1.200907072043/templates/head less-build/customT
>> argets.xml:18: java.net.MalformedURLException: no protocol:
>> ${eclipseBaseURL}
> The problem here is that you have not set the variable eclipseBaseURL. It
> should point to the target eclipse zip file that you are building against.
> Note that this should be in URL format. So, eg:
> file:/home/build/Eclipses/myEclipse.zip
>
> This doesn't need to be called. See the getBaseComponents target in
> customTargets.xml.
Re: Binary cycles while exporting RCP product [message #600288 is a reply to message #74548] Wed, 08 July 2009 21:23 Go to previous message
Andrew Eisenberg is currently offline Andrew Eisenberg
Messages: 77
Registered: July 2009
Member
Don't know what is going on here. The call to the method that is invalid,
existed in the 3.4 version, but does not exist in the 3.5 version. Perhaps
you are picking up the wrong jar (ie- the 3,.4 jar). Make sure that the old
pluign is completely wiped from your workspace. And try running once with
-clean to ensure that the jar wasn't cached anywhere.

If that still doesn't work, I will recreate the plugin for you from scratch
and make sure that the proper jar is in there.


On 08/07/09 12:46 PM, in article h32t2c$s5$1@build.eclipse.org, "Gaston M.
Tonietti" <gaston.tonietti@teracode.com> wrote:

> Thank to point me out this, I'm skipping it now so that problem is solved, but
> I have a new one now:
>
> generateScript:
>
> BUILD FAILED
> releng/buildProduct.xml:22: The following error occurred while executing this
> line:
> releng/org.eclipse.ajdt.pde.build_2.0.1.200907072043/scripts /productBuild/prod
> uctBuild.xml:28: The following error occurred while executing this line:
> releng/org.eclipse.ajdt.pde.build_2.0.1.200907072043/scripts /build.xml:68: The
> following error occurred while executing this line:
> releng/org.eclipse.ajdt.pde.build_2.0.1.200907072043/templat es/headless-build/
> customTargets.xml:12: The following error occurred while executing this line:
> releng/org.eclipse.ajdt.pde.build_2.0.1.200907072043/scripts /productBuild/allE
> lements.xml:10: The following error occurred while executing this line:
> releng/org.eclipse.ajdt.pde.build_2.0.1.200907072043/scripts /genericTargets.xm
> l:88: java.lang.NoSuchMethodError:
> org.eclipse.pde.internal.build.BundleHelper.getRuntimeJavaPr ofiles()[Ljava/lan
> g/String;
>
> Any idea? is it using the wrong jar?
>
> Thanks again.
> Gaston.
>
> Andrew Eisenberg wrote:
>
>>> Ok. I tried to build the product using scripts from ajdt-pde-build plugin
>>> but it fails:
>>> org.eclipse.ajdt.pde.build_2.0.1.200907072043/templates/head less-build/custo
>>> mT
>>> argets.xml:18: java.net.MalformedURLException: no protocol:
>>> ${eclipseBaseURL}
>> The problem here is that you have not set the variable eclipseBaseURL. It
>> should point to the target eclipse zip file that you are building against.
>> Note that this should be in URL format. So, eg:
>> file:/home/build/Eclipses/myEclipse.zip
>>
>> This doesn't need to be called. See the getBaseComponents target in
>> customTargets.xml.
>
Re: Binary cycles while exporting RCP product [message #600296 is a reply to message #74566] Thu, 09 July 2009 06:58 Go to previous message
Eclipse User
Originally posted by: gaston.tonietti.teracode.com

Hi Andrew, finally I was able to build the product.

It was just as you said, I had the old plugin in my dropins, so I removed it and installed the new one and it worked.
I had a little problem when assembling, it tried to find the launcher icon in a folder inside buldDirectory but it wasn't there, I could fix it creating a soft link pointing to the folder it looked for (not
that nice).

I got the product exported, with aspects working great, but I lost a very important thing, repository generation and p2 director invocation. It seems that ajdt-pde-build is ignoring the property
p2.gathering

Do you know how I can get it back?
Can I use AJDT Build just for the plug-in which needs it (domain project) and build the product and the other plug-ins with the regular PDE Build? I tried, but build.xml with aspectj support which I
generate in domain project is overridden when I run the product build. If I make it read only the build fails.

Thank you so much for all your help. I really appreciate it.
Gaston.


Andrew Eisenberg wrote:

> Don't know what is going on here. The call to the method that is invalid,
> existed in the 3.4 version, but does not exist in the 3.5 version.
> Perhaps
> you are picking up the wrong jar (ie- the 3,.4 jar). Make sure that the
> old
> pluign is completely wiped from your workspace. And try running once with
> -clean to ensure that the jar wasn't cached anywhere.
>
> If that still doesn't work, I will recreate the plugin for you from
> scratch and make sure that the proper jar is in there.
>
>
> On 08/07/09 12:46 PM, in article h32t2c$s5$1@build.eclipse.org, "Gaston M.
> Tonietti" <gaston.tonietti@teracode.com> wrote:
>
>> Thank to point me out this, I'm skipping it now so that problem is
>> solved, but I have a new one now:
>>
>> generateScript:
>>
>> BUILD FAILED
>> releng/buildProduct.xml:22: The following error occurred while executing
>> this line:
>> releng/org.eclipse.ajdt.pde.build_2.0.1.200907072043/scripts /productBuild/prod
>> uctBuild.xml:28: The following error occurred while executing this line:
>> releng/org.eclipse.ajdt.pde.build_2.0.1.200907072043/scripts /build.xml:68:
>> The following error occurred while executing this line:
>> releng/org.eclipse.ajdt.pde.build_2.0.1.200907072043/templat es/headless-build/
>> customTargets.xml:12: The following error occurred while executing this
>> line:
>> releng/org.eclipse.ajdt.pde.build_2.0.1.200907072043/scripts /productBuild/allE
>> lements.xml:10: The following error occurred while executing this line:
>> releng/org.eclipse.ajdt.pde.build_2.0.1.200907072043/scripts /genericTargets.xm
>> l:88: java.lang.NoSuchMethodError:
>> org.eclipse.pde.internal.build.BundleHelper.getRuntimeJavaPr ofiles()[Ljava/lan
>> g/String;
>>
>> Any idea? is it using the wrong jar?
>>
>> Thanks again.
>> Gaston.
>>
>> Andrew Eisenberg wrote:
>>
>>>> Ok. I tried to build the product using scripts from ajdt-pde-build
>>>> plugin but it fails:
>>>> org.eclipse.ajdt.pde.build_2.0.1.200907072043/templates/head less-build/custo
>>>> mT
>>>> argets.xml:18: java.net.MalformedURLException: no protocol:
>>>> ${eclipseBaseURL}
>>> The problem here is that you have not set the variable eclipseBaseURL.
>>> It should point to the target eclipse zip file that you are building
>>> against.
>>> Note that this should be in URL format. So, eg:
>>> file:/home/build/Eclipses/myEclipse.zip
>>>
>>> This doesn't need to be called. See the getBaseComponents target in
>>> customTargets.xml.
>>
Re: Binary cycles while exporting RCP product [message #600318 is a reply to message #74584] Thu, 09 July 2009 17:40 Go to previous message
Andrew Eisenberg is currently offline Andrew Eisenberg
Messages: 77
Registered: July 2009
Member
Glad to hear that you got it working.

> I got the product exported, with aspects working great, but I lost a very
> important thing, repository generation and p2 director invocation. It seems
> that ajdt-pde-build is ignoring the property
> p2.gathering

That property is not supported by the build scripts currently. I raised a
bug to track this:
http://bugs.eclipse.org/283054

How important for you is having this property available in your AJDT
headless build scripts? This is not a trivial enhancement, and I need to
know how to rank it in importance.
Re: Binary cycles while exporting RCP product [message #600337 is a reply to message #74601] Thu, 09 July 2009 17:56 Go to previous message
Eclipse User
Originally posted by: gaston.tonietti.teracode.com

It depends on the answer to my other question.

If I can handle product export with the regular PDE Build while using AJDT
Build for just those plug-ins having aspects, it is not important.

I think it makes more sense to do it this way as it is using ajc for all
projects, even for those which I know that don't have any aspect.

Is there any way to address it this way?

Thanks.
Gaston.

Andrew Eisenberg wrote:

> Glad to hear that you got it working.
>
>> I got the product exported, with aspects working great, but I lost a very
>> important thing, repository generation and p2 director invocation. It
>> seems that ajdt-pde-build is ignoring the property
>> p2.gathering
>
> That property is not supported by the build scripts currently. I raised a
> bug to track this:
> http://bugs.eclipse.org/283054
>
> How important for you is having this property available in your AJDT
> headless build scripts? This is not a trivial enhancement, and I need to
> know how to rank it in importance.
Re: Binary cycles while exporting RCP product [message #600348 is a reply to message #74619] Thu, 09 July 2009 20:26 Go to previous message
Andrew Eisenberg is currently offline Andrew Eisenberg
Messages: 77
Registered: July 2009
Member
> If I can handle product export with the regular PDE Build while using AJDT
> Build for just those plug-ins having aspects, it is not important.
>
> I think it makes more sense to do it this way as it is using ajc for all
> projects, even for those which I know that don't have any aspect.
>
> Is there any way to address it this way?

I don't know. Can you export your aspect plugins separately from your
non-aspect plugins?

This might be a question better asked on the pde mailing list.
Re: Binary cycles while exporting RCP product [message #600357 is a reply to message #74637] Fri, 10 July 2009 05:54 Go to previous message
Eclipse User
Originally posted by: gaston.tonietti.teracode.com

Ok Andrew, I'll try with the PDE folks. Thank you so much for all your help. It was very kind of you.

Gaston.

Andrew Eisenberg wrote:

>
>
>
>> If I can handle product export with the regular PDE Build while using
>> AJDT Build for just those plug-ins having aspects, it is not important.
>>
>> I think it makes more sense to do it this way as it is using ajc for all
>> projects, even for those which I know that don't have any aspect.
>>
>> Is there any way to address it this way?
>
> I don't know. Can you export your aspect plugins separately from your
> non-aspect plugins?
>
> This might be a question better asked on the pde mailing list.
Re: Binary cycles while exporting RCP product [message #600369 is a reply to message #74655] Fri, 10 July 2009 07:15 Go to previous message
Andrew Eisenberg is currently offline Andrew Eisenberg
Messages: 77
Registered: July 2009
Member
No problem. Let me know how it goes with the pde team. If they can't help,
come back here, raise a bug, and I will try to find some time to look into
it.


On 09/07/09 10:54 PM, in article h36l2b$g68$1@build.eclipse.org, "Gaston M.
Tonietti" <gaston.tonietti@teracode.com> wrote:

> Ok Andrew, I'll try with the PDE folks. Thank you so much for all your help.
> It was very kind of you.
>
> Gaston.
>
> Andrew Eisenberg wrote:
>
>>
>>
>>
>>> If I can handle product export with the regular PDE Build while using
>>> AJDT Build for just those plug-ins having aspects, it is not important.
>>>
>>> I think it makes more sense to do it this way as it is using ajc for all
>>> projects, even for those which I know that don't have any aspect.
>>>
>>> Is there any way to address it this way?
>>
>> I don't know. Can you export your aspect plugins separately from your
>> non-aspect plugins?
>>
>> This might be a question better asked on the pde mailing list.
>
Previous Topic:Binary cycles while exporting RCP product
Next Topic:Critical:Cross reference view and editor line clutter show incorrect info
Goto Forum:
  


Current Time: Wed Oct 22 01:55:44 GMT 2014

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

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