Placing the plugins in external folders worked as expected, but it didn't 
go so well when we attempted to update to 1.0 RC2, in fact it broke the 
patch process completely.  The patch process detected that idea.properties 
had been modified and offered no solution (not even to replace the modified 
idea.properties file).  At that point the only option available was to 
cancel the patch.  I'll keep digging to see about other ways to configure 
external plugins that may be compatible with the patch process, but if 
anyone has any suggestions, they would be greatly appreciated.

On Wednesday, November 26, 2014 12:54:50 PM UTC-6, Dallin Wilcox wrote:
>
> Thanks Xavier,
>
> After some poking around I found that idea.properties (located in the bin 
> folder) lets me specify an external plugins folder.  I'll give that a shot 
> and see how it goes with the next patch.  Hopefully idea.properties doesn't 
> get replaced as well as part of the patch process.
>
> Relevant portion of idea.properties:
>  #---------------------------------------------------------------------
> # Uncomment this option if you want to customize path to user installed 
> plugins folder. Make sure you're using forward slashes. 
> #--------------------------------------------------------------------- 
> # idea.plugins.path=${idea.config.path}/plugins 
>
>  
>
> On Friday, November 21, 2014 11:20:09 AM UTC-6, Xavier Ducrohet wrote:
>>
>> Signing of Studio requires the Studio installation to not change. 
>> IntelliJ should be able to install additional plugin outside of the studio 
>> folder to avoid this.
>>
>> On Fri, Nov 21, 2014 at 6:33 AM, Dallin Wilcox <[email protected]> wrote:
>>
>>> I find it rather annoying that every time we patch Studio we are 
>>> presented with a dialog that basically forces deletion of all 
>>> user-installed plugins forcing us to re-install them after update.  I would 
>>> think at least an option for plugins to let them be would be a great 
>>> feature.
>>>
>>> Sy my question is... Why delete all plugins that don't come by default? 
>>> (I know there was an update a while back to remove orphaned empty 
>>> directories, perhaps it is related?)  Is there some sort of white list or 
>>> config we can add plugins to to avoid this?
>>>
>>> Thanks for all the great work and I'm excited for Studio to come out of 
>>> beta!
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "adt-dev" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to [email protected].
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> -- 
>> Xavier Ducrohet
>> Android SDK Tech Lead
>> Google Inc.
>> http://developer.android.com | http://tools.android.com
>>
>> Please do not send me questions directly. Thanks!
>>  
>

-- 
You received this message because you are subscribed to the Google Groups 
"adt-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to