* ox-taskjuggler.el (org-taskjuggler-default-reports)
(org-taskjuggler-project-plan): If the default reports contain
%title it will be replaced with the document title.
This is based on a suggestion by John Hendy.
* ox-taskjuggler.el (org-taskjuggler-get-start): Use both the
scheduled and the start property (if it is in
org-taskjuggler-valid-resource-attributes) to determine the
start of a task or the project.
Thanks to John Hendy for the report and thorough analysis.
* ox-taskjuggler.el (org-taskjuggler-process-command)
(org-taskjuggler-reports-directory): Add a defcustom to define
the tj3 command and the directory where the reports are to be
generated.
(org-taskjuggler-export-and-process)
(org-taskjuggler-export-process-and-open): Split the command
so that you can now process and open in separate commands.
(org-taskjuggler-compile): New function to process a tjp file
using org-taskjuggler-process-command.
Finally we have support for processing and opening the exported file
with tj3. For TaskJuggler 2.4 this always worked. Now it also works
for tj3. `org-taskjuggler-export-and-process' exports the file and
runs it through tj3. `org-taskjuggler-export-process-and-open'
additionally opens the reports in a browser.
* ox-taskjuggler.el (org-taskjuggler-default-reports): Set the default
reports so that the user gets a good out-of-the-box experience with
tj3.
The defaults in the defcustom now out-of-the-box support tj3. If you
really want to export to taskjuggler 2.x the documentation explains
how you can do that.
* ox-taskjuggler.el: Update the comment section to TaskJuggler
3.x.
(org-taskjuggler-target-version): Add a link to
`org-taskjuggler-default-reports' to make it clear that both
need to be changed in order to support TaskJuggler 2.4.
* contrib/lisp/ox-taskjuggler.el (org-taskjuggler-target-version): The
default target is now tj3
Since taskjuggler is not developed anymore and hardly any
distributions carry it anymore we ought to target tj3 by default now.
* contrib/lisp/ox-taskjuggler.el (org-taskjuggler--build-task): Fix
the check whether a node has no children
A milestone should only (automatically) be inserted if a node has no
children and no duration defined.
Christian Egli
Christian Egli
Baptiste
Nicolas Goaziou
Bastien Guerry