Version Control with Clearcase

Will anybody tell me how to use clearcase for version control with Jdeveloper? I use clearcase for version control and Jdeveloper as IDE. What are the configuration changes to be made to link jdeloper IDE to clearcase repository so that I can checkout files from clear case directly to Jdev IDE and check them in directly to clear case version control repository.

Hi Srinivas,
Integrated support for Clearcase is coming in a future version of JDeveloper.
In the meantime, you can use the checkin/checkout custom addin to drive clearcase.
Download the custom addins package from:
http://otn.oracle.com/products/jdev/info/CustomAddins.31/CustomAddinsJD31.zip
Then have a look at
http://otn.oracle.com/products/jdev/info/CustomAddins.31/CustomAddins.html#CheckOutIn.Java
for instructions. You will need to alter CheckIn.bat to change the following line:
put -S+_V -U %1
to
cleartool ci -nc -identical %1
And alter CheckOut.bat to change the following line:
get -l -Q -S+_V %1
to
cleartool co -nc -reserved %1
Brian

Similar Messages

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 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 DB

I wonder if some version control like SourceJammer, Prowler can be used along with some relational database in Java Application.
I am looking a requirement where along some relational data, I need to store some xml data as well and plan to use LOB feature of Database as most of the database are XML enabled. But I also need to display version history of those and get appropriate version and diff between version i.e. standard version control features along with check-in, check out. Open source solution is required.
At present, it is something like
Java Application -> O-R Mapper -> DB
Now needed some thing like:
Java Application -> O-R Mapper (should be here or before DB?) -> Version Control -> DB
Any thoughts, pointers/directions will be useful.
Thanks in advance.

Doyou want version control of the scripts that you use to create databases, or do you want version control of the objects in your database.
The former was descibed by another poster (i.e., wincvs). Alternatively, your data modeling tool should provide that type of service. For example, if you are using Oracle Designer then your data models can be versioned.
The latter type of versioning is supported by Oracle workspace manager and the new 10.2 releases of Oracle Content DB and Oracle Records DB. There's also versioned tablespaces in 10g.
-Mark
http://www.remidata.com/book_nuts2soup.htm

How to implement poor-man's version control with TSQL queries

I have a table called Project. Each row completely describes a project and has a username, project name, project description and other numeric parameters that contain all the data about the project.
When multiple rows have the same username, this means a user owns multiple projects.
Now I want to implement a poor-man's version control for my users by adding a new integer column called version. When a user wants to save a new version of his project, the version is incremented and a new row is inserted into the table.
Some projects will have 1 version, others will have a dozen or more.
By default, the user should see a data grid of projects where only the latest version of the project is displayed (including the version count) and all the older versions of each project are ignored.
How do I write a TSQL query to populate this data grid (and ignore every version except the latest versions of each project)?
Thanks
Siegfried
siegfried heintze

Should this work? It prints all the rows.
DECLARE @Projects TABLE
([id] int IDENTITY(1,1), [Project] varchar(1), [Version] int)
INSERT INTO @Projects
([Project], [Version])
VALUES
('A', 1),
('A', 2),
('A', 3),
('A', 4),
('B', 1),
('B', 2),
('B', 3),
('C', 1),
('C', 2),
('D', 1)
-- DECLARE @User varchar(100)
SELECT *
FROM @Projects p
WHERE
-- UserName = @User AND
NOT EXISTS (SELECT 1
FROM @Projects q
WHERE q.id = p.id
AND q.Version < p.Version)
siegfried heintze
Nope you have condition wrong
In my suggestion i've used > and you replaced it with <
it should be this
SELECT *
FROM @Projects p
WHERE
NOT EXISTS (SELECT 1
FROM @Projects q
WHERE q.project= p.projects
AND q.Version > p.Version)
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

Version control with concurrent InCopy and InDesign packages

Hi there,
If Editor A uses the "Forward for InCopy" option to create and send an InCopy package (.incp) to Editor B, and then erroneously uses the "Return for InDesign" function to create an InDesign package (.indp) before the Editor B has returned the new version of the package, can the superflous .indp file (that will never be used by anyone) be safely deleted?
The goal is to receive a new .incp file from Editor B and to treat it as the current version of the assignment, even though a .indp was accidentally created in the interim. Can we simply delete the .indp file or are there other complications that we need to consider?
Thanks.
--Stephen

