If there is a way to customize idea.properties without altering the .app,
then I think that should be sufficient for our needs. Can't wait for RC3
:).
I don't really want to re-package per-se, mostly just automate distribution
within an enterprise environment in order to minimize time spent per
developer on project setup.
Thanks!
-Dallin
On Thursday, December 4, 2014 12:33:38 PM UTC-6, Siva Velusamy wrote:
>
> Just as an FYI, part of the reason for doing this is that if you are on a
> Mac, then touching anything within the .app folder will cause its code
> signature to become invalid. (This is new as of OS X 10.9.5+). If its code
> signature is invalid, then you'll have various issues including some users
> not even being able to run the app. So this affects you whether you do
> something as simple as modifying idea.properties inside the .app or adding
> new plugins.
>
> With RC3, we should have a way to provide custom idea.properties without
> altering the .app.
>
> If you really want to provide a custom distribution, then your only
> recourse is to handle all of the admin work yourself, including packaging
> and re-signing the .app, and then providing the updates yourself. As far as
> I know, there is no simple way to achieve what you want. I'd recommend
> filing an issue at youtrack.jetbrains.com..
>
>
>
> On Thu, Dec 4, 2014 at 8:37 AM, Dallin Wilcox <dcwi...@gmail.com
> <javascript:>> wrote:
>
>> I guess a follow-on question would be does IntelliJ/Studio support an
>> equivalent to the Eclipse links folder for plugins? If there were
>> something like that available that could solve the problem.
>>
>>
>> On Thursday, December 4, 2014 10:30:29 AM UTC-6, Dallin Wilcox wrote:
>>>
>>> Ideally I want to create a software package that can be pushed to
>>> multiple developer's machines (one for Mac and one for Windows).
>>> Installing the plugin in the user directory defeats the purpose since we
>>> want it to be a complete batteries-included start up process so our devs
>>> don't each have to do individual setup/configuration (i.e. installing
>>> plugins) before they can get to coding. Sorry I probably should have
>>> included that context up front :).
>>>
>>> One alternative would be to just create a new package for each update,
>>> but I don't want to preclude the developers from patching themselves since
>>> our internal packaging process can be rather slow at times.
>>>
>>> Dallin
>>>
>>> On Wednesday, December 3, 2014 12:58:55 PM UTC-6, Esteban de la Canal
>>> wrote:
>>>>
>>>> Hi Dalliin,
>>>>
>>>> Android Studio plugins are already outside the installation folder.
>>>> When you install a plugin through the IDE it goes to your own,
>>>> user-specific, directory. If you manually install a plugin (not
>>>> recommended) you should place it in the directories listed bellow.
>>>> However,
>>>> it's better to install it from the IDE.
>>>> Do not change the properties file, as that directory is basically
>>>> already pointing to a place outside the android studio installation
>>>> folder.
>>>> I don't know which platform you are running studio on, but these are the
>>>> locations for the plugin folder you should be looking at:
>>>>
>>>> Linux: ~/.AndroidStudio/config/plugins
>>>> Windows: ~/.AndroidStudio/config/plugins
>>>> Mac: ~/Library/Application Support/AndroidStudio
>>>>
>>>> On Wednesday, December 3, 2014 10:04:10 AM UTC-8, Dallin Wilcox wrote:
>>>>>
>>>>> 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 <dcwi...@gmail.com>
>>>>>>> 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 adt-dev+u...@googlegroups.com.
>>>>>>>> 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 adt-dev+u...@googlegroups.com <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
--
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 adt-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
