Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Gendoc » Command line
Command line [message #1709449] Mon, 28 September 2015 13:09 Go to next message
Francois Le Fevre is currently offline Francois Le FevreFriend
Messages: 56
Registered: October 2014
Location: Paris Saclay, France
Member
Dear Gendoc community,
I have seen you have implemented a command line interface, https://wiki.eclipse.org/Gendoc/FunctionalFeatures

I was not able to find documentation on this point.
How can I use it?

Thanks

Francois

Report message to a moderator

Re: Command line [message #1709454 is a reply to message #1709449] Mon, 28 September 2015 13:52 Go to previous messageGo to next message
Tristan Faure is currently offline Tristan FaureFriend
Messages: 460
Registered: July 2009
Senior Member
Hello indeed information is not available in the PDF tutorial we will fix it

to run command line :

java -cp "ECLIPSE_PATH\plugins\org.eclipse.equinox.launcher_XXXX.jar" org.eclipse.core.launcher.Main -application org.eclipse.gendoc.batch.GendocBatchMode -idt dir="D:\your_template.docx"


if you want to specify a specific workspace you can add -data option : 

java -cp "ECLIPSE_PATH\plugins\org.eclipse.equinox.launcher_XXXX.jar" org.eclipse.core.launcher.Main -application org.eclipse.gendoc.batch.GendocBatchMode -data d:\workspace_directory  -idt dir="D:\your_template.docx"


HTH
Tristan



[Updated on: Mon, 28 September 2015 13:53]

Report message to a moderator

Re: Command line [message #1709603 is a reply to message #1709454] Tue, 29 September 2015 13:39 Go to previous messageGo to next message
Francois Le Fevre is currently offline Francois Le FevreFriend
Messages: 56
Registered: October 2014
Location: Paris Saclay, France
Member
Thanks for the quick answer.

Report message to a moderator

Re: Command line [message #1728870 is a reply to message #1709449] Fri, 08 April 2016 07:09 Go to previous messageGo to next message
Benajmin Schoenholzer is currently offline Benajmin SchoenholzerFriend
Messages: 33
Registered: March 2016
Member
Hi

Im trying to use gendoc by command line in combination with papyrus. But on my installation it doesn't work. Does everybody know why this error happened? Thanks for your help.

Greetings
Benny

Quote:

C:\Users\Benny\PapyrusWorkspace\DevelopmentEnvironment>java -cp "C:\Papyrus\plugins\org.eclipse.equinox.launcher_1.3.100.v20150511-1540.jar" org.eclipse.core.launcher.Main -application org.eclipse.gendoc.batch.GendocBatchMode -idt dir="C:\Users\Benny\PapyrusWorkspace\DevelopmentEnvironment\"
log4j:WARN No appenders could be found for logger (root).
log4j:WARN Please initialize the log4j system properly.
Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1
Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1
Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1
Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1
Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1
Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1
Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1
Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1
Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1
Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1
Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1
Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1
Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1
Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.jdt.internal.ui.InitializeAfterLoadJob
Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1
Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1
Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1
Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1
Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1
Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1
Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1
Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1
Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1

C:\Users\Benny\PapyrusWorkspace\DevelopmentEnvironment>

Report message to a moderator

Re: Command line [message #1728902 is a reply to message #1728870] Fri, 08 April 2016 12:08 Go to previous messageGo to next message
Tristan Faure is currently offline Tristan FaureFriend
Messages: 460
Registered: July 2009
Senior Member
Okay it seems some plugins spam the CLI
what version of Papyrus are you using ?
can you copy paste the content of the .log file inside metadata folder of your workspace ?



Report message to a moderator

icon5.gif  Re: Command line [message #1728949 is a reply to message #1709603] Fri, 08 April 2016 15:41 Go to previous messageGo to next message
Benajmin Schoenholzer is currently offline Benajmin SchoenholzerFriend
Messages: 33
Registered: March 2016
Member
Hello

Sorry today i am a annoying guy. The .log file doen't exists. I think its cause of the log4j warnings....but i received a huge exeption in the console...

I execute the following command:
Quote:

java -cp "C:\Papyrus\plugins\org.eclipse.equinox.launcher_1.3.100.v20150511-1540.jar" org.eclipse.core.launcher.Main -application org.eclipse.gendoc.batch.GendocBatchMode -data C:\Users\Benny\PapyrusWorkspace -idt dir="C:\Users\Benny\PapyrusWorkspace\DevelopmentEnvironment\doc\generic_template_new.docx"


Quote:

C:\Users\Benny>java -cp "C:\Papyrus\plugins\org.eclipse.equinox.launcher_1.3.100.v20150511-1540.jar" org.eclipse.core.launcher.Main -application org.eclipse.gendoc.batch.GendocBatchMode -data C:\Users\Benny\PapyrusWorkspace -idt dir="C:\Users\Benny\PapyrusWorkspace\DevelopmentEnvironment\doc\generic_template_new.docx"
log4j:WARN No appenders could be found for logger (root).
log4j:WARN Please initialize the log4j system properly.
org.eclipse.core.runtime.AssertionFailedException: null argument:Realm cannot be null
at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:85)
at org.eclipse.core.databinding.observable.ChangeManager.<init>(ChangeManager.java:37)
at org.eclipse.core.databinding.observable.AbstractObservable.<init>(AbstractObservable.java:29)
at org.eclipse.core.databinding.observable.value.AbstractObservableValue.<init>(AbstractObservableValue.java:42)
at org.eclipse.core.databinding.observable.value.AbstractObservableValue.<init>(AbstractObservableValue.java:35)
at org.eclipse.papyrus.infra.gmfdiag.common.databinding.custom.AbstractCustomStyleObservableValue.<init>(AbstractCustomStyleObservableValue.java:53)
at org.eclipse.papyrus.infra.gmfdiag.common.databinding.custom.CustomIntStyleObservableValue.<init>(CustomIntStyleObservableValue.java:23)
at org.eclipse.papyrus.uml.diagram.common.editparts.RoundedCompartmentEditPart.addNotationalListeners(RoundedCompartmentEditPart.java:173)
at org.eclipse.gmf.runtime.diagram.ui.editparts.GraphicalEditPart.activate(GraphicalEditPart.java:179)
at org.eclipse.papyrus.uml.diagram.common.editparts.NamedElementEditPart.activate(NamedElementEditPart.java:232)
at org.eclipse.gef.editparts.AbstractEditPart.activate(AbstractEditPart.java:160)
at org.eclipse.gef.editparts.AbstractGraphicalEditPart.activate(AbstractGraphicalEditPart.java:195)
at org.eclipse.gmf.runtime.diagram.ui.editparts.GraphicalEditPart.access$0(GraphicalEditPart.java:1)
at org.eclipse.gmf.runtime.diagram.ui.editparts.GraphicalEditPart.activate(GraphicalEditPart.java:205)
at org.eclipse.gmf.runtime.diagram.ui.editparts.DiagramEditPart.activate(DiagramEditPart.java:349)
at org.eclipse.gef.editparts.AbstractEditPart.addChild(AbstractEditPart.java:215)
at org.eclipse.gef.editparts.SimpleRootEditPart.setContents(SimpleRootEditPart.java:105)
at org.eclipse.gef.ui.parts.AbstractEditPartViewer.setContents(AbstractEditPartViewer.java:617)
at org.eclipse.gmf.runtime.diagram.ui.parts.DiagramGraphicalViewer.setContents(DiagramGraphicalViewer.java:352)
at org.eclipse.gef.ui.parts.AbstractEditPartViewer.setContents(AbstractEditPartViewer.java:626)
at org.eclipse.gmf.runtime.diagram.ui.OffscreenEditPartFactory.createDiagramEditPart(OffscreenEditPartFactory.java:128)
at org.eclipse.gmf.runtime.diagram.ui.render.util.CopyToImageUtil.createDiagramEditPart(CopyToImageUtil.java:86)
at org.eclipse.gendoc.bundle.acceleo.gmf.impl.GMFDiagramRunnable$MultiElementsCopytoImageUtils.copyToImage(GMFDiagramRunnable.java:204)
at org.eclipse.gendoc.bundle.acceleo.gmf.impl.GMFDiagramRunnable.run(GMFDiagramRunnable.java:142)
at org.eclipse.gendoc.services.docx.DOCXAdditionalResourceService.addRunnableResourceToDocument(DOCXAdditionalResourceService.java:252)
at org.eclipse.gendoc.documents.AbstractImageService.getFilePath(AbstractImageService.java:36)
at org.eclipse.gendoc.tags.handlers.impl.scripts.ImageTagHandler.doRun(ImageTagHandler.java:62)
at org.eclipse.gendoc.tags.handlers.AbstractPrePostTagHandler.run(AbstractPrePostTagHandler.java:55)
at org.eclipse.gendoc.tags.handlers.AbstractTagHandler.runChildren(AbstractTagHandler.java:225)
at org.eclipse.gendoc.tags.handlers.AbstractTagHandler.run(AbstractTagHandler.java:130)
at org.eclipse.gendoc.tags.handlers.AbstractPrePostTagHandler.doRun(AbstractPrePostTagHandler.java:114)
at org.eclipse.gendoc.tags.handlers.AbstractPrePostTagHandler.run(AbstractPrePostTagHandler.java:55)
at org.eclipse.gendoc.tags.handlers.process.TagAnalyserProcess.executeOneTag(TagAnalyserProcess.java:226)
at org.eclipse.gendoc.tags.handlers.process.TagAnalyserProcess.executeTags(TagAnalyserProcess.java:204)
at org.eclipse.gendoc.tags.handlers.process.TagAnalyserProcess.executeAndInjectTags(TagAnalyserProcess.java:147)
at org.eclipse.gendoc.tags.handlers.process.TagAnalyserProcess.step(TagAnalyserProcess.java:138)
at org.eclipse.gendoc.process.AbstractStepProcess.doRun(AbstractStepProcess.java:51)
at org.eclipse.gendoc.process.AbstractProcess.run(AbstractProcess.java:72)
at org.eclipse.gendoc.GendocProcess.runProcess(GendocProcess.java:81)
at org.eclipse.gendoc.GendocProcess.runProcess(GendocProcess.java:140)
at org.eclipse.gendoc.batch.GendocBatchModeRunnableApplication.start(GendocBatchModeRunnableApplication.java:108)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
at org.eclipse.core.launcher.Main.main(Main.java:34)
Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1
Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1
Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1
Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1
Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1
Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1
Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1
Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1
Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1
Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1
Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.jdt.internal.ui.InitializeAfterLoadJob
Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1
Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1
Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1
Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1
Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1
Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1
Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1
Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1
Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1
Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1
Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1
Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1


Thanks a lot!

[Updated on: Fri, 08 April 2016 15:43]

Report message to a moderator

Re: Command line [message #1728954 is a reply to message #1728949] Fri, 08 April 2016 16:03 Go to previous messageGo to next message
Tristan Faure is currently offline Tristan FaureFriend
Messages: 460
Registered: July 2009
Senior Member
Does it work using GUI ?



Report message to a moderator

Re: Command line [message #1728962 is a reply to message #1728954] Fri, 08 April 2016 16:21 Go to previous messageGo to next message
Benajmin Schoenholzer is currently offline Benajmin SchoenholzerFriend
Messages: 33
Registered: March 2016
Member
Yes with right-clicking on file and choosing gendoc....

Report message to a moderator

Re: Command line [message #1729091 is a reply to message #1728962] Mon, 11 April 2016 07:05 Go to previous messageGo to next message
Tristan Faure is currently offline Tristan FaureFriend
Messages: 460
Registered: July 2009
Senior Member
Okay it is strange. Which version of Papyrus are you using ?

If you want we can see together what the problem is, you can contact me at this address :

tristan.faure(at)atos.net



Report message to a moderator

Re: Command line [message #1751388 is a reply to message #1729091] Mon, 09 January 2017 16:28 Go to previous messageGo to next message
Benajmin Schoenholzer is currently offline Benajmin SchoenholzerFriend
Messages: 33
Registered: March 2016
Member
I have a new issue with the gendoc 0.6 release. I am using gendoc by the command line and i am using also a own special profile. In the past i wrote the following in the template:

<param key='modelPath' value='platform:/resource/DevelopmentEnvironment/DevelopmentEnvironment.uml'/><drop/>


But now with the new release it doesn't work anymore. I didn't use the batch for a while, therefore i am so late with the issue. I received the following error:

Quote:
at org.eclipse.core.launcher.Main.main(Main.java:34)
at org.eclipse.equinox.launcher.Main.main(Main.java:1492)
at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.gendoc.batch.GendocBatchModeRunnableApplication.start(GendocBatchModeRunnableApplication.java:108)
at org.eclipse.gendoc.GendocProcess.runProcess(GendocProcess.java:140)
at org.eclipse.gendoc.GendocProcess.runProcess(GendocProcess.java:81)
at org.eclipse.gendoc.process.AbstractProcess.run(AbstractProcess.java:72)
at org.eclipse.gendoc.process.AbstractStepProcess.doRun(AbstractStepProcess.java:51)
at org.eclipse.gendoc.tags.handlers.process.TagAnalyserProcess.step(TagAnalyserProcess.java:138)
at org.eclipse.gendoc.tags.handlers.process.TagAnalyserProcess.executeAndInjectTags(TagAnalyserProcess.java:147)
at org.eclipse.gendoc.tags.handlers.process.TagAnalyserProcess.executeTags(TagAnalyserProcess.java:204)
at org.eclipse.gendoc.tags.handlers.process.TagAnalyserProcess.executeOneTag(TagAnalyserProcess.java:226)
at org.eclipse.gendoc.tags.handlers.AbstractPrePostTagHandler.run(AbstractPrePostTagHandler.java:55)
at org.eclipse.gendoc.tags.handlers.AbstractPrePostTagHandler.doRun(AbstractPrePostTagHandler.java:114)
at org.eclipse.gendoc.tags.handlers.AbstractTagHandler.run(AbstractTagHandler.java:120)
at org.eclipse.gendoc.tags.handlers.AbstractScriptTagHandler.runScripts(AbstractScriptTagHandler.java:59)
at org.eclipse.gendoc.tags.handlers.AbstractScriptTagHandler.runProcessorScript(AbstractScriptTagHandler.java:83)
at org.eclipse.gendoc.tags.handlers.impl.context.ContextService.getElement(ContextService.java:182)
at org.eclipse.gendoc.tags.handlers.impl.context.ContextService.getModel(ContextService.java:103)
at org.eclipse.gendoc.tags.handlers.impl.context.EMFModelLoaderService.getModel(EMFModelLoaderService.java:202)
org.eclipse.gendoc.services.exception.ModelNotFoundException: The model Model can not be loaded from URL: "platform:/resource/Deve
lopmentEnvironment/DevelopmentEnvironment.uml" can not be loaded log4j:WARN Please initialize the log4j system properly.
log4j:WARN No appenders could be found for logger (root).


It seems that this key is not valid anymore. Is there a new strategy?

I am using Papyrus Neon and Gendoc 0.6. The generation out of papyrus works fine.

Best regards
Benny

Report message to a moderator

Re: Command line [message #1751395 is a reply to message #1751388] Mon, 09 January 2017 17:07 Go to previous messageGo to next message
Tristan Faure is currently offline Tristan FaureFriend
Messages: 460
Registered: July 2009
Senior Member
Hello
do you have other stacktraces ? maybe it is because there are problems loading the profile.
As i understand the templates works fine using the IDE ?



Report message to a moderator

Re: Command line [message #1751442 is a reply to message #1751395] Tue, 10 January 2017 12:30 Go to previous messageGo to next message
Benajmin Schoenholzer is currently offline Benajmin SchoenholzerFriend
Messages: 33
Registered: March 2016
Member
Quote:
!SESSION 2017-01-10 13:24:18.104 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.8.0_31
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=de_CH
Framework arguments: -application org.eclipse.gendoc.batch.GendocBatchMode -idt dir=C:\Users\Benny\BFH\models\Model_AccumulatorProduction\doc\SystemSpecification_Template.docx
Command-line arguments: -application org.eclipse.gendoc.batch.GendocBatchMode -data C:\Users\Benny\PapyrusWorkspace -idt dir=C:\Users\Benny\BFH\models\Model_AccumulatorProduction\doc\SystemSpecification_Template.docx

!ENTRY org.eclipse.gendoc.services 2 2 2017-01-10 13:24:23.925
!MESSAGE variables can not be registered for file:/C:/Users/Benny/BFH/models/Model_AccumulatorProduction/doc/SystemSpecification_Template.docx

!ENTRY org.eclipse.gendoc.services 4 4 2017-01-10 13:24:30.089
!MESSAGE The execution of a script failed: The model Model can not be loaded from URL: "platform:/resource/AccumulatorProduction/AccumulatorProduction.uml" can not be loaded

!ENTRY org.eclipse.core.jobs 2 2 2017-01-10 13:24:31.298
!MESSAGE Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1

!ENTRY org.eclipse.core.jobs 2 2 2017-01-10 13:24:31.299
!MESSAGE Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1

!ENTRY org.eclipse.core.jobs 2 2 2017-01-10 13:24:31.301
!MESSAGE Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1

!ENTRY org.eclipse.core.jobs 2 2 2017-01-10 13:24:31.302
!MESSAGE Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1

!ENTRY org.eclipse.core.jobs 2 2 2017-01-10 13:24:31.302
!MESSAGE Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1

!ENTRY org.eclipse.core.jobs 2 2 2017-01-10 13:24:31.303
!MESSAGE Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1

!ENTRY org.eclipse.core.jobs 2 2 2017-01-10 13:24:31.304
!MESSAGE Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1

!ENTRY org.eclipse.core.jobs 2 2 2017-01-10 13:24:31.304
!MESSAGE Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1

!ENTRY org.eclipse.core.jobs 2 2 2017-01-10 13:24:31.305
!MESSAGE Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1

!ENTRY org.eclipse.core.jobs 2 2 2017-01-10 13:24:31.306
!MESSAGE Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1

!ENTRY org.eclipse.core.jobs 2 2 2017-01-10 13:24:31.306
!MESSAGE Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1

!ENTRY org.eclipse.core.jobs 2 2 2017-01-10 13:24:31.307
!MESSAGE Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1

!ENTRY org.eclipse.core.jobs 2 2 2017-01-10 13:24:31.308
!MESSAGE Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1

!ENTRY org.eclipse.core.jobs 2 2 2017-01-10 13:24:31.308
!MESSAGE Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1

!ENTRY org.eclipse.core.jobs 2 2 2017-01-10 13:24:31.309
!MESSAGE Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.jdt.internal.ui.InitializeAfterLoadJob

!ENTRY org.eclipse.core.jobs 2 2 2017-01-10 13:24:31.309
!MESSAGE Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1

!ENTRY org.eclipse.core.jobs 2 2 2017-01-10 13:24:31.309
!MESSAGE Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1

!ENTRY org.eclipse.core.jobs 2 2 2017-01-10 13:24:31.310
!MESSAGE Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1

!ENTRY org.eclipse.core.jobs 2 2 2017-01-10 13:24:31.310
!MESSAGE Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1

!ENTRY org.eclipse.core.jobs 2 2 2017-01-10 13:24:31.311
!MESSAGE Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1

!ENTRY org.eclipse.core.jobs 2 2 2017-01-10 13:24:31.312
!MESSAGE Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1

!ENTRY org.eclipse.core.jobs 2 2 2017-01-10 13:24:31.312
!MESSAGE Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1

!ENTRY org.eclipse.core.jobs 2 2 2017-01-10 13:24:31.313
!MESSAGE Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1


Yes out of the IDE it works and it worked also before....

What means the variables can not be registered? I think this could be the problem.

This is the config section of the template:
Quote:
<config><drop/>
<param key='modelPath' value='platform:/resource/AccumulatorProduction/AccumulatorProduction.uml'/><drop/>
<param key='contentElement' value='AccuPro/AccuPro_Kern'/><drop/>
<output path='${project_loc}/doc/documentation/SystemSpecification_AccuPro.docx'/><drop/>
</config><drop/>
<context model='${modelPath}' element='${contentElement}' importedBundles='gmf;papyrus;commons;gendocExtension' searchMetamodels='true'/><drop/>

Report message to a moderator

Re: Command line [message #1751675 is a reply to message #1751442] Thu, 12 January 2017 12:03 Go to previous messageGo to next message
Benajmin Schoenholzer is currently offline Benajmin SchoenholzerFriend
Messages: 33
Registered: March 2016
Member
I created a little example for my problem. I hope it helps to clear the questions. There is a profile (sysmod) and a test model. For executing the commandline i used the batch file in the root of the model.
Thanks for helping!

Best regards
Benny
  • Attachment: Example.zip
    (Size: 190.65KB, Downloaded 157 times)

Report message to a moderator

Re: Command line [message #1751878 is a reply to message #1751675] Mon, 16 January 2017 12:50 Go to previous messageGo to next message
Tristan Faure is currently offline Tristan FaureFriend
Messages: 460
Registered: July 2009
Senior Member
Hello
We will try with your project

did you try to set your variable in this way ? :
<param key='modelPath' value='${project_loc}/AccumulatorProduction.uml'/><drop/>



Report message to a moderator

Re: Command line [message #1751900 is a reply to message #1751878] Mon, 16 January 2017 16:37 Go to previous messageGo to next message
Benajmin Schoenholzer is currently offline Benajmin SchoenholzerFriend
Messages: 33
Registered: March 2016
Member
Thanks. Yes i tried, but it doesn't work. On my pc, the papyrusproject is not located in the workspace. I import the projects from a repositoryfolder into my workspace.

Best regards
Benny

Report message to a moderator

Re: Command line [message #1752051 is a reply to message #1751900] Wed, 18 January 2017 10:26 Go to previous messageGo to next message
Tristan Faure is currently offline Tristan FaureFriend
Messages: 460
Registered: July 2009
Senior Member
Hello
in your command line when you select data : C:\Users\Benny\PapyrusWorkspace
is it a real eclipse workspace ? did you try to set manually the full path of your document ? <param key='modelPath' value='c:/users/benny/somefolders/AccumulatorProduction.uml'/><drop/> ?



Report message to a moderator

Re: Command line [message #1752089 is a reply to message #1752051] Wed, 18 January 2017 17:09 Go to previous messageGo to next message
Benajmin Schoenholzer is currently offline Benajmin SchoenholzerFriend
Messages: 33
Registered: March 2016
Member
Yes, then it works. But i can not use the absolute path in the template, because i also use the generation on other workstations. I tried to use the properties file, but it seems, that the project_loc variable does not work in this case.

Report message to a moderator

Re: Command line [message #1752090 is a reply to message #1752089] Wed, 18 January 2017 17:29 Go to previous messageGo to next message
Tristan Faure is currently offline Tristan FaureFriend
Messages: 460
Registered: July 2009
Senior Member
Yes okay I understand

Actually if you use project_loc or paltform:/resource/ you need to Eclipse to recognize the workspace

can you try : ${workspace_loc}/PROJECT_NAME/AccumulatorProduction.uml ?



Report message to a moderator

Re: Command line [message #1752093 is a reply to message #1752090] Wed, 18 January 2017 17:48 Go to previous messageGo to next message
Benajmin Schoenholzer is currently offline Benajmin SchoenholzerFriend
Messages: 33
Registered: March 2016
Member
No i received the same error. Maybe this also not work, because the project is not physically located in the workspace.

Report message to a moderator

Re: Command line [message #1752095 is a reply to message #1752093] Wed, 18 January 2017 17:52 Go to previous messageGo to next message
Tristan Faure is currently offline Tristan FaureFriend
Messages: 460
Registered: July 2009
Senior Member
ah yes please set -data to the directory containing your project ?



Report message to a moderator

Re: Command line [message #1752100 is a reply to message #1752095] Wed, 18 January 2017 18:46 Go to previous messageGo to next message
Benajmin Schoenholzer is currently offline Benajmin SchoenholzerFriend
Messages: 33
Registered: March 2016
Member
No, it doen't work.....

Report message to a moderator

Re: Command line [message #1752143 is a reply to message #1752100] Thu, 19 January 2017 08:51 Go to previous messageGo to next message
Tristan Faure is currently offline Tristan FaureFriend
Messages: 460
Registered: July 2009
Senior Member
Can you set the full path of your model in the tag to make it work and can you write to this post the result of (to add in a gendoc section in the template):
[gGet('workspace_loc')/]
[gGet('input_directory')/]

?



Report message to a moderator

Re: Command line [message #1775149 is a reply to message #1752143] Wed, 25 October 2017 11:04 Go to previous messageGo to next message
Ursula Kirchgaessner is currently offline Ursula KirchgaessnerFriend
Messages: 18
Registered: July 2017
Junior Member
Hello,

did you solve the problem discussed in this thread? It seems I have the same issue: document generation from generic_template.docx works fine with the wizard, but not with the command line.

Some detail:
Papyrus 2.0.2 with SysML 1.4 Feature 0.10.1 and Acceleo 3.6.6
The document is created in both cases (wizard and command line), but using the command line, the diagrams are not included, the document is empty.

It seems to be a problem related to the diagrams, since I added a paragraph to list the packages:
[for (p:Package|self.ownedElement->filter(Package)->sortedBy(name))] <drop/>
[p.name/]
[/for]
and the packages are listed perfectly in the generated document.

However, the console returns the following messages every time:

log4j:WARN No appenders could be found for logger (root).
log4j:WARN Please initialize the log4j system properly.
Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1
Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.activities.MutableActivityManager$3$1
...

Can you help me with this?
Best regards,
Ursula

Report message to a moderator

Re: Command line [message #1775220 is a reply to message #1775149] Thu, 26 October 2017 12:48 Go to previous messageGo to next message
Ursula Kirchgaessner is currently offline Ursula KirchgaessnerFriend
Messages: 18
Registered: July 2017
Junior Member
Hello again,

I found a work-around for the diagrams: I change the context to use the *.notation file instead of *.uml. I suppose using "notation::Diagram" as done in the template should have the same effect as using the *.notation file in <context>. Do you have any idea why this does not work from the command line when it works perfectly from the GUI?

Thanks for any hint!
Best regards,
Ursula

Report message to a moderator

Re: Command line [message #1777938 is a reply to message #1775220] Wed, 06 December 2017 12:30 Go to previous message
Tristan Faure is currently offline Tristan FaureFriend
Messages: 460
Registered: July 2009
Senior Member
Hello
Sometimes commandline does not work properly if you don't write correctly the path of your model or if the workspace is not well set in the command line. Can you copy paste the beginning of your path ?



Report message to a moderator

Previous Topic:CleanAndFormat() does not work as expected
Next Topic:Behavior diagrams missing in generated document
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ]

Current Time: Fri Nov 08 23:09:10 GMT 2024

Powered by FUDForum. Page generated in 0.05801 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top

Sign up to our Newsletter

A fresh new issue delivered monthly