Shared Scopes (really Shared anything)?

What is this feature and how does it work? The Shared function. How do I share a Scope with my team?

0
14 comments

Shared means that it will be stored in project meta info and thus visible by all team members, and non-shared will be stored in workspace file and is visible for its owner only.

0

"project meta info"

What does that mean? How would they access the "project meta info"? I mean, we all have separate workspaces. I'm confused.

0

Okay, take a few steps back %)

Did you noticed .idea folder in your project folder? That's the project meta data. If you include it in your source control all the team members will be able to share various settings including code style and inspection profile and scopes and some other settings.

The personal, non shared stuff resides inside workspace.xml and it SHOULD NOT be included in SC unless you're single person working on project.

0

Well, by default it's ignored (CVS), but you are saying that I should add the .idea folder to CVS, but ignore the workspace.xml file? Is that the only file we should ignore in that directory? I just want to be certain. We've tried that before with other apps, and had problems out the wazoo.

0

"add the .idea folder to CVS, but ignore the workspace.xml file"
that's exactly what I'm talking about.

Its designed to be used like that %)

0

I'm curious, if this is the designed method to "share" these, why doesn't PHPStorm show the .idea folder in the Project view

or allow for CVS to Add/Commit the files in this folder? To add these to CVS, I'll have to use a different client. I just want to make sure we are on the same page.

0

In case anyone else has this issue.

Because we have a huge project, and some developers only work within a branch and because we check out our branches into different folders to keep them straight, I found that I have to ignore:

workspace.xml
modules.xml
*.iml

As the .iml file name varies and points to different folder names, etc..

0

It's still not going to work correctly. Look at the misc.xml file:

<?xml version="1.0" encoding="UTF-8"?>

<project version="4">

<component name="DependencyValidationManager">

<scope name="CollectionsQueue" pattern="file[Intranet_Local]:library/classes/apps/Collections.php||file[Intranet_Local]:library/classes/DailyReports.php||file[Intranet_Local]:library/classes/RM5_Data_Update.php||file[Intranet_Local]:collections_queue_edit.php||file[Intranet_Local]:collections_queue.php||file[Intranet_Local]:rm5_data_update.php" />

<option name="SKIP_IMPORT_STATEMENTS" value="false" />

</component>

<component name="ProjectResources">

<default-html-doctype>http://www.w3.org/1999/xhtml</default-html-doctype>

</component>

<component name="ProjectRootManager" version="2" />

<component name="SvnBranchConfigurationManager">

<option name="mySupportsUserInfoFilter" value="true" />

</component>

</project>

Intranet_Local is the folder name and that changes (Intranet_TEAM1 for TEAM1 branch, etc.) So, this scope is not transportable. Is there a way to make the scope work on the CURRENT FOLDER?

0

Of course, I post and then figure it out:

file:library/classes/apps/Collections.php||file:library/classes/DailyReports.php||file:library/classes/RM5_Data_Update.php||file:collections_queue_edit.php||file:collections_queue.php||file:rm5_data_update.php

0

I'm still struggling a bit with settings. A couple of things that would help:

  • It would be nice if you could share scopes through the settings repository instead of the metadata folder. We never add the metadata folder to VCS because it's too likely to get checked in corrupted.
  • It would be nice if project settings could be synced with the settings repository. This would be a big help, actually.
  • Settings could be color-coded throughout the UI as project or global settings and synced with settings repo or local. I have trouble understanding these things.

    Jon

 

0

It would be nice if you could share scopes through the settings repository instead of the metadata folder

At the moment, scopes are project-level. Here's a request for global scopes: https://youtrack.jetbrains.com/issue/IDEA-261324

It would be nice if project settings could be synced with the settings repository. This would be a big help, actually.

Not considered at the moment.

We never add the metadata folder to VCS because it's too likely to get checked in corrupted.

I assume that you are talking about this one: https://youtrack.jetbrains.com/issue/IDEA-271728
It's a really unfortunate bug that for some reason gets almost no attention at all, I've tried to attract some to no avail.

0

Eugene Morozov Yeah, it is unfortunate. There are multiple ways to move settings from one IDE to another. My experience so far is that none of them really works. Even the import export failed for me today. It would be good to give this attention. Or maybe someone wants to add a killer sync app to the Marketplace. We'd pay.

0

Please sign in to leave a comment.