metadata folder in our workspace to SVN ignore list. You can, for example, add Check for modifications to the context menu, since you’ll probably use it often. Notice that in the WDJ project we have bin, gen_ddic, gen_wdp folders that will be populated by WDJ at compile time (thus they should not be included in SVN).īefore we go futher, you can add some useful shortcuts to the context menu of TortoiseSVN by selecting TortoiseSVN –> Settings, then General –> Context Menu from the context menu. This is how the project files look in the Resource Perspective of the NWDS. Java project has a POJO (Person.java) and WDJ project imports this POJO as Java Bean Model and maps it all the way to the visual controller in the main Web Dynpro component. We will create a simple WDJ and Java projects for illustration purposes. NWDS will complete the setup for the new workspace. Start NWDS with -data argument pointing to the c:\svn\workspace directory (copy NWDS shortcut, right click on the new shorcut, select Properties). You should now have a SVN controlled workspace directory ready for NWDS projects. Once the workspace (remote) folder has been created, check it out to your local c:\svn\workspace directory. Use SVN Repo Browser from the context menu in c:\svn folder to browse to the root folder of the SVN repository where you want to import your workspace. I also assume you have an SVN repository set up on a remote server. I assume we are going to create a new NWDS workspace under the path c:\svn\workspace.
This made it a breeze to be able to use an external SVN client with any type of NWDS project.ĭownload and install Tortoise SVN client, it integrates seamlessly with Windows file explorer interface. SVN folder containing all of the SVN metadata for the project. Fortunately, the recent versions of SVN protocol specify one top-level.
This caused, SVN clients to complain (since. When working with some type of projects like WDJ (or with DCs in Local Development), NWDS has to copy some contents around (gen* and bin folders) and recreate some folders upon every build. SVN folder with metadata being placed in every folder of the project. Until recently, the problem with this solution was that SVN protocol required an. The solution to the problem is to use an external SVN client to keep track of changes in the NWDS workspace, without Eclipse being aware of it. The problem is that, unlike the recent NWDS for AS 7.3, the older NWDS for AS 7.0 (in my case 7.0.25) is built on an old Eclipse version 2.1.2, which does not have many SVN plugins. All this, naturally, might get you thinking about using an SVN repository to track changes to your NWDS projects. Moreover, you are not always develop using Development Components (DCs) architecture required by NWDI. Sometimes you just need to be able to revert to or compare a file in your project with its version in the repository. But to setup a fully functioning NWDI is not always an option.
Normally, you should take advantage of NetWeaver Developer Infrastructure (NWDI) when developing with Java in NWDS, which takes care of revision control for you (among other things).
In this post I will show how we can setup and work with a popular code source and revision control tool - TortoiseSVN - together with the NetWeaver Developer Studio for AS version 7.0.