Globalyzer Lite - Revision history

Olibouban: /* Language Support */

2025-02-12T21:49:41Z

Language Support

← Older revision		Revision as of 21:49, 12 February 2025
Line 289:		Line 289:
	* Perl,		* Perl,
	* PHP,		* PHP,
	* Qt,		* QT C++,
	* SQL (Oracle, MS SQL, MySQL, PostgreSQL),		* SQL (Oracle, MS SQL, MySQL, PostgreSQL),
	* Visual Basic (Classic, .NET),		* Visual Basic (Classic, .NET),

Olibouban: /* Sharing Project Definition Files Between IDEs and Build Systems */

2022-02-22T15:20:16Z

Sharing Project Definition Files Between IDEs and Build Systems

← Older revision		Revision as of 15:20, 22 February 2022
Line 72:		Line 72:
	The build system can then be set to auto-replace "ScanDetailedCSV" with "ScanDetailedXML". The following Linux command will do so:		The build system can then be set to auto-replace "ScanDetailedCSV" with "ScanDetailedXML". The following Linux command will do so:

	<code>$ sed --in-place 's\|ScanDetailedCSV\|ScanDetailedXML\|' $WORKSPACE/~~ProjectDefinition~~.xml</code>		<code>$ sed --in-place 's\|ScanDetailedCSV\|ScanDetailedXML\|' $WORKSPACE/lingoport/LiteProjectDefinition.xml</code>

	If desired, the opposite replacement also may be performed at the end of the build.		If desired, the opposite replacement also may be performed at the end of the build.

Olibouban: /* Using Globalyzer Lite from the Command Prompt / Shell */

2022-02-22T15:19:44Z

Using Globalyzer Lite from the Command Prompt / Shell

← Older revision		Revision as of 15:19, 22 February 2022
Line 43:		Line 43:

	<code>java -jar globalyzer-lite.jar some_location/YourProjectDefinitionFile.xml</code>		<code>java -jar globalyzer-lite.jar some_location/YourProjectDefinitionFile.xml</code>

			It is strongly recommended to keep the definition under a repository top level directory 'lingoport' with the name 'LiteProjectDefinition.xml':

			<code>java -jar globalyzer-lite.jar lingoport/LiteProjectDefinition.xml</code>

	After lite finishes each scan, a relevant Globalyzer report is created at the location specified in the Project Definition's report path.		After lite finishes each scan, a relevant Globalyzer report is created at the location specified in the Project Definition's report path.

Olibouban: /* Using Globalyzer Lite in a Continuous Globalization System */

2022-02-22T15:17:57Z

Using Globalyzer Lite in a Continuous Globalization System

← Older revision		Revision as of 15:17, 22 February 2022
Line 33:		Line 33:
	# Check in a project definition file into source control (or, if you prefer, place one in the Jenkins server's filesystem).		# Check in a project definition file into source control (or, if you prefer, place one in the Jenkins server's filesystem).
	# Run the following from Jenkins' shell:		# Run the following from Jenkins' shell:
	#:<code>java -jar globalyzer-lite.jar -f "${WORKSPACE}/~~GlobalyzerProjectDefinitionFile~~.xml" --project-path "${WORKSPACE}" --report-path "globalyzer-lite-reports"</code>		#:<code>java -jar globalyzer-lite.jar -f "${WORKSPACE}/lingoport/LiteProjectDefinitionFile.xml" --project-path "${WORKSPACE}" --report-path "globalyzer-lite-reports"</code>
	# Use the Lingoport Dashboard to display the results from the generated reports.		# Use the Lingoport Dashboard to display the results from the generated reports.

Masnes: /* Language Support */

2020-01-10T20:50:16Z

Language Support

← Older revision		Revision as of 20:50, 10 January 2020
Line 280:		Line 280:
	* HTML (in various web files),		* HTML (in various web files),
	* Java,		* Java,
	* JavaScript, (includes AngularJS, NodeJS, and other libraries)		* JavaScript, (includes AngularJS, NodeJS, React, and other libraries)
	* Objective-C,		* Objective-C,
	* MXML,		* MXML,

