adobe-consulting-services / aem-epic-tool Goto Github PK

I would like the ability to download packages from an environment and analyze them offline later when I might night have access to the target environment.

The user should be able to trigger this report from the main package view via the hamburger menu:

• Run report for all packages in list
• Run report for all packages selected (multi-select should be enabled for this to work); This option should be disabled if fewer than 2 packages are selected.

The report should contain:

• Report summary tab including a KEY mapping each package to a letter indicated in the other tabs, should also have all other report information available in the list view such as version number, unpack date, etc
• Root folder summary including all packages and number of files in each location (roll-up report)
• Type summary including all packages and number of files by type (roll-up report)
• Tab indicating all common files (unchanged) between 2 or more packages. Each package having the same file contents should indicate an X that it has that file or blank if it doesn't.
• Tab indicating all overlapping files (changed) between 2 or more packages; columns for each package having that file should indicate revision number which is assigned such that 1 is the earliest revision encountered, etc.

It is generally assumed that most packages will have mostly unique contents so unlike the comparison report between versions, there will be no listing of unique files per package.

Hamburger button makes the checkboxes in the package view unclickable

It would be more user-friendly if reports were pre-formatted as follows:

1. freeze header row (and also leftmost column for some reports)
2. Alternate colors every other column
3. Enable gridlines by default
4. Adjust column width to reasonable defaults where possible

As an ops person I would like to connect to multiple environments and compare packages across the environments to see if they're the same. I would also like to compare version installation order to see if everything matches.

When a file is not downloaded correctly, the application should offer to retry and not require restarting to recover from it.

If there are more than 26 packages in the master report, it starts using characters like [ and ] instead of letters. It might be a good idea to follow an excel-like convention, e.g. AA, AB, AC, etc...

In comparison and package analysis views, all download views should offer a cancel action as well. Download logic should accept an atomic boolean property for cancellation and check it regularly as needed.

Seems like an int / long mismatch somewhere caused packages to appear with negative sizes when they were up in the 2-3 TB size. As these large sizes are rare, it doesn't happen often.

I'm getting this error when running "mvn install":

[ERROR] File [C:\Users\daniel.hernandez\Documents\daniel\aem-epic-tool\src\main\resources\jaxb\catalog.xml] does not exist.

I'm building with java 8 and maven 3.5.2.

Provide a UI which allows viewing a comparison report. This would include:

• Download status for packages
• View of same information shown in report tabs, using accordion for each section of report and table view for each set of information
• Hamburger menu for providing additional actions such as export to Excel

When i am trying to build from Master i get the below compilation error :

#########################
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.6.1:compile (default-compile) on project aem-epic: Compilation failure
[ERROR] /C:/AEM/ACS/aem-epic/aem-epic-tool/src/main/java/com/adobe/acs/epic/util/ReportUtil.java:[84,28] cannot access org.openxmlformats.schemas.spreadsheetml.x2006.main.CTColor
[ERROR] class file for org.openxmlformats.schemas.spreadsheetml.x2006.main.CTColor not found
########################

This is due to incorrect/missing dependency in parent POM.

Add this one and Build finishes successfully :

<dependency> <groupId>org.apache.poi</groupId> <artifactId>ooxml-schemas</artifactId> <version>1.3</version> </dependency>

Let me know if i missed anything here.