[
https://issues.jboss.org/browse/JBIDE-19825?page=com.atlassian.jira.plugi...
]
Viacheslav Kabanovich updated JBIDE-19825:
------------------------------------------
Description:
In CDI 1.1+ and Batch we can check if jar is an archive only by scanning it. The result is
cached so that jar is scanned only once. When it is scanned for the first time, method
resolve() now returns constant 'UNRESOLVED' instead of the computed result. In
this case jar is scanned for cdi beans / batch artifacts as an archive, which almost
doubles the time at the first build.
Besides, in Batch results for checked jars are not saved as it is done for CDI.
was:In CDI 1.1+ and Batch we can check if jar is an archive only by scanning it. The
result is cached so that jar is scanned only once. When it is scanned for the first time,
method resolve() now returns constant 'UNRESOLVED' instead of the computed result.
In this case jar is scanned for cdi beans / batch artifacts as an archive, which almost
doubles the time at the first build.
Coding error in processing jars in Batch and CDI
------------------------------------------------
Key: JBIDE-19825
URL:
https://issues.jboss.org/browse/JBIDE-19825
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: batch, cdi
Affects Versions: 4.3.0.Alpha2
Reporter: Viacheslav Kabanovich
Assignee: Viacheslav Kabanovich
Fix For: 4.3.0.Beta1
In CDI 1.1+ and Batch we can check if jar is an archive only by scanning it. The result
is cached so that jar is scanned only once. When it is scanned for the first time, method
resolve() now returns constant 'UNRESOLVED' instead of the computed result. In
this case jar is scanned for cdi beans / batch artifacts as an archive, which almost
doubles the time at the first build.
Besides, in Batch results for checked jars are not saved as it is done for CDI.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)