Simple Item Version Control Default Option

With simple item versioning, the item version control options that show up are
*Add Item As New Version, but not as Current Version
*Add Item As New and Current Version
*Overwrite Current Version
Currently the option selected by default is Overwrite Current Version. Is there an easy way to change the default option to be Add Item As New and Current Version?
Thanks in advance.

No - there does not seem to be an easy option to do this.

Similar Messages

WebDAV item versions access in 9.0.2

For our portal usage, webDAV is a good way to provide a simple way to update documents stored in the portal.
However, item versioning management through webDAV should be improved/fixed.
A. In case of "simple item versioning", the default behaviour cannot be configured. It is always: "replace current version"
B. The various versions are all accessible through webDAV showing the different filenames associated. So, if having an item with:
ver.1 - TEST_1.TXT
ver.2 - TEST_2.TXT
current ver.3 - TEST.TXT
it will be possible to access any of them. The action of opening one of them, modifying and saving it (same name, same place), will produce a "replace current version" action, even if the folder was marked with "AUDIT versioning"! In this case the action should not be permitted, or it should produce the generation of a new item version.
C. Although still poorely implemented in client applications, it is desirable the implementation of the versioning extension of the webDAV protocol, as described in RFC-3253. We have our own client applications (home made) that could benefit from that feature.
Thanks.

Item versioning was not implemented for this release. We are aware that this functionality is needed by many and are planning on implementing it in a subsequent release.
Thanks for your suggestion!

Removing the "sort by: most recent" default option from my purchased items.

Is there a way to remove the "sort by: most recent" default option from my purchased items? It annoys me to see items that are not ordered alphabetically or by release date so I do not want there to be a record of this.

See:
* https://support.mozilla.com/en-US/kb/Resetting%20preferences

Version Control Options

I created a new project in RH X5 and added it to version
control (SourceSafe); however, even though I set my working folder
to the new project, SourceSafe retrieves the files from a different
project folder, which is evidently set as my default. Any idea how
to fix this?
Shannon

Flex code can be used with any version control system I am aware of.
I was unaware that Flex Builder had native support for any version control.
However, Eclipse, which Flex Builder is based on, has plug-ins for a lot of things, including version control systems.
Take a look at the team development category here: http://www.eclipseplugincentral.com/

New to JDeveloper/ADF, need to create a UI Mockup for a Version Control app

Hi,
I have experience with Java/J2EE, however I'm new to both JDeveloper and ADF and was hoping someone could point me in the right direction with what I'm trying to accomplish/start. We are working on a new application for a client and to kick start things I need to come up with a User Interface Mockup of a Version Control system we're going to create. It should be nothing fancy, and not very functional (for the time being) but should use some dummy data (preferably from a text file - just for demo purposes), be a one-page layout, and use Oracle ADF components (folder tree, datagrid, data view, xml view to be specific). Of course, it is requested that this all be done using JDeveloper/Oracle ADF. I was able to install both of these (it seems ADF is bundled with JDev), however that's about as far as I got. What steps do I need to take in order to come up with something simple like this? When I loaded up JDeveloper there are alot of options when creating a new project and I'm not sure what to choose. ANY help would be appreciated.

Thanks! This is exactly what I was looking for.
However, I'm having some trouble figuring out how to set up my Data Controls for the dummy data. I'd basically like to set up the entire page as follows:
A column on the left that displays a tree as follows:
Folder 1
     ...File 1
     ...File 2
     ...File 3
Folder 2
     ...File 1
     ...File 2
Folder 3
     ...File 1
     ...File 3
     ...File 4
     ...File 5
