OpenScript: Which files to put under Version Control?

Hi,
According to JB's description of [how to enable Subversion|https://forums.oracle.com/forums/thread.jspa?messageID=10677356] for OpenScript, I have now an active version control.
The next question is now: which files I should put under version control? Obviously, the script.java is a good decision, but there are many more, such as java, properties, but also specific folders like "recorded data" and "results" folder.
Which once I should put under version control, any recommendation?
Thanks a lot in advance!
Volker

Thanks for your replies,
it's nice to know that I was going the right way.. :)
But how do you handle these little bugs, that I mentioned in my first message? Do you check-out all files in the project before work? Or they are TeamSystem - specific?
Best wishes, Serg.

Similar Messages

Extremely slow performance on projects under version control using RoboHelp 11, PushOk, Tortoise SVN repository

We are also experiencing extremely slow performance for RoboHelp projects under version control. We are using RoboHelp 11, PushOk and a Tortoise SVN repository on a Linux server. We are using a Linux server on our IT guys advice because we found SVN version control under Windows was unstable.
When placing a Robohelp project under version control, and yes the project is on my local machine, it can take up to two hours to complete. We are using the RoboHelp sample projects to test.
We have tried to put the project under version control from Robohelp, and also tried first putting the project under version control from Tortoise SVN, and then trying to open the project from version control in Robohelp. In both cases, the project takes a ridiculous amount of time to open. The Robohelp status bar displays Querying Version Control Status for about an hour before it starts to download from the repository, which then takes more than an hour to complete. In many cases Robohelp becomes unresponsive and we have to start the whole process again.
If adding the project to source control completes successfully, and the the project is opened from version control, performing any function also takes a very long time, such as creating a topic. When I generated a printed documentation layout it took an astonishing 218 minutes and 17 seconds to complete. Interestingly, when I generated the printed documentation layout again, it took 1 min and 34 seconds. However when I closed the project, opened from version control, and tried to generate a printed documentation layout, it again took several hours to complete. The IT guys are at a loss, and say it is not a network issue and I am starting to agree that this is a RoboHelp issue.
I see there are a few other discussions here related to this kind of poor performance, none of which seem to been answered satisfactorily. For example:
Why does it take so long when adding a new topic in RH10 with PushOK SVN
Does anybody have any ideas on what we can do or what we can investigate? I know that there are options for version control, but am reluctant to pursue them until I am satisfied that our current issues cannot be resolved.
Thanks Mark

Do other applications work fine with the source control repository? The reason I'm asking is because you must first rule out that there are external factors causing this behaviour. It seems that your it guys have already looked at it, but it's better to be safe than sorry.
I have used both VSS and TFS and I haven't encountered such a performance issue. I would suggest filing it as a bug if you rule out that the problem is not related to external influences: https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform&loc=en
Kind regards,
Willam

Placing ~ under version control : ignore mask

Hi.
I am thinking of placing my home directory under version control.
I understand there are threads in Arch and URLs on placing home under version control.
But i find placing everything in ~ will be a waste of space since files such as
web browser cache or icons changes constantly.
I would like to know what does my fellow Archers ~ .ignore files contains?
Any DVCS .ignore files are welcome.

