user-guide:export-as-lib
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
user-guide:export-as-lib [2025/04/02 16:28] – [Compiled resources] gaetan | user-guide:export-as-lib [2025/05/27 00:25] (current) – barley1965 | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Project as Library ====== | + | ====== Project as a Module |
- | Project | + | A project |
These libraries are called module lib. | These libraries are called module lib. | ||
Line 9: | Line 9: | ||
===== Structure ===== | ===== Structure ===== | ||
- | Module lib follow | + | Module lib follows |
Line 20: | Line 20: | ||
===== Compiled classes ===== | ===== Compiled classes ===== | ||
+ | The classes in the project are exported compiled. | ||
==== Package name ==== | ==== Package name ==== | ||
+ | By default, .rgg types are compiled without a package. It makes them all visible from the same pool. However, to ensure uniqueness when importing module library, a package name is required during the export. GroIMP will use the given package name as default package during the compilation. | ||
+ | |||
+ | Thus, if the project contains types with the named package, they will not be affected by the package name provided. | ||
+ | |||
+ | The package name must follow java's specification on package names. | ||
==== Reference wrapper ==== | ==== Reference wrapper ==== | ||
+ | GroIMP implicitly wraps all references call in the project to be exported as a module library to make them use the resources from the library. | ||
+ | |||
+ | Suppose we have a project that contains a resource with the name " | ||
+ | |||
+ | The wrappers force the references to point at '' |
user-guide/export-as-lib.1743604109.txt.gz · Last modified: 2025/04/02 16:28 by gaetan