[
https://issues.jboss.org/browse/JBIDE-19820?page=com.atlassian.jira.plugi...
]
Viacheslav Kabanovich commented on JBIDE-19820:
-----------------------------------------------
In view of JBIDE-19825, my first comment is partly erroneous.
We do need to scan once all 450 jars, and that takes 56 s. But in wildfly, one jar is a
Batch archive (jberet-core-1.1.0.Final.jar), so that the second scan over all 450 jars was
not needed and took place due to an error described in JBIDE-19825.
Batch is a part of Java EE, and a lot of jars of Java EE are other frameworks that do not
have and will never have Batch artifacts in them. Can we keep a name list of well-known
jars (with '*' instead of version part) and never scan them? [~maxandersen],
[~akazakov] what do you think of it?
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)