Browse Source

Do not treat the limits attribute any different than the others

i.e. you have to specify the limits attribute with {} so that
taskjuggler understands it properly. This is for the sake of
consistency.
Christian Egli 15 years ago
parent
commit
a81d93a355
1 changed files with 3 additions and 4 deletions
  1. 3 4
      lisp/org-taskjuggler.el

+ 3 - 4
lisp/org-taskjuggler.el

@@ -110,6 +110,8 @@
 ;;   - Look at org-file-properties, org-global-properties and org-global-properties-fixed
 ;;   - What about property inheritance and org-property-inherit-p?
 ;;   - Use TYPE_TODO as an way to assign resources
+;;   - Make sure multiple dependency definitions (i.e. BLOCKER on
+;;     previous-sibling and on a specific ID) in multiple attributes are properly exported.
 ;;
 ;;; Code:
 
@@ -469,10 +471,7 @@ If the ATTRIBUTE is not in ITEM return nil."
   (cond 
    ((null item) nil)
    ((equal (symbol-name attribute) (car (car item)))
-    (cons (or 
-	   (and (equal attribute 'limits)
-		(format "%s { %s }" (symbol-name attribute) (cdr (car item))))
-	   (format "%s %s" (symbol-name attribute) (cdr (car item))))
+    (cons (format "%s %s" (symbol-name attribute) (cdr (car item)))
 	  (org-taskjuggler-get-attribute (cdr item) attribute)))
    (t (org-taskjuggler-get-attribute (cdr item) attribute))))