1. We use SVN
2. Common > Global Project with filename.css is shared by Project A, Project B, and so forth.
3. We updated some styles in the Global CSS and commited the changes to SVN.
4. These changes are not reflected in any of our projects; yet, we have a red exclamation point on both of the following:
a. Project Organizer > Imports > ImportfromGlobal
b. Content > Resources > Stylesheets > filename.css.
No other changes to Projects A and B have been made.
Should we commit them hoping that the global changes will take affect, or re-import the global?
If we re-import, is it a good practice to re-import only the .css file rather than the entire global project?
Thanks in advance.
Global Project CSS: To re-import or not to re-import?
Global Project CSS: To re-import or not to re-import?
writeeditconsultingllc.com
WE make writing right.
WE make writing right.
-
doc_guy
- Propellus Maximus
- Posts: 1979
- Joined: Tue Nov 28, 2006 11:18 am
- Location: Crossroads of the West
- Contact:
Re: Global Project CSS: To re-import or not to re-import?
SVN isn't connected to the global project linking, so you will need to re-import those files into your working projects. Committing them to SVN as part of the global project won't bring them down into the child projects.
Every time you build, though, Flare will re-import the files in the global project, so if it looks like the local child project file was updated, it may be because you built one of the targets.
When you re-import, Flare will show you which files have changed, and if the changes in the global project are newer than the changes in the local project, and you get to choose which files you want to import. You only need to import files that have changes you want reflected in your child projects (though, ideally, you are only making changes in the global project that you WANT proliferated into all the child projects).
When I'm working with master projects, I leave the linked files alone, and make all necessary changes in the global project, or find a way to make them in the local project.
Every time you build, though, Flare will re-import the files in the global project, so if it looks like the local child project file was updated, it may be because you built one of the targets.
When you re-import, Flare will show you which files have changed, and if the changes in the global project are newer than the changes in the local project, and you get to choose which files you want to import. You only need to import files that have changes you want reflected in your child projects (though, ideally, you are only making changes in the global project that you WANT proliferated into all the child projects).
When I'm working with master projects, I leave the linked files alone, and make all necessary changes in the global project, or find a way to make them in the local project.
