2.2.10
Resolved Issues
| Customer Ticket Id | Details |
|---|---|
| 39121 | Fixesa an issue, where post upgrade Java analysis unit was excluded by DMT. After the fix, Java AU UtilsWeb are not be excluded by DMT. |
2.2.9
Resolved Issues
| Customer Ticket Id | Details |
|---|---|
| 37543 | Fixed an issue where Java package was marked as incomplete package. |
Other Updates
| Details |
|---|
| Fixed an issue where blank project names were created for selected 'Java files per package folder', when java files are present in root. |
2.2.8
Resolved Issues
| Customer Ticket Id | Details |
|---|---|
| 36320 | Fixes an issue where identical JEE projects are discovered for the same root path (one for Maven and one by the JEE File Discoverer), creating duplicate Analysis Units. |
Other Updates
| Details |
|---|
| As a result of the fix provided for the customer bug 36320, the discoverer has been modified to ensure that any discovered JEE File projects that contain only JSP source code already covered by a regular (Eclipse or Maven) project are discarded, ensuring that duplicate Analysis Units are not created for the same root path. |
2.2.7
Note
The overall algorithm has been changed to group together the incomplete package (resp. unnamed package) files that belong to the same folder, and to split the resulting projects from the regular ones (made of complete package files).
Resolved Issues
| Customer Ticket Id | Details |
|---|---|
| 33744 | Fixed an issue where the JEE Analysis Unit was not created due to the presence of a file called AppAuth.java. This change improves the discovery of JEE based projects and as a consequence the number of incomplete/unnamed projects that were previously discovered may be significantly decreased in some cases. |
2.2.6
Resolved Issues
| Customer Ticket Id | Details |
|---|---|
| 32837 | Fixed an issue where the JEE file discoverer did not include "web jsp" type projects. These projects are now taken into account. |
2.2.5
Resolved Issues
| Customer Ticket Id | Details |
|---|---|
| 27207 | SRC path references in AU configuration changes after upgrade |
2.2.4
Resolved Issues
| Customer Ticket Id | Details |
|---|---|
| 24970 | Test codes are not excluded from analysis |
| 15838 | Missing link from JSP to JSF managed Bean |
| 20909 | WSDL files are not picked up by DMT |
2.2.3
Resolved Issues
| Internal ID | Call ID | Summary | Impact? |
|---|---|---|---|
| DISJFIL-86 | 21277 | One Java File discoverer exclusion rule has excluded a Maven project source path | The exclusion rule "Exclude all 'Java files per package folder' projects when a full JEE project also exists for these files" scope must be only JEE file without project'. When this selection rule is activated, and source directory references in a regular Java project (Maven, Eclipse) are covered by another Java project. The selection rule does not remove these source directory references in the regular Java projects. |
2.2.2
Resolved Issues
Below table lists the internal and customer bugs fixed in the 2.2.2-funcrel release:
| Internal ID | Call ID | Summary | Impact? |
|---|---|---|---|
| DISJFIL-74 | 16799 | Add files and references from Web JSP discoverer to Java File Discoverer | A change has been made to exclude web JSP project when JEE file discoverer is present (java files per package folder) in the same web.xml. To implement this we have new exclusion rule (Exclude all 'Web JSP project' when 'Java Files Per package Folder' exists for the same web.xml file) along with JEE file discoverer which is selected by default. Initially in JEE file discoverer, analysis unit web descriptor path was blank, now this path is populated. |
| DISJFIL-76 | - | CAST Management Studio - Many duplicated java analysis units | Changes are made to avoid having duplicated projects (as one project contains the other). This is implemented by adding new exclusion rule 'Exclude Java Files Project located inside other Java files Project'. This selection rule is set to false by default. User can select it when required. |
| DISJFIL-79 | - | Remove source references already covered by another Java project | When a source files package contains Java files not covered by a Maven/Eclipse project, and, in a sub-directory, contains also Maven/Eclipse project based source files, then the discovered Java file project should not refer to the Maven/Eclipse project based source files. |
| DISJFIL-83 | - | Change the name for the root project from "." to the name of the package | When a Java files project is created at the root of the sources directory tree, then the name of this root project should be the same as the name of the package, instead of ".". |
| DISJFIL-84 | 20513 | Existing Java file unanalyzed | After the fix, Java files are analyzed. This fix is a regression introduced in 2.1.0-funcrel (DISJFIL-59) |
2.2.1
JEE File Discoverer 2.2.1 has been released as an LTS (Long Term Support).
Updates
DISJFIL-69 - Signing required when using the extension with CAST AIP 8.2.x.
The extension is optimized to work with CAST AIP 8.3.x, which does not require signed MDA plugin files. However, CAST AIP 8.2.x requires signed MDA plugin files and therefore a manual action is now required before the extension is installed, see Initial actions required when using CAST AIP 8.2.x and extension v. ≥ 2.2.1 for more information about this manual action.
Resolved Issues
| Internal ID | Call ID | Summary | Impact? |
|---|---|---|---|
| DISJFIL-69 | 17245 | User getting an error while trying to package through DMT with extension "JEE file discoverer" version "2.1.0-funcrel" installed with CAST AIP 8.2.7 | User can do packaging without any error with "JEE file discoverer" version "2.2.1-funcrel" installed with CAST AIP 8.2.x. |
2.2.0-funcrel
Updates
DISJFIL-19 - DMT discovery for XML & properties
When the .xml file and the .properties file for a java project exist in same folder, the JEE File Discoverer will now discover references for both files (instead of just one of them). The files will be referenced by the discoverer with the languageID and the resourceID.
Resolved Issues
Below table lists the internal and customer bugs fixed in the 2.2.0-funcrel release:
| Internal ID | Call ID | Summary | Impact? |
|---|---|---|---|
| DISJFIL-60 | 15987 | Permanent Fix: java files with same package are discovered as Invalid package and incomplete package creating inconsistent discovery logs | Previously, any packages flagged as incomplete packages where also marked as invalid packages, thus creating inconsistency in log files. Now, incomplete packages are not marked as invalid packages, ensuring the log is consistent. You can view information about package types in JEE File Discoverer 2.2. |
| DISJFIL-65 | 16204 | Permanent Fix: Duplicate analysis unit created with the same path covered | Previously, when activating the selection rule Exclude all 'java files per package folder' project with an incomplete package, incomplete packages as well as unnamed packages were excluded. The fix for this bug involves modifying the behaviour of the selection rule for unnamed packages (Exclude all 'java files per package folder' project with unnamed package): now the unnamed packages will not be flagged as incomplete packages. Thus, the selection rule Exclude all 'java files per package folder' project with an incomplete package will only exclude the incomplete packages as expected. |
