Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [p2-dev] Testing P2 without SELF_Profile

Unfortunately, depending on what you want to achieve, this may not always work (see mail from Gunnar on Friday, July 23rd)
In this case, a trick consist in exporting your application once, and starting your selfhosting instance with the following VM Args:
	-Declipse.p2.data.area=<fileURLTop2FolderOfTheExportedApplication>
	-Declipse.p2.profile=<profileId>

On 2010-07-22, at 4:34 PM, Eugen Reiswich wrote:

> Thanks Darin,
> 
> glad to hear about this option. That will safe me a lot of time!!!
> 
> Eugen
> 
> Am Jul 21, 2010 um 15:17  schrieb Darin Wright:
> 
>>> 
>>> I am developing a RCP+P2 application and wonder what's the best way 
>>> to test such an application. As far as I understand I need to deploy
>>> my RCP+P2 application before I can test it as P2 requires a profile 
>>> when installing/updating etc. software. This profile is NULL when 
>>> testing within Eclipse IDE so debugging in IDE is not possible for me 
>> yet. 
>>> 
>>> Is there a way to test P2 without deployment e.g. mock a profile?
>>> 
>> 
>> In 3.6, on the Eclipse Application Configuration tab, you can check the 
>> "Support software installation in the launched application" option. This 
>> will mock up a profile in the launched target.
>> 
>> Darin
>> _______________________________________________
>> 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



Back to the top