Excellent, thank you! I just wanted to be certain.
--Stephen

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

Best practice for version control B2B, ESB and BPEL

Hello,
we are setting up a new system using B2B, ESB and BPEL. The development team is more experienced working with PL/SQL, Oracle Workflow and we are worried that Jdeveloper generates changes to the source files during development and that we might have problems with the version control.
Is there any best practice for setting up version control for these systems? Do we need to take anything in particular into consideration when setting up the projects?
We are using Serena Dimensions 9.1 for version control with the add-on in Jdeveloper.
Thanks in advance!

I believe JDeveloper has a plugin for Dimensions.
I havent used it but to get it, go to tools (It may be help I don't have JDeveloper on this machine to confirm) check for updates.
If you select the thrid party check box - next, you will see an entry for dimentions.
Configure the connection and develop as you would any other project.
cheers
James

Version Control question related to Visual SourceSafe.

I have a RoboHELP HTML (RH) project that is set up for
version control with Visual Source Safe (VSS). Now I need to create
a copy of this project and set up version control for it as well. I
tried copying the RH files and adding the copy to VSS. But when I
open the XPJ file from the copied folder, it still has references
to the version controlled original folder.
There are a lot of files in the copied folder that has
references to the original VSS location. How do I make this copied
project a self-containing version-controlled project with no
references to the original?
Thanks,
K

Hi Rick:
Tried the link to the aricle on RobWizard. It works sort-of,
however, I noticed that two files (eHlpDhtm.js and gg_sdk.pss) not
mentioned in that article have references to the old version
control information. What are these two files used for?
So far, it's working fine for me, but not for my colleagues
who are accessing this copied project. They all have gotten the
latest files from VSS on their machine. But the Getting Files
dialog box seems to be getting files from the old version control
location as well. Now my colleagues do not have modify privileges
to this old location at all. So when they try to edit a topic in
the new copy in the new version control location, RH gives an error
that says they don't have access rights to the old version control
location. Why should this happen since the copy of the project is
supposed to now only be aware of the new version control location.
Also, RH also says that is cannot check out the XPJ file from the
new version control location since exculsive privilege is required.
This is weird since the XPJ file is not checked out at all.
Any thoughts? Would the two files (eHlpDhtm.js and
gg_sdk.pss) mentioned in the first paragraph be cuasing this? Those
two files are the only ones in the copied project that have
information about the old version control location.
Thanks,
K

SQL DEV DATA MODELER VERSION CONTROL

Hi Anyone can tell me how to setup an environment to do version controlling with sql DEV data modeler.
Thanks

Hi,
you can use visualSVN server - it has a free edition http://www.visualsvn.com/server/
and getting started is here http://www.visualsvn.com/server/getting-started/
Philip

Version Control Tutorial

I am publishing a reference manual and want to put it under
version control. I also need to provide access to a team of authors
and editors.
I've checked the Adobe on-line tutorials and the one included
with RoboHelp HTML, but could not find any instructions on using
version control with WebHelp/WebHelp Pro.
Does anyone know of a good, comprehensive instruction on
setting up and using version control?
Thanks!
Charles Arnold
Technical Writer

Have you checked this article?
http://www.adobe.com/devnet/robohelp/articles/robosource_control_print.html

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

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

TS1382 Can my iPod Classic 160GB model MB565LL version 2.0.1 Mac be controlled with my Apple Remote if it is connected to the universal dock and connected to my stereo system

Can my iPod Classic 160GB model MB565LL version 2.0.1 Mac be controlled with my Apple Remote if it is connected to the universal dock and connected to my stereo system

Read this Apple Support Article on Apple REMOTE
Good luck!

Can my iPod Classic 160GB model MB565LL version 2.0.1 Mac be controlled with my Apple Remote if it is connected to the universal dock and connected to my stereo system

Can my iPod Classic 160GB model MB565LL version 2.0.1 Mac be controlled with my Apple Remote if it is connected to the universal dock and connected to my stereo system

Read this Apple Support Article on Apple REMOTE
Good luck!

Version Control with Clearcase

Similar Messages

Maybe you are looking for