You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the Eclipse Transformer on WAR/EAR files where it takes a very long time (30 min to hours), it's frustrating to not have any visibility on what's happening.
Usually, the quiet mode is too quiet, the verbose is useless for significant WAR/EAR and the trace not relevant and even slower and unsuable.
I was wondering what I could do to optimise, and the first thing I wanted to look at is the time it takes at least per WAR (in the EAR) and per JAR. Not sure it's too useful to display class/resource level timings for now
The text was updated successfully, but these errors were encountered:
When using the Eclipse Transformer on WAR/EAR files where it takes a very long time (30 min to hours), it's frustrating to not have any visibility on what's happening.
Usually, the quiet mode is too quiet, the verbose is useless for significant WAR/EAR and the trace not relevant and even slower and unsuable.
I was wondering what I could do to optimise, and the first thing I wanted to look at is the time it takes at least per WAR (in the EAR) and per JAR. Not sure it's too useful to display class/resource level timings for now
The text was updated successfully, but these errors were encountered: