Html generation using command line

Hi,
Could you please check with this version of
Capella
Best regards,
Boubekeur Zendagui.

Hello
I tried with this version and with below command line.
“C:/Software-dev/zip files/capella-1.2.1/capella/eclipse/eclipse.exe” -nosplash -application org.polarsys.capella.core.commandline.core -appid org.polarsys.kitalpha.doc.gen.business.capella.commandline -data …/capella1.2.1wp1 -filepath /test/test.aird -outputfolder /DocProject4/HTML -forceoutputfoldercreation -logfile “C:/Software-dev/workspaces/capella1.2.1wp1/logfile.html” -logconsole
I only get a empty output folder in /DocProject4/HTML
I used this option (-logconsole) to see the error in the command window. I dont see any output in this window either.
The html files is generating properly using eclipse gui.
Regards
Arun

Hello
The bug logged in this thread is set a FIXED in version 1.2.1
But I have the below error while executing the command line for html generation in version 1.2.1
log4j:WARN No appenders could be found for logger (org.polarsys.capella.common.mdsofa.common.helper).
log4j:WARN Please initialize the log4j system properly.
!SESSION 2018-08-10 11:17:25.035 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.8.0_121
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
Framework arguments: -application org.polarsys.capella.core.commandline.core -appid org.polarsys.kitalpha.doc.gen.business.capella.commandline -filepath /AMODS.team/AMODS.team.aird -outputfolder F:\workspaces\docgen -forceoutputfoldercreation -logfile F:\log1.html
Command-line arguments: -os win32 -ws win32 -arch x86_64 -application org.polarsys.capella.core.commandline.core -appid org.polarsys.kitalpha.doc.gen.business.capella.commandline -data …\team1.2.1wp1 -filepath /AMODS.team/AMODS.team.aird -outputfolder F:\workspaces\docgen -forceoutputfoldercreation -logfile F:\log1.html -consolelog
!ENTRY org.eclipse.core.resources 2 10035 2018-08-10 11:17:26.902
!MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes.
08-10 11:17:30 INFO F:\workspaces\docgen already exist.
08-10 11:17:44 INFO UsageMonitoring [applicationName=Capella, applicationVersion=1.2.1.201806011020, eventName=Connect to Remote Project, eventContext=AMODS.team.aird, eventStatus=, addendum=TCP]
08-10 11:17:45 INFO UsageMonitoring [applicationName=Capella, applicationVersion=1.2.1.201806011020, eventName=Connect to Remote Project, eventContext=AMODS.team.aird, eventStatus=OK, addendum=TCP]
!ENTRY com.thalesgroup.mde.melody.collab.ui 1 0 2018-08-10 11:17:46.364
!MESSAGE Team for Capella -> SESSION OPENING:Local Session: platform:/resource//AMODS.team/AMODS.team.aird
!ENTRY com.thalesgroup.mde.melody.collab.ui 1 0 2018-08-10 11:17:46.364
!MESSAGE Team for Capella -> SESSION OPENING
!ENTRY com.thalesgroup.mde.melody.collab.ui 1 0 2018-08-10 11:17:50.785
!MESSAGE Team for Capella -> SESSION OPENED:Local Session: platform:/resource//AMODS.team/AMODS.team.aird
!ENTRY org.eclipse.egf.pattern 4 0 2018-08-10 11:17:51.037
!MESSAGE
!STACK 0
org.eclipse.egf.core.producer.InvocationException
at org.eclipse.egf.producer.internal.manager.FactoryComponentMa nager.invoke(FactoryComponentManager.java:138)
at org.polarsys.kitalpha.doc.gen.business.core.ui.helper.Invoke ActivityHelper$1$1.run(InvokeActivityHelper.java:102)
at org.eclipse.jface.operation.ModalContext.runInCurrentThread( ModalContext.java:437)
at org.eclipse.jface.operation.ModalContext.run(ModalContext.ja va:353)
at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(Progress MonitorDialog.java:481)
at org.eclipse.ui.internal.progress.ProgressMonitorJobsDialog.r un(ProgressMonitorJobsDialog.java:242)
at org.eclipse.ui.internal.progress.ProgressManager$3.run(Progr essManager.java:895)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator .java:70)
at org.eclipse.ui.internal.progress.ProgressManager.busyCursorW hile(ProgressManager.java:930)
at org.eclipse.ui.internal.progress.ProgressManager.busyCursorW hile(ProgressManager.java:905)
at org.polarsys.kitalpha.doc.gen.business.core.ui.helper.Invoke ActivityHelper$1.run(InvokeActivityHelper.java:92)
at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.j ava:233)
at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchroniz er.java:145)
at org.eclipse.swt.widgets.Display.syncExec(Display.java:4821)
at org.polarsys.kitalpha.doc.gen.business.core.ui.helper.Invoke ActivityHelper.invokeOutOfUIThread(InvokeActivityHelper.java :89)
at org.polarsys.capella.docgen.commandline.HTMLCommandLine.exec uteEGFActivity(HTMLCommandLine.java:175)
at org.polarsys.capella.docgen.commandline.HTMLCommandLine.exec ute(HTMLCommandLine.java:104)
at org.polarsys.capella.core.commandline.core.CommandLineApp.la unchApp(CommandLineApp.java:136)
at org.polarsys.capella.core.commandline.core.CommandLineApp.st art(CommandLineApp.java:70)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.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(EclipseS tarter.java:388)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:243)
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: 673)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
Caused by: org.eclipse.egf.domain.DomainException: java.lang.NullPointerException
at org.polarsys.capella.docgen.ui.domain.CapellaDomainHelper.do LoadDomain(CapellaDomainHelper.java:91)
at org.eclipse.egf.domain.LoadableDomainHelper.loadDomain(Loada bleDomainHelper.java:38)
at org.eclipse.egf.domain.IDomainHelper$Helper.loadDomains(IDom ainHelper.java:46)
at org.eclipse.egf.producer.internal.manager.FactoryComponentMa nager.invoke(FactoryComponentManager.java:132)
… 30 more
Caused by: java.lang.NullPointerException
at org.polarsys.capella.docgen.ui.domain.CapellaDomainHelper.do LoadDomain(CapellaDomainHelper.java:89)
… 33 more
08-10 11:17:51 INFO HTML generation done!
files generated to F:\workspaces\docgen