MaryH: /* Project Definition Format */

2018-08-06T21:23:52Z

Project Definition Format

← Older revision		Revision as of 21:23, 6 August 2018
Line 138:		Line 138:
	<report-path></report-path> <!-- May instead be specified from command line -->		<report-path></report-path> <!-- May instead be specified from command line -->
	<report-type></report-type>		<report-type></report-type>
	<data-dictionary-location></data-dictionary-location> <!-- optional -->		<data-dictionary-location></data-dictionary-location> <!-- optional -->
	<filter-with-dictionary></filter-with-dictionary> <!-- optional. May be 'true' or 'false' -->		<filter-with-dictionary></filter-with-dictionary> <!-- optional. May be 'true' or 'false' -->
	<scan-timeout>500</scan-timeout> <!-- optional. Max value 600 (seconds) -->		<scan-timeout>500</scan-timeout> <!-- optional. Max value 600 (seconds) -->
	<generate-partial-results></generate-partial-results> <!-- optional. May be 'true' or 'false' -->		<generate-partial-results></generate-partial-results> <!-- optional. May be 'true' or 'false' -->
	<save-history></save-history> <!-- optional. May be 'true' or 'false' -->		<save-history></save-history> <!-- optional. May be 'true' or 'false' -->
	<scans>		<scans>
	<scan>		<scan>
Line 155:		Line 155:
	<ruleset-name></ruleset-name>		<ruleset-name></ruleset-name>
	<ruleset-owner></ruleset-owner>		<ruleset-owner></ruleset-owner>
	<use-machine-learning>true</use-machine-learning> <!-- optional. May be 'true' or 'false' -->		<use-machine-learning>true</use-machine-learning> <!-- optional. May be 'true' or 'false' -->
	<encoding>UTF-8</encoding> <!-- optional. Encoding of files to scan -->		<encoding>UTF-8</encoding> <!-- optional. Encoding of files to scan -->
	<!-- optional: specify files/directories to scan -->		<!-- optional: specify files/directories to scan -->
	<scan-items>		<scan-items>
Line 162:		Line 162:
	<item></item>		<item></item>
	</scan-items>		</scan-items>
	<!-- optional -->		<!-- optional -->
	<comments>		<comments>
	<!-- customize Globalyzer recognized comments -->		<!-- customize Globalyzer recognized comments -->
	<todo>SPECIAL_GLOBALYZER_TODO_COMMENT</todo>		<todo>SPECIAL_GLOBALYZER_TODO_COMMENT</todo>
	<ignore-next-line>GBLYZR_IGNORE_NEXT_LINE</ignore-next-line>		<ignore-next-line>GBLYZR_IGNORE_NEXT_LINE</ignore-next-line>
Line 170:		Line 170:
	<end-ignore>GBL_END_IGNORE</end-ignore>		<end-ignore>GBL_END_IGNORE</end-ignore>
	</comments>		</comments>
	<!-- optional -->		<!-- optional -->
	<checks>		<checks>
	<!-- specify which issue types to detect -->		<!-- specify which issue types to detect -->
	<embedded-strings>true</embedded-strings>		<embedded-strings>true</embedded-strings>
	<locale-sensitive-methods>false</locale-sensitive-methods>		<locale-sensitive-methods>false</locale-sensitive-methods>

MaryH: /* Project Definition Format */

2018-08-06T21:22:07Z

Project Definition Format

← Older revision		Revision as of 21:22, 6 August 2018
Line 143:		Line 143:
	<generate-partial-results></generate-partial-results> <!-- optional. May be 'true' or 'false' -->		<generate-partial-results></generate-partial-results> <!-- optional. May be 'true' or 'false' -->
	<save-history></save-history> <!-- optional. May be 'true' or 'false' -->		<save-history></save-history> <!-- optional. May be 'true' or 'false' -->

	<scans>		<scans>
	<scan>		<scan>

