emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Baptiste <bateast@bat.fr.eu.org>
To: Org-mode <emacs-orgmode@gnu.org>
Subject: Taskjuggler export deals badly with first parent match
Date: Fri, 19 Apr 2013 10:54:41 +0200	[thread overview]
Message-ID: <87k3nyaoj4.fsf@bat.fr.eu.org> (raw)


Hi,

first of all, thanks for the hard work to make 8.0 get out.

I found ox-taskjuggler broken in /task_id/ identification when it is non trivial.

here is an example this is not fine at my side

: Org-mode version 8.0 (release_8.0-1-g5ef07d @ …)

#+BEGIN_EXAMPLE
* Project                                               :taskjuggler_project:

** Training material
   :PROPERTIES:
   :task_id:  training_material
   :END:
*** Markup Guidelines
    :PROPERTIES:
    :Effort:   2d
    :task_id:  markup
    :END:
*** Workflow Guidelines
    :PROPERTIES:
    :Effort:   2d
    :END:
** Presentation
   :PROPERTIES:
   :Effort:   2d
   :BLOCKER:   markup
   :END:
#+END_EXAMPLE

At export, it gives

#+BEGIN_EXAMPLE
task project "Project" {
  purge allocate
  allocate cancelled
  task training_material "Training material" {
    task markup "Markup Guidelines" {
      effort 16.0h
    }
    task workflow "Workflow Guidelines" {
      effort 16.0h
    }
  }
  task presentation "Presentation" {
    depends !!training_material.markup
    effort 16.0h
  }
}
#+END_EXAMPLE

which fails compiling (for good reasons) with
:  Error in scenario plan: Task project.presentation has unknown depends training_material.markup

actually, the line
:     depends !!training_material.markup
should be
:     depends !training_material.markup

– this is an easy fix is this baby example, but on my whole project, I have tons of false references :'( –

again, thanks :)

--

: ~^v^~ Bat

             reply	other threads:[~2013-04-19  7:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-19  8:54 Baptiste [this message]
2013-04-19  9:32 ` Taskjuggler export deals badly with first parent match Nicolas Goaziou
2013-04-19 11:20   ` Baptiste
2013-04-19 11:21   ` Baptiste

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87k3nyaoj4.fsf@bat.fr.eu.org \
    --to=bateast@bat.fr.eu.org \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).