Products Downloads


French version


Comparaison des versions

Légende

  • Ces lignes ont été ajoutées. Ce mot a été ajouté.
  • Ces lignes ont été supprimées. Ce mot a été supprimé.
  • La mise en forme a été modifiée.

...

The Windows Visual Server application and Adelia build machine may be two different machines.

Hardis - Haut de page

Top of page

Configuring an Adelia Windows Server build project

...

The value follows the same naming rules as Java packages (e.g. com.hardis), and the name of the project's top package is generally chosen as a value.


Hardis - Haut de page

Top of page

General parameters for the application installer

...

    • license_default_locale.txt placed at the project root and localized with the default locale
    • license_fr_FR.txt placed in the 'fr' sub-directory and localized with the 'fr-FR' locale
    • license_it_IT.txt placed in the 'it' sub-directory and localized with the 'it-IT' locale


Hardis - Haut de page

Top of page

Extended parameters for the MSI installer

...

Bloc de code
languagegroovy
titlemsi.languages
["en-US", "de-DE", "fr-FR"]
Hardis - Haut de page

Top of page

Repository manager settings

...

By default, Nexus enables the deployment profile (username and password set to the "deployment" value) to be used.

Hardis - Haut de page

Top of page

Configuring the components of the Adelia Windows Server application to build

...

The 'othersResourcesConf' configuration must first be declared in the 'configurations' closure (declaration to uncomment). The artifact content will be inserted into the application in the 'setupBuilder' closure: this content can either be added at the application root or in a sub-directory (code to uncomment).


Hardis - Haut de page

Top of page

Configuring the shortcuts of the Adelia Windows Server application to build

...

  1. Create a .properties file for each supported language (e.g. shortcut_fr_FR.properties, shortcut_en_US.properties) at the build project root,
  2. For each file, add an entry (syntax key = value) with the same key name and for each key, the text of the translated shortcut (e.g. In shortcut_fr_FR.properties, add my_key_shortcut_launch=My application and in shortcut_en_US.properties, add my_key_shortcut_launch=My application)
  3. In the 'desktopStarter' closure, set the '!(loc.my_key_shortcut_launch)' (displayName='!(loc.my_key_shortcut_launch)') string as the "displayName" property
  4. In the "msi" closure, associate the .properties resource files as well as their language:

    Bloc de code
    languagegroovy
    titlemsi closure
    msi {
    	i18n {
            // set locale
            locale = "fr-FR"
            
            // set the localization resource filename (relative to root project directory)
            resource = "shortcut_fr_FR.properties"        
        }
    	i18n {
            // set locale
            locale = "en-US"
            
            // set the localization resource filename (relative to root project directory)
            resource = "shortcut_en_US.properties"        
        }
    }
    Hardis - Haut de page

    Top of page

Configuration files for the Adelia Windows Server application to build

...

This task transfers the built artifacts (by calling the msi and/or zipApp tasks) to the repository local to the build machine (local repository in %USERPROFILE%\.m2 directory).

Hardis - Haut de page

Top of page

MSI installation assistant

...

msiexec /i mynewapp-1.0.0-SNAPSHOT.msi /quiet INSTALLDIR=C:\testInstall



Hardis - Haut de page

Top of page