|Re: Content in ResourceCreationTask getting mangled on save [message #1830223 is a reply to message #1830206]
||Tue, 21 July 2020 07:02
| Ed Merks
Registered: July 2009
The self-extracting eclipse-inst-win64.exe itself handles command line arguments so likely you can launch it and specify what you need on the command line without a more complicated procedure.|
The arguments may start with --debug; this is stripped off and produces trace information about how the extractor is extracting the components. The first argument can be -vm <location> ; this too is stripped off and that location is then used as the JVM. After that, all the arguments are passed to the product/application and all of the following applies:
So you should, for example, be able to run eclipse-inst-win64.exe -name "PCI Eclipse Standard Tools Installer-eclipse.password" C:\PCI_Dev\source\SVN\ProjectEngineering\StandardTools\eclipse\config-gsms\master.key -vmargs -Dfoo=bar
Of course if you're repackaging this and wanting to redistribute a modified installer, that doesn't help so much...
It's still strange though because I don't see any significant changes in how the value is deserialized in BaseResourceImpl. But now that I say that, if the resource is loaded by an older version of the Setup model, one where the type of ResourceCreationTask.content is still EString and not Text, then the special handling doesn't kick in and the value, including the initial blank line and indentation, will be loaded. That must be what's happening...
Note that in advanced mode on the Configuration page, you can review the details of each and every task. So you can inspect the contents of the creation task to see if that already looks wrong; double click an attribute value to see the value in a dialog.
Professional Support: https://www.macromodeling.com/
Powered by FUDForum
. Page generated in 0.02479 seconds