Overlapping classes in quickfixj-core-1.6.1.jar and quickfixj-messages-fix44.jar

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Overlapping classes in quickfixj-core-1.6.1.jar and quickfixj-messages-fix44.jar

Derek Mahar
QuickFIX/J Documentation: http://www.quickfixj.org/documentation/
QuickFIX/J Support: http://www.quickfixj.org/support/



Why do jarfiles quickfixj-core-1.6.1.jar and quickfixj-messages-fix44.jar have so many overlapping classes?  Maven Shade Plugin 2.4.3 reports the following overlapping classes:

Including quickfixj:quickfixj-messages-fix44:jar:1.6.1 in the shaded jar.
quickfixj-core-1.6.1.jar, quickfixj-messages-fix44-1.6.1.jar define 1173 overlapping classes: 
  - quickfix.field.ExchangeSpecialInstructions
  - quickfix.field.TargetCompID
  - quickfix.field.ListName
  - quickfix.field.SettlBrkrCode
  - quickfix.field.NoMsgTypes
  - quickfix.field.InstrAttribType
  - quickfix.field.SimulatedTime
  - quickfix.field.ClearingInstruction
  - quickfix.field.ExDestination
  - quickfix.field.PosMaintRptRefID
  - 1163 more...
maven-shade-plugin has detected that some class files are
present in two or more JARs. When this happens, only one
single version of the class is copied to the uber jar.
Usually this is not harmful and you can skip these warnings,
otherwise try to manually exclude artifacts based on
mvn dependency:tree -Ddetail=true and the above output.

Can I just ignore this warning? 

Derek

------------------------------------------------------------------------------

_______________________________________________
Quickfixj-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/quickfixj-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Overlapping classes in quickfixj-core-1.6.1.jar and quickfixj-messages-fix44.jar

Derek Mahar
QuickFIX/J Documentation: http://www.quickfixj.org/documentation/
QuickFIX/J Support: http://www.quickfixj.org/support/



I resolved this issue by replacing dependencies quickfixj-core and quickfixj-messages-fix44 with quickfixj-all.  As a side-effect, using quickfixj-all also resolved another issue that I encountered where my application would mysteriously jump to the most outer final block (skipping all inner catch blocks) when it first tried to create an instance of class NewOrderSingle.

On 5 April 2016 at 16:12, Derek Mahar <[hidden email]> wrote:
Why do jarfiles quickfixj-core-1.6.1.jar and quickfixj-messages-fix44.jar have so many overlapping classes?  Maven Shade Plugin 2.4.3 reports the following overlapping classes:

Including quickfixj:quickfixj-messages-fix44:jar:1.6.1 in the shaded jar.
quickfixj-core-1.6.1.jar, quickfixj-messages-fix44-1.6.1.jar define 1173 overlapping classes: 
  - quickfix.field.ExchangeSpecialInstructions
  - quickfix.field.TargetCompID
  - quickfix.field.ListName
  - quickfix.field.SettlBrkrCode
  - quickfix.field.NoMsgTypes
  - quickfix.field.InstrAttribType
  - quickfix.field.SimulatedTime
  - quickfix.field.ClearingInstruction
  - quickfix.field.ExDestination
  - quickfix.field.PosMaintRptRefID
  - 1163 more...
maven-shade-plugin has detected that some class files are
present in two or more JARs. When this happens, only one
single version of the class is copied to the uber jar.
Usually this is not harmful and you can skip these warnings,
otherwise try to manually exclude artifacts based on
mvn dependency:tree -Ddetail=true and the above output.

Can I just ignore this warning? 

Derek


------------------------------------------------------------------------------

_______________________________________________
Quickfixj-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/quickfixj-users
Loading...