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

Similar Messages

SQLDeveloper Version Control

I have seen some posts regarding version control in SQLDeveloper. Evidently, integration with PVCS is a feature to be added in some future version.
There might be an easier way to handle it. If SQLDeveloper would allow us to specify a "version logging" folder, and if it would then create a new version of any edited source file in that folder, each time you press the save button, then this would handle 80% of the need, with only 1% of the complexity.
For example, suppose the object was named "MyView", and then I edit it. Then, in the logging folder, we end up with file name "MyView.sql" in the logging folder. If I edit again, then the previous version is renamed as "MyView 09-20-06 10_44_22.sql" (append the time and date to the file name), and a new version MyView.sql is put into the logging folder.
You maintain the time-stamped file versions, forever. You might have like a two week or 500 version limit, or something like that, so the folder does not fill up infinitely.
That is about it. If you made a mistake, and needed to roll it back, you just grab a previous version. If you want to check it into PVCS, then you just take the file and copy it into your source folder and then check it in.
You are never going to be able to fully integrate SQLDeveloper with PVCS, because the target keeps moving. Instead, you should focus on simple compatibility between the two approaches.
The current method of edits directly in the database and no roll-back and no ability to check-in the code other than copy and paste, this does not work.

Umm.. The reason that people ask for version control integration is to save time. Switching to another application to check in/out files is a huge waste of time as well as being error prone.
Tools like JDeveloper and Eclipse have histories like what you are asking for. Histories such as that are a great help when debugging files, but cannot be substituted for good source control integration.
Oracle, can we get the 'history' tab enabled in the file editors like JDeveloper? That feature is great in JDeveloper and would be a great edition to SQL Developer.

Version control J2EE applications

Hello,
This is a fairly general question regarding version control. I want to bundle a J2EE application as an EAR file and deploy it to a number of different application servers. On every server where the EAR file is deployed, I would like to keep a history of what version of the J2EE application was installed, and when.
For example, say I have 3 servers (S1, S2, and S3), and want to deploy myApp.ear to all 3. Something's gone wrong (the application doesn't deploy to S2), and we're not aware of any problems until users start complaining. How can I check which version of my J2EE application has been successfully deployed on each server at a glance?
Are there any logs kept regarding J2EE deployment histories in the Enterprise Manager? How are these logs maintained? Are they self maintianing?
We currently have a custom made installation system for non J2EE apps that adds an entry to a table on one of our databases that records the username, date, time and version of a particular application when it is installed. We can't use this custom installation system when we bundle our applications as EARs.
Basically, how have you guys (other professionals) managed software releases with EARs? Can you recommend any methods, articles, or utilities? Does 10g Application Server provide any means of managing releases?
Thanks for your input!

Hello,
You bring up an interesting problem. At the moment 10.1.2 does not have anyway to manage releases, however there is a simple way out of this.
When creating the ear file (i.e. pre-deploy), you can add a versions.txt to your ear file which will have the version number of the application. In regards to the time-stamp, the application server will create a directory (under applications and application-deployments) for the respective deployment. In conjunction with the version.txt and the timestamp of your files on the OS, you could get a pretty good feel of releases.
If you implement your own logging into a file system (which means writing more code), you could do this as well.
You could also write a servlet that starts-up and writes this data to the DB, however please note that this write will happen every time you start the OC4J instance, so this might not be a good solution.
Hope this helps.
Deepak

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

Best practice for version control

Hi.
I'm setting up a file share, and want some sort of version control on the file share. What's the best practice method for this sort of thing?
I'm coming at this as a subversion server administrator, and in subversion people keep their own copy of everything, and occasionally "commit" their changes, and the server keeps every "committed" version of every file.
I liked subversion because: 1) users have their own copy, if they are away from the office or make a big oops mistake, it doesn't ever hit the server, and 2) you can lock a file to avoid conflicts, and 3) if you don't lock the file and a conflict (two simultaneous edits) occur, it has systems for dealing with conflicts.
I didn't like subversion because it adds a level of complexity to things -- and many people ended up with critical files that should be shared on their own hard drives. So now I'm setting up a fileshare for them, which they will use in addition to the subversion repository.
I guess I realize that I'll never get full subversion-like functionality in a file share. But through a system of permissions, incremental backups and mirroring (rsync, second-copy for windows users) I should be able to allow a) local copies on user's hard drives, b) control for conflicts (locking, conflict identification), and keeping old versions of things.
I wonder if anyone has any suggestions about how to best setup a file share in a system where many people might want to edit the same file, with remote users needing to take copies of directories along with them on the road, and where the admin wants to keep revisions of things?
Links to articles or books are welcome. Thanks.

Subversion works great for code. Sort-of-ok for documents. Not so great for large data files.
I'm now looking at using the wiki for project-level documentation. We've done that before quite successfully, and the wiki I was using (mediawiki) provides version history of pages and uploaded files, and stores the uploaded files in the file system.
Which would leave just the large data files and some working files on the fileshare. Is there any way people can lock a file on the fileshare, to indicate to others that they are working on it and others shouldn't be modifying it? Is there a way to use unix permissions (user-group-other) permissions, "chmod oa-w" to lock a file and indicate that one is working on it?
I also looked at Alfresco, which provides a CIFS (windows SMB) view of data files. I liked it in principle, but the files are all stored in a database, not in the file system, which makes me uneasy about backups. (Sure, subversion also stores stuff in a database, not a file system, but everyone has a copy of everything so I only lose sleep about backups regarding version history, not backups on the most recent file version.)
John Abraham
[email protected]

Version Control for adobe forms

Dear All,
We have a situation where we already go live with version 0 of our adobe form. Now, we have an enhancement to the form i.e.: some new functionalities and new field. Previously we have tried to transport the new changes to the production without any version control and those processes that have been already started prior to the new changes encounter error when the user continues the process.
I am wondering how do the version control works and any documentation on how to configure it?
Thanks in advance
Regards,
Bryan

Hi Brian,
Here is some information that I found in the IMG on Create ISR Scenario...
Create ISR Scenario
Use
In this IMG activity, you create an ISR scenario that has a one-to-one relationship with a form scenario. To be able to use a form scenario in a process, one ISR scenario must exist for each form scenario. The ISR scenario and the form scenario must be linked with each other. You make this setting in Customizing for HR Administrative Services in the IMG activity Link ISR Scenario with Form Scenario.
In the form scenario, you define primarily the basic set of form fields and their processing through the backend services. In the ISR scenario, you specify the definition of the user interface. You also specify which form is used for the display and how the layout of this interactive form is designed. You use interactive forms based on Adobe software to create and process the forms.
ISR scenarios and form scenarios are version dependent. The version numbers of the ISR scenario are assigned automatically. Note that a form scenario must have exactly the same version as the linked ISR scenario. For this reason, you should always create a new version in the ISR scenario first and then use the same version number when you create a version in the form scenario manually.
Note
If an ISR scenario or form scenario (with an existing version) has already been used in a productive process, you should not change the configuration. If you want to make changes to a process or an ISR scenario or form scenario, you should always create a new version, and only ever use that new version in the future. In this way, processes that have been started can be concluded with the old version and new processes can be started simultaneously with the new version.
This is from the Create Form Scenario documentation...
Create version
Form scenarios are version dependent, which means that there is at least one version of each form scenario. Versions are linked with processes. Since processes can vary, you must also be able to adjust the associated scenarios. To be able to provide different forms for process variants, you create versions.
You can still process and change an existing version at a later point in time. Once a version has been used to execute a process, you should not make any more changes to this version; instead, you should create a new version.
The form scenario and the (linked) ISR scenario are both version dependent. They must always have exactly the same version numbers. Note that the version number of the ISR scenario is generated and cannot be entered manually. When you create a new version in the form scenario, you therefore have to use the version number generated in the ISR scenario.
If you have already made extensive Customizing settings for the form scenario and want to create a new version based on the settings, you should use the IMG activity Manage Form Scenario.
Hope this helps...
Cheers,
Kevin

What is version control in oracle apps

hi,
I want to know what is version control , why it is done for... please help me in this regard...

Version Control Tools used to maintain developed code multiple version .
there are many types of it like WINCVS,PVCS,SVN and SVN on oracle usually we use PVCS version control tools.
safe eldin siddig

Report Builder RDF, XML, REP and Version Control

I'm looking to convert our existing RDF reports to XML format to better support version control and have a few questions.
- Are there any issues with converting these RDF files to XML and developing them going forward?
- When it's time to deploy to the server we'll convert them to RDF or REP. Any issues?
- This question was asked before, [Thread: Oracle Reports Builder - RDF vs XML|https://forums.oracle.com/forums/thread.jspa?threadID=721959], but that was over 3 years ago. Have the issues been resolved?
- Is anyone currently following the workflow I've outlined with success?
Couple of links of interest regarding this topic.
[Tuning Oracle Reports - 20.5.1 Paper Layout|http://download.oracle.com/docs/html/B14048_02/pbr_tune.htm#i1007252]
[Running Report Requests - 13.3 Deploying Your Reports|http://download.oracle.com/docs/html/B14048_02/pbr_run.htm#i1008764]
My Oracle Report Builder Version Info (Help -> About)
Report Builder 10.1.2.0.2
ORACLE Server Release 10.1.0.4.2
Oracle Procedure Builder 10.1.2.0.2
Oracle ORACLE PL/SQL V10.1.0.4.2 - Production
Oracle CORE 10.1.0.4.0 Production
Oracle Tools Integration Services 10.1.2.0.2
Oracle Tools Common Area 10.1.2.0.2
Oracle Toolkit 2 for Windows 32-bit platforms 10.1.2.0.2
Resource Object Store 10.1.2.0.2
Oracle Help 10.1.2.0.2
Oracle Sqlmgr 10.1.2.0.2
Oracle Query Builder 10.1.2.0.2 - Production
PL/SQL Editor (c) WinMain Software (www.winmain.com), v1.0 (Production)
Oracle ZRC 10.1.2.0.2
Oracle XML Developers Kit 10.1.0.4.2 - Production
Oracle Virtual Graphics System 10.1.2.0.2
Oracle Image 10.1.2.0.2
Oracle Multimedia Widget 10.1.2.0.2
Oracle Tools GUI Utilities 10.1.2.0.2
Edited by: 896352 on Nov 9, 2011 2:35 PM

Hi Michael,
Per my understanding that you want to find a solution for version control when you design the report using the Report Builder 3.0, right?
As you know that Report Builder is a tool which can only work on one single file instead of a project , so the current version of Report Builder doesn't have these capabilities. You can submit a feature request about it on the Microsoft UserVoice site
here:
http://visualstudio.uservoice.com/forums/121579-visual-studio/category/53187-sql-bi-tools-srs-ssis-ssas-
Generally, visual Studio Team System and Visual Source Safe integrate with the Visual Studio/BIDS shell and third-party source control solutions like SVN managed from the file system play well with version control. So I would suggest you to consider use
them instead.
In conclusion, one possible workaround for you is that you can save all .rdl files in third part tool’s(TFS) workspace folder for version control purpose (check in, check out with the Windows Shell Extension), and you can use Report Builder to edit these
report files. Then use Report Builder to deploy the .rdl file to Report Server.
More details information about the version control for your reference:
https://sqlserverbiblog.wordpress.com/tag/ssrs-version-control/
Similar thread for your reference:
https://social.msdn.microsoft.com/Forums/en-US/939b3a90-067d-4593-b456-76533c9d60ce/sync-ssrs-visual-studio-project-with-ssrs-server-alm?forum=sqlreportingservices
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/1ad0db30-7fd8-4007-9731-ec8f2f44605f/report-format-rdl-version-control?forum=sqlreportingservices
If you still have any question, please feel free to ask.
Regards
Vicky Liu

How can version control check-in prompts be disabled?

We are using RoboHelp 11 with TFS for version control, and the check-in prompts are killing our productivity. The TFS interface is slow to begin with, but we are getting 3-4 prompts every time we do something as simple as renaming a file, plus tons of "No Changes to Check-In" message boxes we have to clear. If we move a folder containing several topics and images, it gets downright ridiculous. I literally just had to sit for 23 minutes clicking on confirm boxes just to move a folder from one location to another - there were about 4 confirm boxes to click for every single topic file and image file. Is there a solution for this?

I believe these dialogs are from TFS, not from RoboHelp. Ask your TFS admin. He may be able to disable those prompts.
Kind regards,
Willam

Cp5 Project version control

Hi all
Can anyone recommend best practice for version control in Cp5? In other documentation I'm in the habit of saving the version number in the file name, but with Captivate, if there are links to projects, changing file names with every edit will cause problems.
Any advice would be appreciated.
Regards
Amanda

I don't know of a way to do this so that you can see the version information without opening the Captivate file. My way to include version information within the .cptx file is to put the version number into a caption on the title slide of the presentation. If the version number is only relevant to the developer(s), make the caption invisible, but if you want users to be able to see it in the published presentation, leave it visible and format it appropriately (e.g., a transparent caption with say 8 point font, at the very bottom of the slide).

Version control and deployment strategies

Hi,
I was looking for input from the community on general
strategies for using version control and managing deployments to
test/stg/production.
Currently, I am using subversion to track my source code, and
using the standard flex builder build routine to produce my binary
output and test. My output is stored locally on a shared vmware
drive, so that it can be served up with a linux vm running apache
(this is not dissimilar to just local testing)
Now I'm getting ready to deploy to some remote testing server
though, so I'm trying to think of the best way to go about it. I
would like to tag my code in svn with a release tag, as is my
practice in other platforms. Should I also store the bin folder in
svn? Should I check in the resulting binary code independently in a
separate repository/directory and then tag it there? Should I
create a new build target to deploy directly to my testing server?
The issue with the tagging approach seems to be that if I
want to rebuild the code or redeploy it for any reason, I would
have to checkout the tagged code in a separate directory, import it
as a new project, rebuild and then redeploy.
If I checked in the tested binaries into a separate
repository/folder, I could always just do an svn export for
deployment, but I'm not sure if that would cause any weird issues,
and it seems a bit wasteful. I suppose I could build from the tag
and zip up the resulting release and just make it available via
normal download, but it seems that I would likely then have lots of
working directory checkouts as flex builder projects for each tag
or release, just so that I could rebuild from them....doesn't seem
very elegant.
I'm very interested in hearing any feedback on this. How do
you do it?
thanks,
Cliff

flex with ant is still not very very popular
combination,since FB does all for you anyways, but I have to say
ant is lot more flexible, especialy if you combine it with FB, ant
can do pretty much anything, ...
here is link about flex's ant tasks
http://livedocs.adobe.com/flex/3/html/help.html?content=anttasks_1.html
most of the projects I have done in Flex were with ant,
here is general approach:
for internal testing I let flex builder build and deploy
within integrated tomcat,this is also where I do debugging, FB is
pretty good about that.
then I have following targets :
build target - builds optimized version of flex app, only
using library classes that are needed by project, also using that
to feed my Modules building tasks so that they exclude all class
references (like Button, Tabnavigation etc... ) from their compiled
units,
something like this (this is my old fb2 example) i don't have
fb3 example handy right now :
quote:
<mxmlc file="${basedir}/main.mxml"
debug="false"
optimize="true"
output="${dir.web}/main.swf"
show-binding-warnings="false"
show-actionscript-warnings="false"
link-report="${basedir}/docs/my-links.xml"
use-network="true">
<load-config
filename="/configdir/modified/flex-config.xml"/>
<source-path path-element="${FLEX_HOME}/frameworks"/>
<compiler.library-path dir="." append="true">
<include name="lib" />
</compiler.library-path>
<compiler.source-path path-element=""/>
<compiler.source-path path-element="src"/>
<metadata description="some app">
<contributor name="John Doe" />
<contributor name="Apple Orangino" />
</metadata>
</mxmlc>

<mxmlc file="${basedir}/mymodule.mxml"
debug="false"
optimize="true"
output="${dir.web}/mymodule.swf"
show-binding-warnings="false"
show-actionscript-warnings="false"
load-externs="${basedir}/docs/my-links.xml"
use-network="true" >
<load-config
filename="/configdir/modified/flex-config.xml"/>
<source-path path-element="${FLEX_HOME}/frameworks"/>
<compiler.source-path path-element=""/>
<compiler.source-path path-element="src"/>
<metadata description="some app">
<contributor name="John Doe" />
<contributor name="Apple Orangino" />
</metadata>
</mxmlc>
tag -target tags release based on parameter of latest tag
plus number increment I configure in properties file.
Utility targets :
classpath target - builds classpath string for compc task.
commit target : commits source code, before building.
resources target - copies all resources files to build
directory,
deploy-local target- deploy to local Integration server
deploy-remote target deploy to remote uat server.
test -target - run test cases over classes and generate
report.
and of course all famous asDoc target :)
good thing is that you can create "ant builder" under project
properties and chain your targets with flexbuilder's build
commands,
you can also easily integrate with build servers ( I use
hudson)
here is example :
http://hudson.amostudio.com/
MR hudson checks out code for you, builds it using ant
targets you tell it to use, and reports to you, its pretty cool and
very handy to always have active build proccess over codebase, of
course in some cases its overkill, but most of the times, MR hudson
is good to have.
unfortunately all my ant files are for external clients I
cant disclose them, but I can write blog about some general (apples
and oranges) example, hhm that's actually good idea :) I can shake
off some stress as well :)
thanks for the idea :)
hth
regards
levan

Version control in BO 6.5 & XI

How is the versioning controlled in Business Objects? Do we need to use any configuration management tool for bO 6.5? Is it inbuilt in BO XI?

Hi Navneet,
There are some version control tools for BO, like BISolid.
What they do is versioning of universes and reports, and they control the deployment towards the different repositories.
Makes it easy to rollback a version in production, or automates the manual steps needed to promote a report/universe.
Regards,
Lisette Johnson

Version Control System?

Is there an option for integrated version control?
Specifically, is there a recommended plug-in available that
integrates with Visual Source Safe (2005)? I'm using the dedicated
Eclipse IDE for Flex 2 (ie... I'm not running Eclipse with the Flex
2 plugin)
I'm using Visual Studio 2005 and web services to integrate
with Flex 2. I'm having a wonderful experience so far....kudos to
your product team (I seriously think Microsoft delayed their
expressions' tools after trying this out.) I hope you consider
creating a Visual Studio plugin for Flex.
Thanks,
Daniel

There are options for source control plugins for Eclipse
(Flex Builder 2), but you'd have to go to the eclipse site to see
what those options are.
Here's the link to our bug and enhancement request form:
http://www.adobe.com/cfusion/mmform/index.cfm?name=wishform&product=20&6213=35
Please give as much detail as you can regarding your desire
for a Visual Studio edition of Flex. Can't hurt to ask.

Version control bug

JDev Team,
a) The candidates tab of pending changes window lists the "JDeveloper project" files although I have "**/*.jpr" added to global ignore list.
b) Incoming tab of pending changes window does not bring in changes checked into version control repository. I checked in a file using the previous version of JDeveloper which is not recognized by the incoming tab.
I am using subversion for my version control.
Thanks
Message was edited by:
balar1

Hello
The global ignore list is used by many components within JDeveloper. The Navigator and Pending changes windows are included in that list. Any file pattern that is defined in the global ignore list will get applied to the navigator and pending changes window. The project (jpr) file is very important to the navigator so you should not define a pattern that would make the project file to be removed from the navigator. I believe that defining this pattern (**/*.jpr) will be excluded from the list. Oracle recommends that project files are version controlled. Is there a specific reason why you don't want to version control them?
The Incoming changes window lists files that have a later revision number in the subversion repository from the copy you have in your working copy (file on disk). If you checked in a file and the revision in the repository is the same as the revision in your working copy it will not be listed in the incoming changes window. If the revision in the repository is later then it may not be shown in the incoming changes window, because the window has not be refreshed. The window is automatically refreshed on a timer (15 min) or you can manually refresh it
Regards
Dave

Compare version control file

I installed SVN server and makes version controls work.
I tried to compare 2 version and Dreamweaver asks me to select application to compare 2 versions file.
Does Dreamweaver has any compare versions applications?
If not then can you please advise any program to download to install for comparing 2 versions?
By the way, I just learned that Dreamweaver just allows user to use either version controls or check in and check out.
Is it true that Dreamweaver only can use one of them at same time?
Your help and information is great appreciated,
Regards,
Iccsi,

Is it true that Dreamweaver only can use one of them at same time?
Right. If you use version control you don't need the other option.
Does Dreamweaver have any compare version applications?
No.
Do a Google search for FileMerge, BBEdit or TextWrangler.
See Comparing Files for Differences:
http://help.adobe.com/en_US/dreamweaver/cs/using/WSc78c5058ca073340dcda9110b1f693f21-7edda .html
Nancy O.

Regarding version control

Similar Messages

Maybe you are looking for