MaryH: /* Project Definition Format */

2018-08-06T21:21:49Z

Project Definition Format

← Older revision		Revision as of 21:21, 6 August 2018
Line 138:		Line 138:
	<report-path></report-path> <!-- May instead be specified from command line -->		<report-path></report-path> <!-- May instead be specified from command line -->
	<report-type></report-type>		<report-type></report-type>

	<data-dictionary-location></data-dictionary-location> <!-- optional -->		<data-dictionary-location></data-dictionary-location> <!-- optional -->
	<filter-with-dictionary></filter-with-dictionary> <!-- optional. May be 'true' or 'false' -->		<filter-with-dictionary></filter-with-dictionary> <!-- optional. May be 'true' or 'false' -->
Line 157:		Line 156:
	<ruleset-name></ruleset-name>		<ruleset-name></ruleset-name>
	<ruleset-owner></ruleset-owner>		<ruleset-owner></ruleset-owner>

	<use-machine-learning>true</use-machine-learning> <!-- optional. May be 'true' or 'false' -->		<use-machine-learning>true</use-machine-learning> <!-- optional. May be 'true' or 'false' -->
	<encoding>UTF-8</encoding> <!-- optional. Encoding of files to scan -->		<encoding>UTF-8</encoding> <!-- optional. Encoding of files to scan -->

	<!-- optional: specify files/directories to scan -->		<!-- optional: specify files/directories to scan -->
	<scan-items>		<scan-items>
Line 166:		Line 163:
	<item></item>		<item></item>
	</scan-items>		</scan-items>

	<!-- optional -->		<!-- optional -->
	<comments>		<comments>
Line 175:		Line 171:
	<end-ignore>GBL_END_IGNORE</end-ignore>		<end-ignore>GBL_END_IGNORE</end-ignore>
	</comments>		</comments>

	<!-- optional -->		<!-- optional -->
	<checks>		<checks>

MaryH: /* Project Definition Format */

2018-08-06T21:19:47Z

Project Definition Format

@@ Line 138: / Line 138: @@
       <report-path></report-path>   &lt;!-- May instead be specified from command line --&gt;
       <report-type></report-type>
       <scans>
          <scan>
@@ Line 146: / Line 153: @@
          </scan>
          <scan>
-        &lt;!-- create and execute a single scan with this info -->
+           &lt;!-- create and execute a single scan with this info -->
             <scan-name></scan-name>
             <ruleset-name></ruleset-name>
             <ruleset-owner></ruleset-owner>
             &lt;!-- optional: specify files/directories to scan -->
             <scan-items>
@@ Line 155: / Line 166: @@
                <item></item>
             </scan-items>
          </scan>
       </scans>

MaryH: /* Using Globalyzer Lite from an Integrated Development Environment */

2018-05-09T18:33:09Z

Using Globalyzer Lite from an Integrated Development Environment

← Older revision		Revision as of 18:33, 9 May 2018
Line 9:		Line 9:
	== Using Globalyzer Lite from an Integrated Development Environment ==		== Using Globalyzer Lite from an Integrated Development Environment ==

	Lite may be used within many IDEs that support external tools, including Visual Studio, IntelliJ IDEA, and Eclipse. Configuring Lite as an external tool takes some initial setup, but is relatively easy to accomplish. Once configured, Lite may be used through the IDE's external tool menu, with the click of a button. The recommended, documented tools:		Lite may be used within many IDEs that support external tools, including Visual Studio, IntelliJ IDEA, and Eclipse. Configuring Lite as an external tool takes some initial setup, but is relatively easy to accomplish. Once configured, Lite may be used through the IDE's external tool menu with the click of a button. The recommended, documented tools:

	# Scan the currently selected file/directory.		# Scan the currently selected file/directory.