Hi,
Are you using Team For Capella (T4C)? Because it indeed seems that there is a problem with T4C.We have no visibility on when this will be fixed for T4C.

Hi Arun, Boubekeur and Stephane,
It seems that the command line launcher is not currently able to open/load a shared project.
I think it might come from the fact that the HTML generator is not aware of the authentification/credentials needs when launched from the command line.
There might be a workaround with the secure storage (except if its scope depends on the -application arg): if the login/password are stored in the secure storage for the current user it might success to open the connection to the shared project.
Arun, could you create a bug on your Team for Capella bug tracker ?
Regards,
Maxime

Hi Arun,
In Team for Capella, you could also try to modify the Import job and launch the HTML generation on the imported project as additional task.
Regards

Hi Arun,
in fact, this is a known issue (Bug 1513 “Generation HTML in command line can use .afm file”): it has been fixed in the latest html addon 1.1 for Capella 1.1.
A new version of this addon (1.2.1) will be available soon in order to fix #1513 for Capella 1.2 (filesystem models).
Best regards,
Michel

Thank you for your responses. In fact, regarding previous messages, I am having the issue with local models also (not only for shared models in T4C).
I will wait for 1.2.1 version of this addon.
Best Regards
Arun

Copyright © Eclipse Capella, the Eclipse Capella logo, Eclipse and the Eclipse logo are Trademarks of The Eclipse Foundation.