Control PackageScope During Command Line Generation

Uploaded report templates and discussions about reports.

Moderators: sarawut_w, Moderators

Control PackageScope During Command Line Generation

Postby » Tue Oct 12, 2021 7:17 pm


I would like to access a nested package via command line generation. I am specifying the scope via the -package option. I am not receiving the expected package. The generated document when generating within the app is different from its command line counterpart using the same template document. I suspect that there is another package with the same name but I am having a hard time tracking down the package.
I have a couple questions:
- How do I specify the exact package I want to input when using command line to generate?
- Are there any helper macros or properties I can use to help me locate this mystery element within the project?

Thank you for your time,

For more info:
I am using the following template file to debug:
Code: Select all
#foreach($p in $packageScope)
- $
  - $p.documentation
  - $p.elementType
  - $p.ownedBy
  - $elementURL

I get this with <redacted info> when generating from within MagicDraw on desired package:
Code: Select all
- <Package Name here>
  - <Package Documentation here>
  - resourcestaxonomy

I get this from command line generation with the following properties file:
Ran from
Code: Select all
C:\Program Files\MagicDraw\plugins\com.nomagic.magicdraw.reportwizard

Property file:
Code: Select all
#----main argument ----#
project = <path\\to\\local_project>.mdzip
output =  <path\\to>\\debug_packageScope.txt
template = debug_package_scope
package = <Package Name>

Command line generated code:
Code: Select all
- <Package Name here>
  - requirements
Forum Newbie
Forum Newbie
Posts: 1
Posts Rating:0
Joined: Tue Oct 12, 2021 6:08 pm

Return to Report Engine

Who is online

Users browsing this forum: No registered users and 1 guest