Details
-
Bug
-
Resolution: Fixed
-
Minor
-
1.6.3
-
None
-
Grouper client pulled in through a maven dependency
Description
When I attempt to run the grouperClient on a project which has pulled in the grouperClient through a maven dependency I get the error:
Error with grouper client, check the logs: java.io.FileNotFoundException: /Users/buckett/.m2/repository/edu/internet2/middleware/grouper/grouperClient/1.6.3/grouper.client.usage.txt (No such file or directory)
Apr 28, 2011 12:06:15 PM edu.internet2.middleware.grouperClient.GrouperClient main
SEVERE: java.io.FileNotFoundException: /Users/buckett/.m2/repository/edu/internet2/middleware/grouper/grouperClient/1.6.3/grouper.client.usage.txt (No such file or directory)
java.lang.RuntimeException: java.io.FileNotFoundException: /Users/buckett/.m2/repository/edu/internet2/middleware/grouper/grouperClient/1.6.3/grouper.client.usage.txt (No such file or directory)
at edu.internet2.middleware.grouperClient.util.GrouperClientCommonUtils.readFileIntoString(GrouperClientCommonUtils.java:4877)
at edu.internet2.middleware.grouperClient.util.GrouperClientCommonUtils.readResourceIntoString(GrouperClientCommonUtils.java:4937)
at edu.internet2.middleware.grouperClient.GrouperClient.usage(GrouperClient.java:2547)
at edu.internet2.middleware.grouperClient.GrouperClient.main(GrouperClient.java:247)
Caused by: java.io.FileNotFoundException: /Users/buckett/.m2/repository/edu/internet2/middleware/grouper/grouperClient/1.6.3/grouper.client.usage.txt (No such file or directory)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(FileInputStream.java:106)
at edu.internet2.middleware.grouperClient.util.GrouperClientCommonUtils.readFileToString(GrouperClientCommonUtils.java:4956)
at edu.internet2.middleware.grouperClient.util.GrouperClientCommonUtils.readFileIntoString(GrouperClientCommonUtils.java:4875)
... 3 more
Digging through web pages and source it seems I'm supposed to make a copy of the example file for my own usage and customise it. This isn't very user friendly, wouldn't it be better to have a default usage description that it used, but can be overridden?