Post reply

Warning: this topic has not been posted in for at least 120 days.
Unless you're sure you want to reply, please consider starting a new topic.
Name:
Email:
Subject:
Message icon:
Verification:
Type the letters shown in the picture
Listen to the letters / Request another image

Type the letters shown in the picture:
What is the last letter in the word "SlickEdit":
How many LETTERS are in the following? "a1b2c3":
Which number is missing?  "12345689":

shortcuts: hit alt+s to submit/post or alt+p to preview


Topic Summary

Posted by: patrick
« on: August 20, 2018, 01:54:14 PM »

Fixed for the next beta so the wildcard class path entries show up.
Posted by: patrick
« on: August 16, 2018, 08:33:54 PM »

I get the same.  When I use the wildcard option, none of the jars in the repository show up in the generated classpath.  Only the ones I add individually.  I'll look into it.
Posted by: jporkkahtc
« on: August 16, 2018, 08:15:27 PM »

I've got a big java project that imports lots of jars.
The jars are managed by maven.

Even though I setup JavaOptions -> Classpath to include:
C:\Users\jporkka\.m2\repository\*.jar

Slick clearly doesn't import all of those jars as it is unable to find lots of the symbols.

If I add specific jars in this dialog, that seems to work.

Should this work?
How can I tell what JAR files Slick is using?