Re: [p2-dev] director and eclipse.p2.data.area

[DJ Houghton <DJ_Houghton@xxxxxxxxxx>]

Hi Scott. As you noticed we had similar problems and ended up calling <exec>. I think this is the original bug report: https://bugs.eclipse.org/bugs/show_bug.cgi?id=209185
Feel free to open a new one to enable the tasks to be run in-process.

dj

Scott Lewis <slewis@xxxxxxxxx>

Scott Lewis <slewis@xxxxxxxxx>
Sent by: p2-dev-bounces@xxxxxxxxxxx

09/26/2008 12:57 PM

Please respond to
slewis@xxxxxxxxx; Please respond to
P2 developer discussions <p2-dev@xxxxxxxxxxx>

To	Francis Upton <francisu@xxxxxxxx>
cc	P2 developer discussions <p2-dev@xxxxxxxxxxx>
Subject	Re: [p2-dev] director and eclipse.p2.data.area

Hi Francis,

Thanks much Francis...for the moment I am doing what you are doing.

Should an enhancement request be made (against director?) to support 
in-process director execution?...as the current makes the p2.director 
task (in PDE) sort of useless for certain use cases (non-eclipse).

Thanks,

Scott

Francis Upton wrote:
> Here is how I do it, note that the eclipse.p2.data.area must be a Java 
> system property:
>
>                <exec executable="${baseLocation}/eclipse" 
> failonerror="true" timeout="60000" logError="true" output="director.txt">
>                    <arg line="-application 
> org.eclipse.equinox.p2.director.app.application" />
>                    <arg line="-nosplash" />
>                    <arg line="--launcher.suppressErrors" />
>                    <arg line="-consolelog" />
>                    <arg line="-flavor tooling" />
>                    <arg line="-installIU 
> com.oaklandsw.transform.product${productNumber}" />
>                    <arg line="-p2.os ${confOs}" />
>                    <arg line="-p2.ws ${confGui}" />
>                    <arg line="-p2.arch ${confArch}" />
>                    <arg line="-roaming" />
>                    <arg line="-profile OSDTProfile" />
>                    <arg line="-profileProperties 
> org.eclipse.update.install.features=true" />
>                    <arg line="-metadataRepository ${p2.metadata.repo}" />
>                    <arg line="-artifactRepository ${p2.artifact.repo}" />
>                    <arg line="-destination 
> ${builder}/${buildLabel}/${collectingFolder}-kits/${confOutDir}" />
>                    <arg line="-bundlepool 
> ${builder}/${buildLabel}/${collectingFolder}-kits/${confOutDir}" />
>                    <arg line="-vmargs" />
>                    <arg line="-Xmx400m" />
>                    <arg 
> line="-Declipse.p2.data.area=${builder}/${buildLabel}/${collectingFolder}-kits/${confOutDir}/p2" 
> />
>                    <arg line="-Declipse.p2.profile="" />
>                    <!--    <arg line="-Xdebug -Xnoagent 
> -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=8888" />-->
>                </exec>
>
> Also note that I have yet to get this whole thing working correctly, 
> so take this as a starting point rather than the gospel.
>
> Francis
>
>
> Scott Lewis wrote:
>> Hi Folks,
>>
>> I'm attempting to run the p2.director ant task and have found a 
>> problem.  I would like to set the eclipse.p2.data.area to some 
>> location *other* than the default that's specfied by eclipse, and the 
>> AntRunner runs in the eclipse process...so when I run the director is 
>> uses the wrong location for the eclipse.p2.data.area.
>>
>> Is it possible to run the p2.director ant task from within Eclipse 
>> and use an alternative p2.data.area?  I'm trying now to run/exec the 
>> director in a separate ant 'exec' call (as the Eclipse build does it) 
>> rather than p2.director task, and set the eclipse.p2.data.area 
>> explicitly.
>>
>> Thanks,
>>
>> Scott
>>
>>
>> _______________________________________________
>> p2-dev mailing list
>> p2-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/p2-dev
>>
>
>

_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev