Difference between revisions of "Developers:howtoUseSVN"

From RifidiWiki

Jump to: navigation, search
(New page: -Subversion structure- example package org.rifidi.example --first create a directory with the bundle name in tags-- rifidi branches tags org.rifidi.example trunk org.rifidi.ex...)
 
 
(4 intermediate revisions by 2 users not shown)
Line 1: Line 1:
-Subversion structure-
+
=Subversion structure=
 
example package org.rifidi.example
 
example package org.rifidi.example
--first create a directory with the bundle name in tags--
+
==first create a directory with the bundle name in tags==
  rifidi
+
(required to allow easier work later on)
  branches
+
  -rifidi
  tags
+
  -branches
   org.rifidi.example
+
  -tags
  trunk
+
    -org.rifidi.example
  org.rifidi.example
+
      -2.0.1
 +
      -2.0.2
 +
      -...
 +
   -trunk
 +
    -org.rifidi.example
 +
==second edit the version of the bundle==
 +
*open the manfifest of the bundle
 +
*select overview
 +
*edit Version:
 +
**first digit: major version (in our case 2)
 +
**second digit: minor version (should be changed if an interface or a behavior has been changed)
 +
**third digit: patch level (should be changed after one or some bugs got fixed, the fixes were checked and everything is in svn)
 +
*after submitting create a tag
 +
**select create branch/tag
 +
**change the word trunk to tag , add a slash on the end and then type the new version
 +
**example:
 +
from: https://transcends.svn.cloudforge.com/rifidi/trunk/org.rifidi.example
 +
to: https://transcends.svn.cloudforge.com/rifidi/tags/org.rifidi.example/2.0.1

Latest revision as of 12:38, 29 June 2014

Subversion structure

example package org.rifidi.example

first create a directory with the bundle name in tags

(required to allow easier work later on)

-rifidi
  -branches
  -tags
    -org.rifidi.example
      -2.0.1
      -2.0.2
      -...
  -trunk
    -org.rifidi.example

second edit the version of the bundle

  • open the manfifest of the bundle
  • select overview
  • edit Version:
    • first digit: major version (in our case 2)
    • second digit: minor version (should be changed if an interface or a behavior has been changed)
    • third digit: patch level (should be changed after one or some bugs got fixed, the fixes were checked and everything is in svn)
  • after submitting create a tag
    • select create branch/tag
    • change the word trunk to tag , add a slash on the end and then type the new version
    • example:
from: https://transcends.svn.cloudforge.com/rifidi/trunk/org.rifidi.example
to: https://transcends.svn.cloudforge.com/rifidi/tags/org.rifidi.example/2.0.1
Personal tools