Polarion Software

We will release an update shortly after the SVN 1.7 release

We are proud to announce the release of Subtrain 1.6.

Grab it here: http://www.polarion.com/products/svn/subtrain.php

We fully updated the admin training to cover a lot of exciting 1.5 and 1.6 stuff, like write-through proxy and file externals.

Feel free to post your remarks!

Regards,
ldornbusch

Hi there, we are proud to announce the release of [b]subtrain 1.5[/b] . We have new structure, new exercises-concept and also support for svn1.5. For example there is a batch file which generates all steps for each exercise. So you can just start with the exercise you are interested in. We shortened...

Hi Christian, ok, I understand, in this case you can use a collection of workitem inside a LiveDoc(note that LiveDoc-option is only available in Polarion Enterprise Ed.) You can create a fixed set of Workitems inside a LiveDoc and assign WorkitemIDs after project creation. You can also edit the Work...

Hi, Christian you can use the templates, if you want to copy the project-configuration. It is very straightforward to create a template: Just create your desired Project-structure into your template folder. If you create a polarion project, Polarion will copy this template structure into your new cr...

Hi clarkee,
as unofficially tip:
you can try srvany, which allows you to run any .exe -file as a service,
however, we do not support this solution

Greetings,
LD

Hi,
what problems do you want to solve? In which way do you want to have it easier?

I think svn_load_dirs.pl does a pretty good job.

Greetings,
Lutz Dornbusch

Hello dea, can we change the Subject of your first post, so it won't sound so "dangerous"? For people just reading the headlines it could be a bit disturbing to read of a virus in a release.. I would like to change subject to [false alarm]virus in subversive 1.1.7 release Anybody objects? ...

Hi, You cannot merge a branch into trunk directly in a single operation in your repository. This would commit conflicts into your repository which you surely not want. 1. You have to check out your target(where you want to merge to: for example: merge changes from branch to trunk: check out trunk) 2...

Hi etiennel, What are we doing wrong? Nothing, but the question is here: what do you expect? SVN will surely not "bend" your workingcopy to a new place without informing you. So this is how you solve this issue: 1. Developer B has to figure out where the files have moved (look into history...

[...] We are both seeing similar problems, mainly having to do with renaming and moving files and subpackages -- it is really easy to create a mess, even to the point of having to disconnect SVN, make the changes locally, and then repeatedly and selectively spoon feeding the SVN commits to clean up...

hello again, this is a common svn workflow: you cannot see the realtime status of a file on server. This is a limitation of subversion itself. Usually you should not need to know who is changing a file. Subversion will keep track of this. Otherwise, if you have often out-of-date errors and/or confli...

Hello, you can use the svn:needs-lock property. svn will checkout the files with this property write-protected, so you need to acquire a lock via svn lock before you can edit a file. Problem: some file editors will not notify you about a writeprotected file and will just overwrite the old file. Gree...

Hello Mumpitzstuff, unfortunately this is a common working cycle with cvs / svn and in this case outside of scope of subversive development. Usually more than 1 developer should not work on the same lines in a file(note that two developer can edit the same file as long as they edit not the same line...

Hi Lars, this is a limitation of svn, so it is not possible to fix this in subversive. The SVN-Team is working hard, to implement an atomic rename, which probably will fix this issue, however at the moment this is a limitation in the svn workingcopy. Maybe you can move your file and rename it on the...