dotSoftwaredotDevelopmentdotCustomersdotAbout us
PushOk logoblank
bullet Home
bullet My software
bullet Support
bullet My payments
bullet My info
bullet Subscriptions
bullet Voting
bullet Contact us
fast linksFast Links
news&eventsnews and events

2012-12-21 
Major update of SVNCOM version 1.7.2 are finaly released

2012-12-21 
Major update of SVN SCC plug-in - versions 1.7.2 are finaly released

Lightweight embedded Node.js database with MongoDB API.

Ticket

Search go
PushOk Logo blank
leftTicketright

Unable to get new Source Controled Project containing Common Files

( CVSSCC )
Type: Public Status:Closed Created: 22 Jun 05 06:00 Updated: 23 Jun 05 06:00
--> Igor Pushkov (admin)  at 23 Jun 05 06:00 writes

By default VS.NET not designed to share files this way. It designed to
share entire projects. However sharing of common files are possible.
First _and very goog way_ is use unix file links, just creating symlinks
for shared files and virtually placing them into correct projects.
However the first solution cannot be used if your server is not unix based.

So, you still can share the files with one limitations. You repository
folder structure and local folder structure always should remain the same.
In other words if on adding of files you have this sturcture:
source
common
projects
A
B
B1
B2
C
On pulling you should have the same.
--> Chris (user)  at 22 Jun 05 06:00 writes

I am having some issues getting source controled projects that share common
files. Our basic path structure looks something like this:

source
common
projects
A
B
B1
B2
C


I can import all this stuff in using the plugin and then check in/out on
the machine that did the original import. However once in CVS, it's
impossible to get the new project anywhere else *if* the project uses any
common file outside it's own directory tree (ie, Anything from common for
example)

When trying to get the project, when the IDE gets to the common files, it
complains that it cannot find modules like this
"source/projects/A/source/common"

We can change this to the correct module, but the local path it has decided
on is also wrong and that is unchangable so the final retrieval, if it
worked, is scattered around in completly incorrect directories.

I've done a search and seen a few people mentioning issues with common
files, but was unable to duplicate their apparent success at fixing this.
It's seems to just be the initial "get" that is the issue. Once set up it
apparently works ok, but we have not tried using it for long
Rate this ticket:
Not useful at all
Partially useful
Useful
Very useful



You are 9533086 visitor since 20 Jan 2003.
1094 visitors today and 2 online right now.
blank left to top right blank

© Copyright by PushOk Software, 2003-2024, webmaster@pushok.com