You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+7-9Lines changed: 7 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,12 +13,14 @@ When you select e.g. a page for inclusion into package, all the assets reference
13
13
14
14
### Project structure
15
15
16
-
The project consists of two modules:
16
+
The project is organized as a multi-module Maven build:
17
17
18
-
**core module* runs in an AEM instance containing to respond to user commands and provide data processing service.
19
-
**ui/application module* embeds into AEM administering interface and runs in browser to give to the user control over package creation and storage, as well as detailed feedback. This module is built upon the modern Coral 3 graphic interface and TouchUI-ready.
18
+
*`core` — the server-side OSGi bundle. It contains the Java code that implements BackPack services, request processing, package handling logic, and tests.
19
+
*`ui.apps` — the AEM application package. It contains the repository content installed under the application area, including the UI assets and browser-facing integration.
20
+
*`ui.apps.structure` — the repository structure package. It defines the AEM repository roots required by the application packages.
21
+
*`ui.config` — the AEM configuration package. It contains configuration content packaged separately from the application code.
22
+
*`all` — the aggregate container package. It embeds the `core`, `ui.apps`, and `ui.config` artifacts into a single package for deployment.
20
23
21
-
The two modules communicate via JSON-based REST protocol. Basically, a user command is sent to an endpoint, parsed and processed by a specially designed AEM service, then result and/or status message returned to user.
22
24
23
25
### Installation
24
26
@@ -57,10 +59,6 @@ There is also the specific "test" profile that helps to collect code quality sta
57
59
58
60
The project is in active development stage. Community contribution is heartily welcome.
59
61
60
-
### Known issues
61
-
62
-
The project uses `com.google.common.cache.Cache` bundled in `uber-jar-6.3.0` which is in "beta" status. Despite this class is out of beta stage in standalone Google Guava releases since *20.0*, we are currently sticking to *uber-jar* version to avoid inconsistency. We have tested this doesn't cause trouble in regular usage.
63
-
64
62
### Licensing
65
63
66
-
The project is licensed under [Apache License, Version 2.0](LICENSE). All runtime project dependencies are guaranteed to be compliant with the license. Dependencies such as Adobe's *uber-jar* are considered *provided* in the end-user environment and are not explicitly engaged. The end user is to comply with the regulations of the corresponding licenses.
64
+
The project is licensed under [Apache License, Version 2.0](LICENSE). All runtime project dependencies are guaranteed to be compliant with the license. Dependencies such as Adobe's *uber-jar* are considered *provided* in the end-user environment and are not explicitly engaged. The end user is to comply with the regulations of the corresponding licenses.
@@ -197,7 +196,7 @@ public PackageInfo buildPackage(final ResourceResolver resourceResolver,
197
196
if (!PackageStatus.BUILD_IN_PROGRESS.equals(packageInfo.getPackageStatus()) && !PackageStatus.INSTALL_IN_PROGRESS.equals(packageInfo.getPackageStatus())) {
0 commit comments