-
Type:
Bug
-
Resolution: Fixed
-
Priority:
P2
-
Affects Version/s: 7u45
-
Component/s: deploy
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8027005 | 8 | Mark Howe | P2 | Closed | Fixed | b113 |
| JDK-8034443 | 7u65 | Mark Howe | P2 | Resolved | Fixed | b01 |
| JDK-8027009 | 7u60 | Mark Howe | P2 | Resolved | Fixed | b01 |
the Application-Name attribute is read from the “main” jar only, although all jar files without it generate a warning.
o if it is only read from the “main” jar file, why do all the other files generate warnings was well?
o Is it going to be mandated that this attribute appears in all the jar files?
o If so,it is the same in every file?
Which doesn’t seem necessary since the authenticity is already validated via the certificate.
o if it is only read from the “main” jar file, why do all the other files generate warnings was well?
o Is it going to be mandated that this attribute appears in all the jar files?
o If so,it is the same in every file?
Which doesn’t seem necessary since the authenticity is already validated via the certificate.
- backported by
-
JDK-8027009 Warning message appears in all the jar files not only the main jar file
-
- Resolved
-
-
-
- Resolved
-
-
-
- Closed
-