Unable to find layout/schemaSpy.css

[schemaspy]

Unable to find layout/schemaSpy.css

[rafalkasa]

Hi @saihegde I confirm this bug it will be fixed today

[rafalkasa]

issue fixed

[saihegde]

Thanks. Just tested it. Works as expected.

[tjdavis3]

This error currently exists again in 6.0.0-rc1:

$ java -jar schemaspy-6.0.0-rc1.jar
May 11, 2017 12:20:19 PM org.springframework.context.annotation.AnnotationConfigApplicationContext prepareRefresh
INFO: Refreshing org.springframework.context.annotation.AnnotationConfigApplicationContext@4edde6e5: startup date [Thu May 11 12:20:19 MDT 2017]; root of context hierarchy
Using database properties:
[schemaspy-6.0.0-rc1.jar]/org/schemaspy/types/pgsql.properties
Gathering schema details................................................(192sec)
Connecting relationships................................................(2sec)
Writing/graphing summary..12:23:35.007 WARNING: Main.main - Bad config Unable to find requested file: file:/Users/.../schemaspy-6.0.0-rc1.jar!/layout/schemaSpy.css

[Riggs333]

This issues has the same root cause as #83

I'll try to provide a fix tommorrow as long as noone else does until then.

[rafalkasa]

@Riggs333 now I remember why this isJarFile method was added to the Config class.

You can understand more when you will analyzing my commit 71e32e7 which is fixing the problem reported once again by @tjdavis3.

[rafalkasa]

@tjdavis3 I try to reproduce the issue and after few tests I can't.
I verify schemaspy lunched it from InteliJ IDEA, from command shell and still everything is working correctly.

Your schemaspy-6.0.0-rc1.jar is build by you on your local machine or maybe downloaded version from schemaspy 6.0.0-rc1

Third version can be schemaspy@latest

Could you tell as which version did you use ?

[rafalkasa]

@Riggs333 you prepare the fix how did you reproduce the issue ? This is strange thing unfortunately I try but I can't :-(

[Riggs333]

I could not reproduce the issue as you already said, but found out that the css parameter was not used correctly.

[Riggs333]

Thinking of it again I should have raised a separate issue. But this is strongly related.

[rafalkasa]

Thank you for let me know, it was strange for me. Good that you also could not reproduce the issue.

From my point of view -css parameter is different story but somehow related.

[tjdavis3]

It was downloaded from the site

…

On Fri, May 12, 2017, 00:26 Rafal Kasa ***@***.***> wrote: Thank you for let me know, it was strange for me. Good that you also could not reproduce the issue. From my point of view -css parameter is different story but somehow related. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#26 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AJqqbIQPTKoRnfW49PNeWMxkBtUNGS_8ks5r4_uFgaJpZM4LZ4Fo> .

[rafalkasa]

@Riggs333 I would like confirm the issue reported by @tjdavis3 if you download schemaspy@latest application throw exception described by @tjdavis3 only when you will run it from command line java -jar schemaspy-6.0.0-rc1.jar. I can't reproduce the issue before because I had in my configuration custom template provided -template. This issue not occurred when you download last released version of SchemaSpy schemaspy-6.0.0-rc1.jar

[rafalkasa]

@Riggs333 after few test I can't to reproduce this scenario based on changes made in pull request #87 but this must be verified also after the merge with master.

[Riggs333]

I cannot reproduce the issue either. Nevertheless #90 should be merged to fix the other problem.
I would like to take a deeper look at this issue again if #90 and #87 are merged.

[tjdavis3]

For what it's worth, after reading Rafal's email on the 15th, I extracted the jar file contents and ran it as java -jar schemaspy-6.0.0-rc1.jar -template schemaspy/layout and it worked. It only failed when run without -template (I had also previously tried running it from the extracted jar as java org.schemaspy.Main, which also failed).

…

On Thu, May 18, 2017 at 12:37 AM Thomas Traude ***@***.***> wrote: I cannot reproduce the issue either. Nevertheless #90 <#90> should be merged to fix the other problem. I would like to take a deeper look at this issue again if #90 <#90> and #87 <#87> are merged. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#26 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AJqqbPLbN4s4rcYLWhR9wYWpHtCgyvXsks5r69krgaJpZM4LZ4Fo> .

[rafalkasa]

@tjdavis3 after many test I can't reproduce your scenario based on schemaspy@latest. In my opinion problem was fixed and I'm close the issue.