..etc
The right side of the screen will have 3 "columns" or borders that will take up the entire screen, from top to bottom:
List of Versions (large column)
Version Data (smallest column)
Version Text (large column)
List of Versions:
When the user selects a "File" from the tree, a datagrid will appear that displays all versions of the selected file with columns like "File Name", "Version", "Date", and a checkbox to select a row.
Version Data:
When the user selects a row using the checkbox, some relevant version info will display here. This info will come from the database when the final version of the app is written using various fields from the "Files" tables
Version Text:
When the user selects a row using the checkbox, some relevant version CODE (possible to display code neatly?) will display here. This info will come from the database when the final version of the app is written using a field from the Files table that has not been seen yet
How would I go about setting something like this up? Using the sample you provided earlier, the example just has main categories on the left. I'm confused how to set up a fell fledged tree and then to incorporate the functionality I described above.
ANY help would be appreciated.

Opening Project First Time from Version Control. RoboSource Node

Four writers have upgraded successfully. My fifth is having issues...
She has Serena Dimensions SCC installed as well (another source control product - used by Applications, not the authors or Infra.
Problem: When she is establishing the root path (and the Browse RoboSource Node window opens, but it does not populate, even after 20 minutes. Reboot did not work, neither did manually removing Serena Dimensions SCC. I have verified that she has a connection to the database (via RSC Explorer) and can see the project (as well as the RH7 version of the project). We have
These are the instructions... (screenshots not included). She's hanging up on
1.1    Using a New Project for the First Time
IMPORTANT NOTE:
The author must have local administrator rights on the machine. If the user has a privileged account, they must set up full local control of their work folder (specified in 1.1.2.8).
1.1.1    Install RoboHelp and RoboSource Control
1.    Download appropriate software packages, including all patches, from Adobe.
2.    Launch RoboHelp Installer. Select the following options for installation:
o   RoboHelp for HTML
o   RoboSource Control (Client)
o   CS4 Script Extender
INSTALLATION NOTES
Installation of each component is separate and may take up to 30 minutes. You do not have to install RoboHelp for Word.
Only select the Client Install for RoboSource Control.
3.    Install all patches in the order specified by the vendor. Check with the technical communicator on which version is currently in use for patching.
1.1.2    Open the Project
1.    Launch RoboSource Control.
2.    Establish a database connection per section 3.3.1.
3.    Close RoboSource Control.
4.    Launch RoboHelp 8 for HTML.
5.    Click Open under Recent Projects under the main frame (do not use title bars).
6.    Click the Open Project from version control button (shown below).
7.    Make sure that RoboSource Control 3.1 is highlighted as the Version Control Provider and the checkbox for “Make this my default selection” is checked. Click OK.
8.    Configure the Source Control system as follows:
Connection: PROD
Root Path: Click the … button and navigate to the (project name) root in the database and click OK. This may take several minutes.
Connection Mode: Online
Get to Local Path: Click the … button and navigate to your Data folder. Select Make New Folder under Data and give the folder a unique name to help you identify the files as for the Support KB in RoboHelp.
9.    Click OK when you have configured source control. A copy of the database is now being downloaded to the path you specified. This may take up to 20 minutes.
You can verify that installation is proceeding either by watching your local path fill with files or keeping an eye on the CPU usage of the RSO3MiddleTierService and RoboHelpHTML files under Task Manager.
10. Once transfer is complete, highlight Tier1KB.xpj and click Open. It may take several minutes to open the project the first time. It is typical for the snippet file to check out the first time you open the project and the first time each day that you save all project files.
11. Once the project is open, set Version Control properties:
a.         Select Tools > Options.
b.         On the Version Control tab, select all options. This will prompt the user on each version control action they take.
12. Test a check out/check in to validate correct installation and source control operation.

It's the settings in miscproperties in the XPJ and it works in TFS just fine. I'ts as follows:
<miscproperties>
<matchedpair>
<name>vc::provider</name>
<value>Team Foundation Server MSSCCI Provider</value>
</matchedpair>
<matchedpair>
<name>vc::agent</name>
<value>MSSCC</value>
</matchedpair>
<matchedpair>
<name>vc::database</name>
<value>http://ap-gda113-tfs-a:8080/tfs/centric|NB-WWEELDEN|ITS\Wweelden</value> <- Add the TFS URL, your workspace name and your domain name.
</matchedpair>
<matchedpair>
<name>vc::cookie</name>
<value>$/BV - MVV/Main/Tools/Documentatie/mvv-beheerders</value> <- The location of the project in TFS.
</matchedpair>
</miscproperties>

OWB Change Management/Version Control Best Practice

Hi
I am about to start developing a data warehouse using OWB 10g R2, and I've been doing quite a lot of research into the various deployment/change management/version control techniques that can be used, but am still unsure which is the best to use.
We will have 2-3 developers working on the project, and will be deploying from Development, to Test, to Production (each will have a separate repository). We want to be able to easily identify changes made between 1 release and the next to have a greater degree of control and awareness of what goes into each release. We also wish to use a source control system to track changes (we'll probably use SVN, but I don't think that the actual SCS tool makes a big difference to our decision at this point).
The options available (that I'm aware of), are:
1. Full MDL export/import.
2. Snapshot MDL export/import.
3. Manual coding of everything using OMB Plus.
I am loath to use the full MDL export/import functionality since it will be difficult, if not impossible, to identify easily the changes made between 1 release and the next.
The snapshot MDL export/import functionality is a little better at comparing releases, but it's still difficult to see exactly what has changed between 1 version and the next - particularly when a change to a transformation has been made. It also doesn't cope that well with tracking individually made changes to different components of the model.
The manual coding using OMB Plus seems like the best option at the moment, though I keep thinking "What's the point of using a GUI tool, if I'm just going to code everything in scripts anyway?".
I know that you can create OMB Plus code generation scripts to create your 'creation' scripts, but the code generation of the Alteration scripts seems that it would be more complicated than just writing the Alteration scripts manually.
Any thoughts anyone out there has would be much appreciated.
Thanks
Liffey

Well, you can also do per-object MDL exports and then manage those in your version control system. With a proper directory structure it would be fairly simple to code an OMB+ Script that scans a release directory tree and imports the objects one by one. I have done this before, although if you are using OWB as the primary metadata location for database objects then you have to come up with some way to manage object dependency order issues.
The nice thing about this sort of system is that a patch can be easily shipped with only those objects that need to be updated.
And if you force developers to put object-level MDL into your version control system then your system should also have pretty reporting on what objects were changed for a release and why.
At my current job we do full exports of the project MDL and have a deployment script that drops the pre-existing deployed version of the project before importing and deploying the new version, which also works quite well - although as you note the tracking of what has changed in a release then needs to be carefully managed elsewhere. But we don't deploy any of our physical database objects through OWB. Those are deployed from Designer, and our patch script applies all physical changes first before we replace the mappings from the OWB project. We don't even bother synching the project metadata for tables / views / etc. at deployment. If the OWB project's metadata for database objects is not in sync with Designer, then we wind up with deployment errors. But on the whole it works pretty well.

Version Control with JDeveloper

Does any one know what version control packages can be used with JDeveloper? If you do, would you please let me know where I can get info on them.
Thank you

Alex,
There are two parts to this answer.
You can hook up any version control system
to JDeveloper using various JDeveloper
extension mechanisms including adding items
to the tools menu or complete wizards.
On OTN, you can find an CustomAddins which provides a way to integrate to any version control system by editing some batch files to point to their "put" and "get" type tools. This is meant as a simple starting point.
Starting with JDeveloper 3.2, you will be able to take advantage of the intergrated source control feature that integrates Oracle Repository's source control features into JDeveloper.
I hope this helps,
-John

Version Control with JDeveloper application using ClearCase

My team is evaluating J Developer to see if
it matchs our requirement. We want
to know how we will be able to use Clearcase
as version control tool with our Java or JSP application developed using JDeveloper.
We understand that J Developer will help us
to create a zip file for deployment. Do we need to check in/out that zip file, zip/unzip the zip file, look for the file
that we want to change, and then make change to it?
If so how Clear Case knows which files in that zip file has been changed and what changes have been made?
Currently, we use Clearcase to check in/out
every single file, one at a time. We don't know how it will work with a zip file.
Sincerely,
Khanh

Alex,
There are two parts to this answer.
You can hook up any version control system
to JDeveloper using various JDeveloper
extension mechanisms including adding items
to the tools menu or complete wizards.
On OTN, you can find an CustomAddins which provides a way to integrate to any version control system by editing some batch files to point to their "put" and "get" type tools. This is meant as a simple starting point.
Starting with JDeveloper 3.2, you will be able to take advantage of the intergrated source control feature that integrates Oracle Repository's source control features into JDeveloper.
I hope this helps,
-John

Version control (lvcompare and lvmerge) for projects, classes and libs?

Hi everyone
Version control for classes, projects and libs (not just a plain .vi) - can it be done with lvcompare and lvmerge?
I've tried a simple "LVCompare.exe project1.lvproj project2.lvproj" and it only returns an error (lvcompare.exe vi1.vi vi2.vi works). So this is maybe a dead end.
How do you guys version control more complex projects? E.g. projects which use classes, libs, labview projects (.lvproj)?
Best regards
Jonascj

Thank you for your reply. You are right, .lvclass, .lvproj and .lvlib are all just xml files - I've just figured that out my self when I accidentally called GIT's default diff on a lvclass
I've also just spoken to National Instruments. The person I spoke to (from the one of the danish offices) told me that no tools exist at this time (2013-04-08) which will compare those LabView file types, but that there was an internal (National Instruments themselves) feature request for such tools.
He also told me another interesting thing which I did not know. The lvcompare.exe (located in National Instruments/Shared/LabVIEW Compare/ on Windows) is actually the not developed by National Instruments, but is either a "fork" of LVDiff (http://meta-diff.sourceforge.net/) or LVDiff renamed. So one could simply obtain the source code from http://meta-diff.sourceforge.net/ (at the bottom of the page "Win32 binary w/source") and add a few property nodes to do comparision of lvclass attributes etc.

Why do people use SharePoint for Version Control?

People have a few options for placing their FrameMaker documentation in version control. One option is to use the SharePoint CMS integration. What I don't understand is why someone would choose to use SharePoint for this. I have seen several points with complaints like "I have everything set up correctly but sharepoint still isn't working correctly for X reason...". Now there are business reasons why you may have to use SharePoint. For example, the organization you work for is all based on Sharepoint and they demand the use of SharePoint as a business requirement. However, if you have a choice, why not use subversion? I have been using it for years with my framemaker documentation. There are no configuration steps. Someone sets up the SVN repository and then you add the FrameMaker files. That's it; you are done. After that, SVN just works. However, the bottom line is that Sharepoint CMS sounds like a nightmare. I can personally attest there are almost no problems with using a SVN repository. From a technical standpoint, I have no idea what SharePoint could possibly provide that would make it worth the hassle it puts people through to do simple check ins and check outs. Joe

In my case, "business reasons" more or less nails it. Our company is implementing SharePoint and they're hoping I can use it for DITA. They'll entertain other options only if there are good reasons why we can't make SharePoint work for this. I've already started exploring the SharePoint API. Meanwhile, we have the SharePoint Connector working and we can check files in and out -- it's not that difficult.
I've heard about Subversion, but I understand that it's mainly a source-control application. I have no shortage of those to choose from; our company already uses MKS and TFS. (In fact I'm using MKS to store one of my DITA projects.) SharePoint has an edge over them because it allows me to associate custom metadata with a library (say "topic type" or "audience"), complete with a list of fixed values like "concept" and "task" for our authors to choose from. I'm not sure if Subversion offers similar functionality.
Where all of them fall down is in the area Nakshatra mentions -- dependency management. If I want to rename a file, or replace a Windows7 screenshot with a Windows8 screenshot that has a different file name, or I want to know everywhere a conref is used, or want an alert when someone changes the conref, I need an underlying database to make the file management system "DITA-aware."
I was all set to create such a database for our SharePoint implementation, along with a user interface -- very gradually, in small steps over a long time. FM's "FMDependency" field presents an unexpected complication for this plan, and I'm still absorbing that.
If Subversion is "DITA-aware" or has promising open-source plugins to make it so, I'm interested. Otherwise I still have to develop a database and UI, and in my case, I might as well try to do it with SharePoint.

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.)

How do I fix project after "Remove From Version Control" corrupted it?

I am using RoboHelp 9.0.1 and installed both Tortoise SVN 1.6.9 and latest PushOK SVNSCC then added my large RoboHelp project to SVN. I was able to check in and out files from SVN but had several issues with it:
1) Super super slow. Working with folders or any renames would take 10 seconds per file and up to 1 hour if needed to refresh the root folder.
2) I could not perform some actions at all, such as delete, rename, or move folders. I kept getting COM errors.
I therefore decided that working with SVN and RoboHelp is not practical, at least not on my VPN so I decided to disconnect the project from source control and just work locally. The only option that I saw that sounded like it would do that was the "Remove from Version Control". This started a process that lasted for several hours. At the end of it, I now have several significant issues:
1) The order of the files and folders in my Project Manager is completely wrong now. I have almost 1000 topics and reordering all of them is not possible.
2) The Table of Contents, Glossary, and Index files appear empty. They had content before.
2) A couple of the Single Source Layouts I had created are completely missing.
3) Many, but not all, of the folders have tons of files with the extension ending in "_temp_removed_by_svn"
4) Many, but not all, of the files are actually gone from SVN so I can't recover a clean image. There was no warning that this command would actually delete the files from SVN (I thought it would just remove the version control connection).
5) Who know what other issue exist that I haven't seen.
Any idea how I can fix this?
Thanks in advance,
Dan

