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
I'm experiencing a strange issue. For some reason the resolve task fails for some people but
not for others.
We narrowed the issue down that it has to be somehow classpath ordering related, as we have
two conflicting versions of swagger-core in our classpath. This is an issue of its own but we
never noticed, as the build never failed.
I guess the reason we experiencing this, is that the resolve task uses an Set to filter out
duplicated urls here.
As this set then gets transformed to an array the ordering is not stable. Which means that
for some of my colleagues the wrong version is earlier in the resulting url classpath causing
the build to fail.
The text was updated successfully, but these errors were encountered:
Hi,
I'm experiencing a strange issue. For some reason the
resolve
task fails for some people butnot for others.
We narrowed the issue down that it has to be somehow classpath ordering related, as we have
two conflicting versions of
swagger-core
in our classpath. This is an issue of its own but wenever noticed, as the build never failed.
I guess the reason we experiencing this, is that the resolve task uses an
Set
to filter outduplicated urls here.
As this set then gets transformed to an array the ordering is not stable. Which means that
for some of my colleagues the wrong version is earlier in the resulting url classpath causing
the build to fail.
The text was updated successfully, but these errors were encountered: