Đang chuẩn bị liên kết để tải về tài liệu:
Bắt đầu với IBM Websphere smash - p 10

72 Chapter 4 Configuration Files Explained Table 4.3 Versi on 1.0.x 1.1.x Latest Remote Zero Repositories Module Group Name stable stable experimental URL https://www.projectzero.org/sMash/1.0.x/repo/ https://www.projectzero.org/sMash/1.1.x/repo/ https://www.projectzero.org/zero/monza/latest/repo/ The default Maven repository is located at the following: http://repo1.maven.org/maven2/ To see information about your current local repository, such as its location on your local file system and which module groups are available, you can execute the following from the WebSphere sMash CLI directory: zero repository info This command will also tell you which module group is currently being used by the CLI. The CLI can only use one module group at a time. Any CLI commands will execute from modules in the. | 72 Chapter 4 Configuration Files Explained Table 4.3 Remote Zero Repositories Versi on Module Group Name URL 1.0.x stable https www.projectzero.Org sMash 1.0.x repo 1.1.x stable https www.projectzero.Org sMash 1.1.x repo Latest experimental https www.projectzero.org zero monza latest repo The default Maven repository is located at the following http repo1.maven.org maven2 To see information about your current local repository such as its location on your local file system and which module groups are available you can execute the following from the WebSphere sMash CLI directory zero repository info This command will also tell you which module group is currently being used by the CLI. The CLI can only use one module group at a time. Any CLI commands will execute from modules in the currently active module group. Likewise any applications created will be created using modules from the currently active module group. To see which module group an application is using you can execute the following command from the application s directory zero modulegroup info You can see which specific modules a module group contains by executing the following zero modulegroup list If you want to use multiple module groups for different versions of your application such as a stable and experimental version you must make sure your CLI is pointing to the correct module group. You must switch the CLI to use the new module group zero modulegroup switch modulegroupname After switching the command line you can create the application using the create command. You can also use the modulegroup switch command from within an application s directory to switch the application to a new module group. In this case the application will be resolved again against the new module group. You will probably need to run zero update to pick up compatible versions of modules from the new module group. NOTE The preceding instructions apply to CLI users. If you are using App Builder module group switching is handled