[news.eclipse.technology.ajdt] Re: Binary cycles while exporting RCP pro

["Gaston M. Tonietti" <gaston.tonietti@xxxxxxxxxxxx>]

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@xxxxxxxxxxxxxxxxx, "Gaston M.
> Tonietti" <gaston.tonietti@xxxxxxxxxxxx> 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/templates/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.getRuntimeJavaProfiles()[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/headless-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.
>>