steveklabnik wrote:This seems to be a decent guide to how one guy uses SVN.
Yes, it's a useful guide, but it doesn't discuss the "which files to ignore" part.
I'm running my ~ in svn for already a while now, originally based on the ideas of the above article and some others.
And let me tell you: there are many, many applications who are not consistent, dump cachefiles etc in folders in your ~, or also store things like "last opened, last window size, last status on msn (pidgin)" into your *config* files etc. many applications seem to honor freedesktop's xdg specs on first sight, but in reality it's seldomly the way it should be.
It's very hard to handle this, I have many ignore rules and I regulary do a `svn status ~` to update my ignore rules. I also have a script that svn reverts some known files.
For me this list currently is:
~/.common/.mplayer/* \
~/.common/xdg/.config/vlc/* \
~/.common/.purple-private/logs/msn/*/.system/ \
~/.common/xdg/.config/banshee-1 \
~/.common/xdg/.config/totem \
~/.gconf/apps/banshee-1 \
~/.gconf/apps/brasero \
~/.gconf/apps/compiz/general/allscreens/options/%gconf.xml \
~/.gconf/apps/evolution \
~/.gconf/apps/file-roller \
~/.gconf/apps/gedit-2 \
~/.gconf/apps/miro \
~/.gconf/apps/panel/applets/applet_0/prefs/%gconf.xml \
~/.gconf/apps/panel/applets/clock_screen0/prefs/%gconf.xml \
~/.gconf/apps/nautilus/preferences/%gconf.xml \
~/.gconf/apps/rhythmbox \
~/.gconf/apps/totem \
~/.gconf/apps/update-manager/%gconf.xml \
~/.gconf/desktop/gnome/font_rendering/%gconf.xml \
~/.gconf/desktop/gnome/peripherals/keyboard/ \
~/.gnome2/evince/ev-metadata.xml \
~/.gnome2/gedit-2 \
~/.gnome2/rhythmbox
When I used gnome this list was MUCH longer. I am still in the process of getting rid of apps that misbehave badly (biggest offenders are gnome, gnome-do, tomboy, pidgin and for firefox and thunderbird I would even make a separate category: those directories are just filled with many (binary) files, impossible to manage. I use separate rsync "repositories" for those)
See http://dieter.plaetinck.be/Im_done_with_gnome_and_gconf
Here are the outputs of:
svn propget svn:ignore -R ~
/home/dieter - .adobe*
.aptitude
.bashdb_hist
.cache
.cheat
.dbus
.deb-gview
.civclientrc
.dia
.dmenu_cache
.eclipse
.evolution
.fontconfig
.freeciv
.gem
.gimp*
.gcjwebplugin
.gksu*
.gnupg
.gpilotd*
.gstreamer*
.gtkpod
.gvfs*
.hplip
.icons
.ies4linux
.java
.kde
.macromedia*
.mcop
.metacity
.mozilla
.mozilla-thunderbird
.nautilus
.netxrc
.openoffice.org*
.pulse
.qt
.sane
.scim
.serverauth*
.solfege
.thumbnails
.thunderbird
.update-manager-core
.update-notifier*
.VirtualBox
.w3m
.wapi*
.wine
.xine
bin
eclipse-3.3*
scripts
.esd_auth
.ICEauthority
.mcoprc
.pulse-cookie
.recently-used*
.sudo_as_admin_successful
.tomboy.log
.Xauthority
.xsession-errors
.scrobby.log
scrobby.cache
*.pid
/home/dieter/.local/share/applications - *.desktop
/home/dieter/.etwolf/jaymod - *.dat
*.pk3
*.so
*.tmp
/home/dieter/.q3a - qkey
servercache.dat
/home/dieter/.etwolf/noquarter/profiles/Dieter_be - servercache.dat
/home/dieter/workspaces/eclipse - *
/home/dieter/pictures-buffer - *
/home/dieter/.etwolf/jaymod/profiles/Dieter_be - servercache.dat
/home/dieter/.etwolf/etpro - *.pk3
*.so
*.tmp
/home/dieter/audio-buffer - *
/home/dieter/.local/share - bashrun
vlc
/home/dieter/.etwolf/etpro/profiles/Dieter_be - servercache.dat
/home/dieter/workspaces/ardour - *
/home/dieter/.gconf/apps - procman
/home/dieter/.etwolf/pb - *.dat
*.db
*.so
*.tmp
/home/dieter/.miro - *
/home/dieter/audio-selection - *
/home/dieter/bin-blob - *
/home/dieter/.exaile/saved - playlist0000.m3u
/home/dieter/video-selection - *
/home/dieter/.etwolf/pb/dll - *.so
/home/dieter/.etwolf/etmain - etkey
*.dat
*.pk3
*.so
*.tmp
You can build up a similar list like this:
svn create a-place-for-your-home-in-svn
svn checkout a-place-for-your-home-in-svn ~
then do svn status ~, and you'll see lots of stuff. then go over everything and decide if you want it in svn or not. by adding it (non-recursively) or updating your ignore rules. that's how I am still building up my list.. all because of those damn programs who don't implement xdg cleanly
Last edited by Dieter@be (2009-01-02 19:47:30)

How do you create translated versions of a project under version control?

Hi,
We have a project under version control that has been translated. How do we best create projects for the translated material so that the webhelp output matches the English version only translated? Is it possible to create a project with a name that reflects the translated language, copy the English project file to the new folder, change the name to coincide with the translated version, import all of the associated English files, and then exchange all of the English files with the translated ones?
Thanks,
Allen

Hello Allen and welcome to the community.
See if this article helps. You didn't mention which RH version you're using, but except for the features specifically called out as being in RH8, the process should work for RH7 projects.
I use Subversion for version control, and I haven't had any additional challenges from having localized projects in version control—you check the files in and out as you do the English ones. Check out the article and let us know if you have any additional questions.
Note that the article gives recommendations, but you certainly can do your localized versions as completely separate projects. If you do it that way, for each separate project, copy the English project to a new location, rename it if you want, and change the project language.
Hope this helps,
Ben
GryphonMountain.net

RoboHelp 11 .mdb files unhandled in SharePoint version control

Since RoboHelp 11, .mdb files don't seem to be recognized with SharePoint version control. Note that we have ensured the file type is allowed in SharePoint.
Lauching RoboHelp in Admin mode does not help.
Note that this was working under RoboHelp 10.

Hi, goguenr
Because RoboHelp 11 has some enhancements and a new Topic-Sharing workflow (that can be "cloud-based") there have been some modifications. So perhaps it requires a re-connection to SharePoint. Normally, the RoboHelp/Sharepoint integration is most commonly used for source control of those files related to a specific RoboHelp Project. RoboHelp will exclude any "output" files (like those in the !SSL! folder because after all they are output files and not "source" files as source control implies. However, you can modify how this works with some configuration. If you also link to files (which are managed by "Baggage" in the Project Manager); those are added to Source Control as well. (But it sounds like you were already doing that with previous versions, so sorry if I'm stating the obvious.)
I think if would be great if you could take a look at a webinar that Willam van Weelden and I did last Fall. A recording is available for viewing and is free. You can also learn more on Willam's website:
http://www.wvanweelden.eu/blog/2013/08/17/adobe-robohelp-using-sharepoint-version-control
The recording is here (you may be asked to sign in with free Adobe ID)
http://www.adobe.com/cfusion/event/index.cfm?event=set_registered&id=2099687&loc=en_us
Willam is more versed in this than I, so perhaps he will chime in with more.
Thanks
John Daigle
Adobe Certified RoboHelp and Captivate Instructor
Evergreen, Colorado
www.showmethedemo.com

How to clone a project that is under version control?

[RH10]
Hello. I have a large project that is under TFS source control. I would like some advice on how to safely clone a copy of this project to a separate location (not under source control).
In the past I ran into problems when copying a project under source control. I think I need to somehow unlink the project from TFS before copying it, but I am hesitant to do this without some expert guidance. Can anyone walk me through the steps for doing this safely? (By safely, I mean without altering in any way the state of the production files under source control.)
Thanks,
Mike

An olden golden from Rick: http://www.robowizard.com/RoboWizard/MonthlyScry/102004.htm
Just create a copy somewhere and follow the steps outlined by Rick. This article applies to all versions of RoboHelp, no matter the source control system used.
Greet,
Willam

Which file will identify Leopard version number?

Is there a file in the System folder which gives away the system version number?
I need to find out which version of Leopard (10.5.1 or 10.5.2) is installed on a mounted (but not booted) volume so can't just go to About This Mac. I can access all the System files but I can't find one which gives a definitive clue - unless perhaps it's the Finder (which has the futuristic version number of 10.5.3). TIA.
Simon

pr100 wrote:
Is there a file in the System folder which gives away the system version number?
I need to find out which version of Leopard (10.5.1 or 10.5.2) is installed on a mounted (but not booted) volume so can't just go to About This Mac. I can access all the System files but I can't find one which gives a definitive clue - unless perhaps it's the Finder (which has the futuristic version number of 10.5.3). TIA.
Simon
If you open a Terminal and look in the root directory you will see a file, "mach_kernel" which I believe represents the OS version by date
If you cd to the root directory and enter the Terminal command:
ls -lT mach_kernel
(that's the letter l)
You should get the date of the kernel, which, on my 10.5.2 machine is dated Feb 5 2008
10.5.2 was released on Feb 11, so the final date may well be Feb 5.

Version control for FH files

For the last 2 years I've been using a subversion system that
works very well with FH files. It does basicly the same as
VersionCue but works with a lot of file formats (not Flash 8 btw)
My setup is like this:
- File server at my home studio (just a win machine with RAID
5 disks and mapped network drives shared on my home network)
running Win XP Pro (backup done every 24h)
- a workstation running TortoiseSVN on Win XP Pro (it becomes
a shell extension in Explorer)
my simple system:
- I create a version repository in my project folder on the
server
- I check out a working copy of the file(s) I want to work
with to a local folder or a dedicated disk partition as I do
Whenever I save my changes I commit these changes to the
repository with a text comment
Icon overlays tells me the status for each file and folder
under version control
Whenever I get a file corruption (it happens with FH files) I
just check out a fresh working copy from that last commited
version. You can of course revert to any previous version at any
time or create branches out from one main design.
The best thing is that I'm able to review my change log
without opening a lot of files and revert to previous designs
without keeping a lot of different files, and of course being able
to resolve problems with corrupted FH files with minimal loss.
http://tortoisesvn.tigris.org/

I started version control on 01/14/2014.
As you can see below I modified several topics. When I opened the RSC database and did a history on any modified Topic from 01/14/2014 to a date in the future, it always said there was no difference. In the past it always showed there was a difference and what the difference was.
I have started and stop version control several times hoping that would resolve the problem. Right now I am not using version Control.
I will start version control again.
Richard Wright
Functional Area Expert II
Systems Made Simple (SMS)
1615 Woodward Street
Austin, TX 78772
Service Delivery and Engineering (SDE)
Enterprise Operations (EO)
Enterprise Applications Support (EAS)
(512) 326-6610
[email protected] <mailto:[email protected]>
One of the Inc. 500 Fastest Growing Privately Held Companies in the U.S.

Putting ~ into a version control system

Hey folks!
I'm curious as to how one could put ones home directory into version control, to quote Codemac;
codemac wrote:I keep my ~ in mercurial, so all files are checked in and versioned. [...] I highly suggest you put your $HOME into version control. It's real fun to see what your home directory looked like 3 years ago
I once used Subversion under Mac OS X to download a random project just for kicks, but had no idea what it was all about really. I understand that a version control system assists (manually or automatically?) in labeling files/data/"units" with version numbers, and storing the data as well? I've also seen that a number of users here use Git, another version control system, to label and share their various configuration files. Where is the data stored? On a server belonging to someone else or on ones own computer?
I found a Wikipedia article on the topic, although Subversion isn't named there, so I may be wrong on that one.
Is there a CVS that is small in size and amount of features and easy to get the grasp of?
Thanks in advance.

I'm having my ~ under version control now for a while (I am using git - the decision to do so was mainly motivated by my desire to learn git). However, I don't track every file in my ~. Just the configuration files (.bashrc, .bash_logout, .zshrc, .awesomerc, vim ... etc. etc.) and some docs (though I keep them in a different private repository). I'd recommend that if you plan to put your ~ under a VCS that you should think about what you plan to track and what not first. It certainly means some additional work, because you have to remember to commit changes back into your repository every time you change a tracked file. Of course you can perform a commit on every logout, but if you want to revert/restore a single file, it's better to track changes in files individually. As I see it, the main idea of keeping your ~ in a VCS system is to have a backup from where you can restore a single file to every point in time you want, or to revert uncommited changes which broke sth. in an instant. So, IMHO it doesn't make that much sense to have the repository on your laptop only, but also to have a remote repository (in case your HD dies). For me, it's also a nice way to keep my home directory in sync over multiple machines.
As for the decision on which particular VCS to use. I first tried to do that a year ago using svn, and it didn't work out that well - for some reason I don't like svn - but that doesn't mean that svn is bad - it could be right for you . Darcs is an easy to learn VCS but it lacks some features like branches and the like (which you may not need in this szenario anyway). I don't know much about Bazaar or Mercurial, because I've never used them, however from what I've read, these two are very popular choices nowadays (maybe someone with some experience with those can shed some more light ). Also, you have to chose the VCS according to what you like to track, because they differ in performance and the extra storage they need to keep track of the changes (I read a good article which compared all named VCSs regarding repository/metadata size in differrent szenarios, small files only, big files only etc. etc. - but unfortunately I can't find it atm).

Can't rename file under Subversion control.

CS5 - Unless I'm missing something you can't rename a file (using dreamweaver to do so) and have it maintain it's connection to subversion. For example, if I rename a file using Dreamweaver, edit it, then go to "Commit" it, I get an error "File is not under Subversion Control". What is the correct way to rename a file in CS5 under subversion control?
This is a serious deficit.

Saving the file under a different name creates all sorts of problems. Especially since all the history of the changes are lost. DW provides a "rename" command but it doesn't update the files svn metadata. If you use the rename command it doesn't warn you that you will loose the connection to the repository.
This must be a bug because an equivelent version of Tortise SVN DOES allow you to rename a file and preserve all the history. I just found this out and am using Tortise SVN to do the renaming. It's the same SVN version as DW so it updates the metadat just fine and it preserves the history of the previously named file.
This is a bug in DW or a serious omission.

Regarding version control

Hi,
Could u please help me out in giving some ideas of version control in sap?
First let me give some example as follows:
First if i develop something in the developement server then later when i transfer to the QA server and later to production server then is there any change in version.
Please give me a details of this issue????
Thanks,
Batista....

hi priya,
Version Control
Version control is a mechanism that helps maintaining the revision history of a development resource and tracking the changes done to it. It defines a set of constraints on how a development resource can be changed. A development resource that complies with the constraints defined by the version control is called a versioned resource. When a versioned resource is modified or deleted, a new version is created for the resource. A unique sequence number is associated with each version of the resource created in a particular workspace. This sequence number identifies the order in which the versions were created in that workspace. The DTR graphically represents the relationship between the different versions of a versioned resource in the form of a version graph.
For the representation of version graphs, this document follows the conventions shown in this figure.
The figure shows the meaning of the symbols in the version graph.
The following changes are tracked by the version control mechanism of the DTR:
·        Addition of the resource to the repository
·        Modification of the resource in the repository
·        Deletion of the resource from the repository
In all the above cases, a new version of the resource is created.
Production Delivery
Packaging
To deliver your product, you have first to package it. There are different packages you can use for shipping your product to your customers:
●      Software Component Archives (SCAs) this is the standard way to deliver software for the SAP NetWeaver platform.
●      Software Deployment Archives (SDAs) for top-level applications you can deliver only the executable part of the software. You can directly deploy the SDA file.
●      Public Part Archives (PPAs) in Development Component Interface Archives (DCIAs) for reusable components (Java EE server libraries, Web Dynpro components, Visual Composer components and so on). You can deliver only the metadata of the components. DCIA can be included in SCA file too.
How to do that?
Using the command line tool provided with the SAP NetWeaver Composition Environment you can:
●      package a collection of components into an SCA including only the deployable archives. This is required if you do not want others to reuse the delivered components.
●      package a collection of components into an SCA including the deployable archives and the corresponding interface archives. This allows customers to develop against these components. Those customers can directly import the SCA into their own SAP NetWeaver Development Infrastructure (NWDI) or into an SAP NetWeaver Developer Studio local installation.
●      package the public parts of a component together with the required metadata into a DCIA (and further into an SCA).
●      include source code into an SCA.
●      unpack a deliverable archive and drop the result into an existing version control system for example, or directly import them into an existing Design Time Repository (DTR).
Delivery of Source Code for Further Customization
In addition, you can deliver source code to your customers to allow further customizing or add-on development. The deliverable archive may contain sources for:
●      individual development components (DCs).
●      a collection of development components, for example a whole software component (SC).
Example
A customer can add a new source compartment to an existing configuration, and then locate that compartment in the file system where it is accessible by the version control system in charge. Then he or she extracts the sources with the command line tool to the compartments root directory and refreshes the configuration in the SAP NetWeaver Developer Studio. The compartment tree is populated with components from the archive. Afterwards, the customer may put those components under version control. Deliverables that contain only individual components may be treated accordingly.
This mechanism may also be used for other purposes, for example for setting up a simple backup and restore mechanism for components in Developer Studio, or sharing DC sources without having a central version control system: a developer may pack a compartment and store the resulting SCA on a central share or backup system. Another developer may take that SCA and import it.
Limitations
Note the following limitations connected with this kind of source code delivery:
●      There is no support for handling conflicts when different actors in a delivery chain develop independently in the same source code. You cannot prevent the customer from modifying delivered sources. When you ship a new version of the sources, there is no special support for updating and no support for merging the update with modifications done by the customer. You and the customer have to agree on a process how those conflicts are handled. For example, the customer can decide not to import the update you deliver directly into the active development line, but to unpack the delivered sources to some unconnected sandbox system and perform the required merges manually.
●      When you deliver source code to customers, it is important that you also deliver the required libraries and generators that are needed to build these sources. For example, it may be necessary to ship some archive compartments that contain used components.
●      There is no support for delivering deletions in a new version. If a source file was deleted, the customer has to manually ensure that the file is also deleted in the Developer Studio or source code management system.
●      If a customer prefers to work with the SAP NetWeaver Development Infrastructure (NWDI), this customer cannot directly import the source delivery package into the NWDI landscape. Between NWDI landscapes at different places, sources usually are exchanged through a more sophisticated export format that contains not only the pure source code, but also the versioning meta information of the exporting DTRs. This ensures that the importing repository can detect conflicts that arise due to modifications. If this versioning information is not available, the only way to import source deliveries is to unpack them to a file system and manually put them under version control with the Design Time Repository perspective of the Developer Studio. In case of an update, the customer would have to check out all affected files, merge them with the new versions from the source delivery, and finally check them in as a new version.
More information: Composition Environment Command Line Tool
see this url
http://www8.sap.com/businessmaps/0134713B1D6046C59DE21DD54E908318.htm
thanks
karthik
reward me if usefull

Configuration version control software

I know some people like to put their /etc under version control with CVS or hg or something, to make it easier to recover if they misconfigure something. I think this is kind of overkill, though. For one, you don't really need "distributed" or "centralized" version control, you just need to control the version. And for another, version-controlling the entire /etc doesn't really make sense considering that you're usually only working with a few files at a time, which you would generally control separately. So, I came up with the idea for a VCS specific to managing your system configuration. I'm going with the name Tessen for now since it sounds cool.
The two basic concepts involved here are applications and snapshots. An "application" refers to a particular set of config files managed by Tessen. For example, the pacman application would own pacman.conf, makepkg.conf, and pacman.d (a directory). Ownership in this context means that it will automatically track changes to the contents of the files and folders. (Each application has an active snapshot, which is basically "the last one you saved or reverted to.")
A "snapshot" is how an application's config files looked at any given time. A snapshot has a number (since it's not distributed, a simple autoincrementing integer will work), a timestamp (for obvious reasons), an action (to indicate exactly what caused this snapshot to be taken - for the user manually saving it would be "save", if it was installed by a package manager, "install", etc.), a note (if you feel like it - a good sysadmin would always have one), and the files' contents. (You can also add additional notes to snapshots after the fact, but this won't affect the note that was saved with the snapshot in the first place.)
Anyway, the workflow would run something like this:
"tessen newapp pacman pacman.conf makepkg.conf pacman.d". Tessen creates a new application named "pacman" that owns pacman.conf, makepkg.conf, and the directory pacman.d. (Tessen would automatically save a snapshot at this point consisting of the current contents of said files. That would be snapshot #1.)
Make changes to the configuration, like using aria2c as the transfer command.
"tessen save pacman -n 'set XferCmd to aria2c'". Tessen will take a snapshot of all the files owned by pacman and save that, making it #2.
DOOM! You forgot that you don't have aria2 actually installed, and now that XferCmd is aria2c you can't install it! (This is just a contrived example.)
"tessen revert pacman". Since you're at #2 but haven't made any changes, it will switch you back to #1. (If you had made changes, it would reset to #2 instead.) All necessary files will be reverted.
Now you can "pacman -S aria2" and make sure it works this time.
You could edit it manually to set it back to aria2 (which if you saved it would make it #3) but it's easier just to "tessen revert pacman 2". revert jumps back one step by default, but you can tell it to revert to anything. Then the next change you make would be #3.
One major thing about the design I haven't quite decided would be how ownership is stored, and what to do if you change the ownership and try to revert to an older snapshot. That would be tricky to figure out. Still, what do you think about this approach?

ewaller wrote:I think I'm missing something :-/
I know the OP dismissed git and hg at the outset -- but why? It seems to me they are ideal for just this sort of thing. On this machine, I do have an Hg archive living under /etc. Being Hg, it is simple to push that off to other systems and keep them synced (or not).
Perhaps tessen could wrap git or Hg?
The reasons I had for not using a traditional DVCS (as much as I love them) include:
A VCS in all of /etc would manage your configuration as a whole. Tessen lets you manage each application separately without awkwardness.
Also, there is stuff in /etc that isn't really configuration (I'm looking at you, /etc/bash_completion!). You could get around this by simply not "hg add"ing those files, but it does make it trickier. (Though in an ideal world, each app would store its configuration in a separate directory and things like the completion scripts would be in /share or /usr/share.)
Finally, if you're using a DVCS so you can sync configuration, this would actually be better. For example, if you're trying to share the Apache and CouchDB configurations between your boxen, you have no way to keep out any other files you might have added (like, say, fstab).
Really, it's mostly just that the concepts behind Tessen map more clearly to the problem than those in hg or git. At least in my mind. Although using a DVCS as the storage backend would be interesting...
fukawi2 wrote:What language are you planning on writing this in?
Probably Python. (My original concept would use SQLite as the database.)

Version Control for OSB Proxy/Business Services ?

Dear all
I've used the browser-based osb console to expose a legacy web-service as follows :
1. Create a Session
2. Create a BusinessService based on the legacy web-service WSDL
3. Create a ProxyService based on the BusinessService WSDL
4. Activate the Session
I now have two further questions :
1. How do we version control the OSB "code" ? (we use Subversion for other code)
2. How do we implement it in other environments (TEST, PROD, etc.)
Thanks,
Peter.

>
Are there other reasons why you say it's not the most ideal way of development ?
>
Versioning binary files is always a pain. You can't compare them, you can't merge them ... Another point, if you put your jar archive with OSB artifacts under version control, you will most probably face issue related to end of line styles (mac, unix, windows).
However, the most important point is usability. I want to version .proxy and .biz services to see right in IDE that I changed something and I should check that in for the others. I don't want to risk that I forget something. And I also want to see what other users committed, what sources they work on ... You loose all of that by versioning jar file. I would never go this way.

Hello, I want to use version controlling software with Labwindows.

Hello All.
I want to use version controlling tool with Labwindows/CVI. Actually version controlling tools work for text files and by using the tool i can do version controlling of my .c and .h files in Labwindows/CVI project. But is there a way to do version controlling of .uir files also. Version control tool can detect the changes made in .uir file but is there any tool that can be used to compare and merge .uir files too just like text files operation for version controlling.
Regards

Hello Moshi,
Personally I never understood how the integrated version control system of
CVI works, but SVN (and TortoiseSVN) works fine with CVI projects.
UIR files are treated as binary, as they should be, and that's about all.
You could put the .tui file under version control instead, but I don't think
it's worth the bother.
Guillaume Dargaud
http://www.gdargaud.net/

Version controlling tool

Brian,
We are going to use Oracle 9i database & 9i AS & JDeveloper 10g as tool for our web development. We have been using SourceSafe as version controlling tool successfully, but could not decide what we should adopt for the integration.
I do know that Oracle is not planning further development for Oracle SCM and as such recommends all new development with JDeveloper makes use of open source tools such as CVS. JDeveloper offers different choices for your configuration and team development environment. You can continue to use Oracle SCM with the JDeveloper extension or you can use open source tools such as CVS.
My question is
You said that you can confirm that SourceSafe will definitely be supported in the next release. (Apr 19, 2004 9:31 AM Subversion Source Control). Has it been released?
If not, what is your advise on tool to use for our development team?
Thanks in advance,
YingShi

Hello Moshi,
Personally I never understood how the integrated version control system of
CVI works, but SVN (and TortoiseSVN) works fine with CVI projects.
UIR files are treated as binary, as they should be, and that's about all.
You could put the .tui file under version control instead, but I don't think
it's worth the bother.
Guillaume Dargaud
http://www.gdargaud.net/

OpenScript: Which files to put under Version Control?

Similar Messages

Maybe you are looking for