[
https://issues.jboss.org/browse/JBIDE-19820?page=com.atlassian.jira.plugi...
]
Viacheslav Kabanovich commented on JBIDE-19820:
-----------------------------------------------
450 big jars (about 90000 classes) in 56 seconds is rather fast. And it is done only once,
at the first build. The names of jars that do not have Batch artifacts are saved for next
builds. If we cannot afford that much time for scanning, my suggestion above is to keep
the list of Java EE jars that are known to have no Batch artifacts and thus avoid scanning
them.
Batch feature makes wildfly import way slower
---------------------------------------------
Key: JBIDE-19820
URL:
https://issues.jboss.org/browse/JBIDE-19820
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: batch
Affects Versions: 4.3.0.Alpha2
Reporter: Rastislav Wagner
Assignee: Viacheslav Kabanovich
Priority: Critical
Fix For: 4.3.0.Beta1
I made a comparison between Eclipse M6 and Eclipse M6 with batch feature installed while
importing wildfly. WF is imported as maven project, maven is set to offline mode and local
repository contains all needed dependencies.
I did a 4 runs with following results:
M6 was able to import WF 628,575,577,612 (in seconds) = average 598s
M6 with batch feature: 843,832,924,877 (in seconds) = average 869s
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)