[QFJ-800] jar signing issue with quickfixj-all-1.5.3.jar Created: 10/Jul/14 Updated: 02/Apr/15 Resolved: 11/Jul/14 |
|
| Status: | Closed |
| Project: | QuickFIX/J |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.6.0 |
| Type: | Bug | Priority: | Default |
| Reporter: | Hemlata Singh | Assignee: | Unassigned |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Environment: |
windows and linux |
||
| Attachments: |
|
| Description |
|
getting error while signing the jar. ERROR : Tactical fix : Resolved by removing duplicate xml files. |
| Comments |
| Comment by Christoph John [ 10/Jul/14 ] |
|
I cannot see any duplicate FIX40.xml in the jar. Where did you find them? |
| Comment by Hemlata Singh [ 10/Jul/14 ] |
|
multiple xml files. |
| Comment by Hemlata Singh [ 10/Jul/14 ] |
|
Please find attached screenshot. |
| Comment by Christoph John [ 10/Jul/14 ] |
|
That is very strange. When I look at the archive with "ark" I do not see any duplicate entries but when I list the archive entries with "jar tfv <file>" then there are multiple entries for the xml files. Anyways, I was able to sign quickfixj-all-1.6.0-SNAPSHOT.jar successfully. So I'd like to close this issue. |
| Comment by Hemlata Singh [ 10/Jul/14 ] |
|
Hey Christoph, From where can i download quickfixj-all-1.6.0.jar? |
| Comment by Christoph John [ 10/Jul/14 ] |
|
Hi, you can download it here: http://www.quickfixj.org:8085/browse/QFJ-GIT/latest/artifact/shared/qfj-zip/ |
| Comment by Hemlata Singh [ 10/Jul/14 ] |
|
My google chrome is not able to connect to www.quickfixj.org:8085. |
| Comment by Christoph John [ 10/Jul/14 ] |
|
I guess some firewall is blocking access. Maybe you could try downloading it outside of a company network? I am not aware that the access to that page is restricted. |
| Comment by Hemlata Singh [ 10/Jul/14 ] |
|
How can you close the jira without giving me any solution? Requesting you to provide me some solution with quickfixj-all-1.5.3.jar |
| Comment by Christoph John [ 10/Jul/14 ] |
|
The solution to the issue would be to use 1.6.0 once it is released. |