Are the "_temp_removed_by_svn" files in your local folder or SVN? Let us know how you get on with the new project. It sounds like something is wrong with SVN. Can you use the SVN Log command to see whether there is a different version you can restore. This might also give you an indication of what might have caused the problem. You could try deleting your CPD file. It gets rebuilt it is isn't there anyway. This file can become bloated and it is good practice to delete it when it gets close to 2mb in size. Your project is fairly large and has a lot of folders and may affect performance. Have you considered splitting them and merging the output? I know you probably don't want to consider this right now, but I think it may be a better long term solution.
The RoboColum(n)
@robocolumn
Colum McAndrew

Can I have a library of PDF docs with version control? Can it cope with version nos. embedded in the file name?

I manage a set of documents which are edited in Word but "published" as PDFs (using Word 2010's save to PDF capability).
I want to create a library for them on SharePoint (my company has SharePoint Online via its Office 365 subscription).
I'm pretty much a SharePoint novice but even I can see it's easy to upload the documents to a simple library. The things that are giving me a headache are:
Can I tell SharePoint what the version number of the uploaded PDF document is? The version number as understood by the library needs to match the version number written into the document (where it is called a revision number and increments in whole numbers
starting from zero).
How do I handle replacing the uploaded PDF documents with new versions? If they were Word documents I could edit them by opening them from the SharePoint library, checking them out if necessary, and SharePoint would handle version control.
But since the PDFs are generated from editable masters (Word documents) which are NOT on SharePoint I would need to edit the local Word document on my PC then generate a PDF version then upload it to replace the existing PDF document in the
library. Is it easy to upload a new document over the top of an old in a SharePoint library?
Hoping someone can give me some answers.
Regards,
Bruce Officer

hi Bruce,
1. It sounds like what you need is to set the starting version number since your revision number increments in whole numbers, it would match up to SharePoint once the starting version number is set. You can potentially create a new custom field in the
library to manually track the version of the uploaded PDF document, but this might not match up with SharePoint's own version number and could get confusing. Another possibility is to upload dummy versions of the PDF document until the SP version
matches with the revision version and then delete these dummy versions.
2. When you upload the PDF document again into the library, it should prompt you to see if you want to replace the existing. If you proceed with the upload, it should replace and increment the SharePoint version number.
Please Mark Answered if my reply solves your problem. Thanks!
Jeff Thai
Technical Solutions Architect, AvePoint
http://www.AvePoint.com

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

Simple Item Version Control Default Option

Similar Messages

Maybe you are looking for